Applied science invention lab · Oakville, Ontario

We build things that don't exist yet.

Wren Labs is an applied science and engineering laboratory in Oakville, Ontario developing biotechnology, molecular diagnostics, scientific instruments, laboratory automation, AI, robotics, electronics and advanced manufacturing systems.

We don't separate research from engineering. We don't separate engineering from manufacturing.

The laboratory, in numbers.

We would rather show the shape of the place than describe it. Every figure below is the company's own count, and every one of them is meant to be checked.

  • 40+Scientists, engineers & builders
  • 10+Disciplines under one roof
  • Biology → Chemistry → Physics → Engineering → ManufacturingIn one continuous workflow

One laboratory

  • Molecular biology
  • Synthetic chemistry
  • Materials
  • Physics
  • Electronics
  • Software
  • AI
  • Mechanical engineering
  • Automation
  • Manufacturing

01 / Built differently

One building, many disciplines, very few boundaries.

The problems we work on rarely belong to one field. They move between fields — and at Wren the person who can take the next step works in the same building.

  1. A biological problem becomes
  2. a chemistry problem becomes
  3. a materials problem becomes
  4. a sensing problem becomes
  5. an electronics problem becomes
  6. a mechanical problem,
  7. and eventually somebody has to build the machine.

If the solution exists in a catalogue, we're probably not the right lab. If it requires inventing something new, we might be.

02 / The development stack

From molecule to machine.

We can work across the complete development stack, from the scientific question to the manufactured system, without the problem leaving the building.

  1. Scientific question
  2. Molecular recognition
  3. Chemistry + materials
  4. Sample preparation
  5. Detection
  6. Electronics + fluidics
  7. Mechanical automation
  8. Software + AI
  9. Prototype
  10. Test + validation
  11. Manufacturing

That breadth is deliberate. We think difficult physical technologies are developed faster when the people who understand the molecule, the signal, the electronics and the machine can solve the problem together.

03 / Science

Molecular diagnostics, synthetic chemistry, materials science and physics.

We aren't interested in science that exists separately from the system that uses it. Our scientists work beside physicists, electronics designers, mechanical engineers and software developers.

Molecular biology + diagnostics

  • PCR, qPCR and RT-qPCR
  • Multiplex and isothermal amplification
  • Nucleic-acid extraction and sample preparation
  • Sequencing workflows
  • Assay optimization and validation

sample → prep → extraction → amplification → detection → interpretation

Synthetic + peptide chemistry

We are expanding our ability to create the molecules behind our technologies.

  • Multistep organic synthesis
  • Noncanonical amino acids
  • Solid-phase peptide synthesis
  • Purification and isolation
  • HPLC · LC-MS · HRMS · NMR

Molecular recognition and biosensors

Different targets demand different strategies, so we work across several.

  • Nucleic acids · aptamers
  • Peptides · proteins
  • Synthetic ligands
  • Functional polymers

How do you make a machine recognize something it has never been able to recognize before?

Materials, polymers and reagent stabilization

Sometimes the critical invention isn't the sensor. It's the material touching the sample, or the reagent that has to survive outside an ideal laboratory.

  • Polymer synthesis and functional materials
  • Formulation, composites, surface interactions
  • Structure–property relationships and scale-up
  • Lyophilized reagents for fieldable systems

Physics and measurement

Our physicists work where the signal meets reality.

  • Spectroscopy and optics
  • Sensors and noise
  • Signal processing
  • Statistical inference and modeling
  • Experimental design and reliability

We hire physicists because difficult engineering problems often get easier when someone reduces them back to first principles.

Sometimes we need to invent the chemistry that makes the measurement possible.

04 / Engineering

Scientific instrumentation, embedded electronics and laboratory automation.

Wren develops physical systems that combine mechanics, electronics, fluidics, sensing, firmware and software. Our engineers don't operate downstream of science. They work beside it.

Mechanical + automation

  • Mechanical design and CAD
  • Mechanisms, robotics, actuation
  • Fluid handling, pumps, valves
  • Thermal systems and sample handling
  • Rapid prototyping and DFM

Our engineers don't stop when the CAD is finished. They build it.

Electronics

We build the nervous systems of machines.

  • Mixed-signal electronics and low-noise measurement
  • PCB design and sensor interfaces
  • Motor, solenoid and power electronics
  • Distributed controllers and communications

We don't buy a development board and call it hardware engineering.

Embedded systems + firmware

  • STM32 · ESP32 · ARM
  • RS485 · UART · SPI · I²C
  • Embedded C/C++ · Python · Linux
  • Distributed microcontrollers and sensor integration

The objective isn't simply to make hardware operate. It's to build reusable technical architectures many instruments can grow from.

Scientific instrumentation

We are most at home building machines that:

  • move samples
  • control environments
  • perform chemistry
  • measure physical or biological signals
  • operate outside a conventional laboratory

05 / AI + software

Scientific software, machine learning and device control.

Software isn't an interface sitting on top of our machines. It is part of the machine. Our architecture spans device control, firmware, communications, cloud systems, bioinformatics and experimental data.

The loop we're building toward

  1. Search the scientific literature
  2. Generate hypotheses
  3. Design the experiment
  4. Control the experimental hardware
  5. Analyze results and flag anomalies
  6. Recommend the next experiment

The scientist remains responsible for scientific judgment. The machine removes the repetitive intellectual and experimental work around them.

What that rests on

  • Python · C/C++ · embedded development
  • Machine learning, PyTorch, TensorFlow
  • Data pipelines and bioinformatics
  • Microservice backends and device communication
  • Scientific computing and experimental data systems

Our ambition is not to put AI inside a product. We want AI to change how quickly physical technology can be invented — a cross-cutting tool, not the thing we are.

06 / Test + validation

We try to break everything we build.

A prototype working once proves surprisingly little. We want to know when it stops working, why, whether we can reproduce the failure and whether we can eliminate it.

How we test

  • Accelerated-life testing over thousands of automated cycles
  • Synchronized multi-sensor datasets
  • Environmental and cycle testing
  • Sensor characterization and fluidic reliability
  • Electronics validation and software regression
  • Failure reproduction and root-cause analysis

Map the envelope, not the verdict

Instead of reducing validation to PASS / FAIL, we want to understand where it works, where performance degrades, where it fails and which variable caused the failure. That feeds directly back into the science and the engineering.

Build → break → understand → rebuild.

07 / Build

Prototyping, precision fabrication and manufacturing.

The machine shop is part of the laboratory. Iteration slows dramatically when every physical change becomes a purchase order, so we're building fabrication capability inside R&D rather than at arm's length from it.

From CAD to physical part

  • CAD
  • CAM
  • CNC machining
  • G-code
  • FDM printing
  • SLA printing
  • Laser fabrication
  • Injection molding
  • Electronics assembly
  • Precision assembly
  • Fixtures and jigs
  • Production tooling

The loop we're leaving

  1. Design
  2. Quote
  3. Purchase order
  4. Supplier
  5. Wait
  6. Receive, discover the problem, repeat

The loop we want

  1. Design
  2. Fabricate
  3. Assemble
  4. Test
  5. Learn
  6. Redesign

The goal isn't cheaper parts. It's faster learning: change a part today, test the next revision tomorrow.

08 / This is Wren

Chemistry, molecular biology, electronics and fabrication, in one building.

Six laboratories — chemistry, molecular biology, electronics, the machine shop, instrument development and test — so a sample, a board or a part can move between them without leaving the organization.

Chemistry laboratory

Synthetic chemistry · formulation · peptide chemistry · materials

Molecular laboratory

PCR · qPCR · extraction · sequencing · assay development

Electronics laboratory

PCB development · embedded systems · sensors · instrumentation

Machine shop

CNC · CAD/CAM · rapid fabrication · fixtures · prototyping

Instrument development

Fluidics · robotics · thermal control · automation

Test laboratory

Reliability · accelerated-life testing · automated validation

09 / Projects

Classes of problem: molecular detection, sequencing and field analytical systems.

We don't publish customers or programme details. These are the kinds of systems we work on — technologies meant to move sophisticated analytical capability out of centralized laboratories and closer to where decisions get made.

Molecular detection

Automated systems combining sample handling, nucleic-acid preparation, amplification, detection and software interpretation.

Automated sequencing

Systems designed to reduce the manual workflow between sample, nucleic acid, sequencing and identification.

Environmental sensing

Technologies for understanding complex environmental samples, including water and wastewater.

Molecular recognition

New approaches to detecting targets that conventional nucleic-acid methods cannot directly measure.

Field analytical systems

Ruggedized technologies intended to perform sophisticated sample preparation and measurement outside a conventional laboratory.

Scientific automation

Machines that replace repetitive manual laboratory workflows with controlled, reproducible automation.

Different problems. Shared technology. Every project should make the next one easier.

10 / People

Different brains. Same building.

We don't put names and headshots on this page. What matters to the work is which capabilities are in the room, so that's what we list.

Aerospace + systems

Aerospace engineering, scientific simulation, additive manufacturing, design optimization and complex systems.

Molecular diagnostics

10+ years of assay development, sample-to-answer diagnostics, qPCR, LAMP and other isothermal methods, lyophilization and analytical validation.

Materials science

15+ years across polymer synthesis, functional materials, composites and scale-up.

Synthetic chemistry

Multistep organic synthesis, peptide synthesis, noncanonical amino acids, HPLC, LC-MS, HRMS and NMR.

Machine intelligence + software

Machine learning, device control, firmware, bioinformatics and distributed systems, from embedded C to the data model.

Electronics

Mixed-signal design, low-noise detection, PCB development, power electronics and controls, with 10+ years in embedded systems.

Physics

Astrophysics, spectroscopy, experimental instrumentation, signal processing, statistical modeling and scientific Python.

Manufacturing

CAD/CAM, CNC, injection molding, laser fabrication, 3D printing, precision assembly and production engineering.

What happens when you put all of these people in one building?

  1. A biologist identifies a target.
  2. A chemist designs a molecule.
  3. A materials scientist designs the interface.
  4. A physicist figures out how to measure the signal.
  5. An electrical engineer designs the detector.
  6. A mechanical engineer builds the machine around it.
  7. A software engineer teaches the machine how to operate.
  8. AI helps design the next experiment.
  9. The shop fabricates the parts and the technicians assemble the prototype.
  10. The test engineers try to destroy it.
  11. Then we do it again. That's Wren.

11 / Ambition

The laboratory itself is the experiment.

We're asking a bigger question: what happens if you put an unusually broad group of scientists and engineers together, give them AI tools, rapid fabrication and the freedom to cross disciplines, and optimize the whole organization for iteration speed? We want to compress the cycle.

Idea → experiment

from weeks to days

Experiment → prototype

from months to weeks

Prototype → manufacturable system

from years to months

We want Wren to become a place where a difficult scientific question enters one side of the building and a working physical system emerges from the other.

12 / Careers

Come build impossible things.

We're looking for scientists, engineers and builders who are unusually curious. People who want responsibility before they're completely ready for it. People who would rather learn a new field than say "that's not my job."

Your degree is a starting point. Not a boundary.

  • A physicist can debug a sensor.
  • A chemist can help invent a detection system.
  • A biologist can automate an experiment.
  • A software developer can work directly with a machine.
  • A mechanical engineer can stand beside the scientist running the assay.
  • A technician can find the design flaw everyone else missed.

You might love it here if…

  • You take things apart because you need to understand how they work.
  • You routinely learn things outside your field.
  • You build things nobody asked you to build.
  • You like laboratories, workshops and machines.
  • You'd rather run the experiment than argue about it for another week.
  • You're comfortable saying "I don't know. Let's find out."
  • You want to see something you designed become a physical machine.
  • You care more about whether something works than who gets credit.
  • You want the next few years to make you technically dangerous across more than one discipline.

You probably won't like Wren if…

  • You need your responsibilities narrowly defined.
  • You strongly prefer staying inside your discipline.
  • You want every problem to arrive with an established procedure.
  • You dislike hands-on work.
  • You believe building the prototype is somebody else's job.
  • You want research, engineering and manufacturing kept comfortably separate.

That's okay. There are excellent organizations built that way. We aren't one of them.

Early career doesn't mean small problems.

We deliberately hire exceptional people early in their careers. You may work beside PhD scientists, senior engineers and experienced builders while holding responsibility for a real technical problem. Physics graduates model systems, analyze sensors and build test rigs. Chemists synthesize and characterize, then walk across the laboratory to see how that chemistry behaves inside an actual instrument. Biologists run assays and automate them. Engineers design parts, write firmware, machine prototypes, break them and make the next version better.

We don't expect you to know everything. We expect you to be capable of learning what you don't. That's different.

Tell us what you've built. Email hello@wrenlabs.com.

13 / Work with us

Bring us difficult problems.

We're most useful when the answer needs some combination of biology, chemistry, materials, physics, electronics, automation, software, AI and manufacturing. We can engage at different points:

  • You understand the scientific mechanism but need an instrument.
  • You have an instrument concept but need the underlying assay.
  • You have a prototype that needs automation.
  • You have technology that works in the laboratory but has to survive the field.
  • Or you have a problem nobody has solved yet. That's often the best place to start.

What are you trying to build?

Tell us the problem, not the solution you think you're supposed to buy. What we want to understand:

  • What needs to be measured?
  • Where does it need to operate?
  • How quickly do you need the answer?
  • What has already been tried?
  • What currently makes it difficult?
Oakville, Ontario, Canada