Partner Login EN
Engineering & robotics

Engineering & robotics — where software meets hardware.

The long-horizon bet. AI applied to controls, sensing, and automation — the place software is heading whether industry is ready or not. Selective, exploratory, deliberately small.

Engineering & robotics Operator partners only
Software → hardware
AI applied to controls, sensing, automation
StageR&D · early
FormatCo-build · operator-led
Projects1–2 active
StatusOperator partners only
The thesis

Why this discipline exists.

The next decade of meaningful AI work happens where software touches the physical world — manufacturing lines, logistics, energy systems, agriculture, clinical environments. Generative models on a screen are easy now; closed-loop systems with sensing, control, and consequence are hard.

We don't run a robotics lab. We don't sell humanoids on TED stages. We co-build with operators who already understand a physical domain — and we bring the AI, software, and systems engineering they don't have time to staff for internally.

Most projects in this discipline never leave the operator's facility. That's the point.

Areas

Where we spend the time.

Sensor fusion & control loops

Combining vision, depth, IMU, and process telemetry into closed-loop systems. From offline modelling to deployed controllers running at the edge.

AI-assisted vision

Computer vision in industrial settings — defect detection, tracking, scene understanding. Not pretty demos; production-grade pipelines that survive a factory floor.

Sim-to-real

Building simulators that the real system actually transfers from. Reuses the spatial pipeline behind Witmodel and the data pipeline behind WMind.

Hardware-in-the-loop

Test rigs, calibration tooling, and the unsexy infrastructure that makes physical systems iterable on a software cadence.

How we engage

Operator-led co-build, or nothing.

We don't take engineering & robotics work as a vendor. We co-build with an operator partner who owns the domain, the facility, and the customer relationship — and we bring the engineering. Equity-for-build, capped scope, clean exits if the thesis doesn't hold.

What we look for
  • 01An operator partner who already sells into the target sector
  • 02A specific physical problem with a measurable improvement target
  • 03A 12–24 month horizon, not a 6-month tech demo
  • 04Willingness to structure as a co-build (equity, not invoice)
What we won't do
  • 01Build a robot for a press release
  • 02Take a fixed-fee project to deliver a fragile demo
  • 03Compete with our customers' own engineering teams
  • 04Pretend a research project is a product

You know the domain. We bring the engineering.

If you're an operator with a physical problem, an existing customer base in a specific sector, and the willingness to co-build rather than buy consulting — we'd like to talk. Most weeks the answer will be "not now, not us" — but the right fit is rare and worth finding.