Machina · the IDE for machines

Fly it a thousand times before you build it.

Machina is an AI engineer for drones and robots. Describe the machine and its goal, and its agent picks real parts, models the frame, designs the electronics and checks them. We're closing the loop now: the real autopilot firmware flies every design in simulation, and the agent keeps improving it until the goal is met.

Lap
1000/1000
Design
4/4
Laps failed
0.0%
Gate error p95
0.65m
Response lag
90ms

Live in your browser: a toy quadrotor flies 1,000 laps through seeded gusts and is redesigned every 250. Move the pointer to blow wind at it.

01Machina today

From a few sentences to a frame ready for the cutter.

A recorded agent session, sped up. The agent picks motors, props and a battery from the parts library, builds the frame feature by feature in carbon-fibre sheet, checks each arm at full throttle with finite elements, and produces ISO drawings, DXF files and a bill of materials.

Recorded in Machina. The parts, the design, the analysis and the drawings are the agent's; the captions are ours.
2–3%
from textbook references, across its analyses
30 / 34
design cases passed in our last live evaluation
500+
tools the agent drives, from sketch to SPICE
Any LLM
Claude, GPT, Gemini or a local model; outside agents connect over MCP
02Why

Software has tests. Hardware has crashes.

We built our first racing drone from scratch. We printed the frame and built the circuits, and thirty seconds into its first flight it fell out of the sky.

We had missed one capacitor. When the motors braked, the voltage spike on the battery bus reset the flight controller. That one mistake cost us three weeks and $600, and nothing we used could have caught it before we built.

So we're building the tool that would have.

The spike that crashed our drone computed in your browser
Bus capacitor

Peak 36.9 V against a 36 V rating: the flight controller resets.

The model: a full 6S pack (25.2 V, 12 mΩ); about 1 µH per metre of battery lead; 10 µF of ceramics on the ESC; an optional 1,000 µF capacitor with 20 mΩ ESR; the motors braking from 45 A drawn to 30 A returned in 2 µs; a regulator rated for 36 V. Checking this on your real parts, in flight, is part of the loop we're closing.
03Failure modes

The failures nobody warns you about.

They hide where parts meet, so no single tool sees them. Each one takes minutes to fix on a screen, and a crashed prototype to find in the air.

  1. Carbon fibre conducts.

    A battery lead that rubs through its insulation on a carbon arm shorts the whole drone mid-flight.

  2. Carbon fibre blocks radio.

    An antenna tucked inside the frame loses the control link at range.

  3. Some materials don't mix.

    Carbon fibre bolted straight onto aluminium corrodes the aluminium.

  4. One millimetre too long.

    Motor screws that reach the windings short the motor the first time it spins up.

  5. A battery that can't keep up.

    At full throttle the motors pull more current than the pack can deliver. The voltage sags, the flight controller resets, and the drone falls.

  6. Braking spikes.

    On a 6S pack, braking motors push spikes back into the power lines that kill the flight controller, unless a capacitor sits in the right place.

  7. Resonance.

    If the frame's natural frequency falls inside the motors' RPM range, vibration floods the gyro and the drone shakes itself out of control.

  8. Arms that flex.

    At full thrust a thin arm bends far enough for a prop to strike the frame.

  9. Heat with nowhere to go.

    ESCs and regulators packed into a closed stack overheat halfway through a hard flight.

  10. Joints that stall.

    A robot joint that holds its load standing still but stalls the moment the arm accelerates.

04The loop

The loop hardware never had.

Software engineers have agents that write, test and fix code in a loop. Hardware never got one, because its tools don't talk to each other. Machina keeps a machine's mechanics, electronics and physics in one model that the agent can query, change and test, so a change anywhere is checked everywhere.

Lap 4 · goal met

Mass ≤ 650 g641 gPass
Thrust ÷ weight ≥ 1010.1Pass
Endurance ≥ 4 min, 95%4.2 ± 0.1Pass
Bus surge ≤ 36 V26.1 VPass

Goal met with 95% confidence. Export.

  1. ADescribe

    “A 5-inch racing drone, at most 650 g, with ten times its weight in thrust and four minutes of flight.”

  2. BDesign

    Real parts from datasheets. Frame, electronics and power network in one parametric model.

  3. CFly

    The real autopilot firmware flies it, in lockstep with the physics: PX4, ArduPilot, Betaflight, INAV, or your own controller.

  4. DVerify

    Every requirement checked with its uncertainty. Missing evidence is inconclusive, never a pass.

  5. EImprove

    The agent changes geometry, parts or electronics, shows the result behind each change, and goes round again.

  6. FBuild

    Drawings, CNC and 3D-print files, a bill of materials, and the firmware's own parameter file.

An illustrative run. In Machina, every change the agent makes shows the result behind it.

05Progress

What works, what flies in the lab, what's next.

Works today

From a few sentences of requirements, the agent picks real parts from datasheets, models the machine in 3D, designs its electronics, checks stress, fatigue, dynamics and power, fixes what fails, and produces drawings, CNC and 3D-print files and a bill of materials.

  • Printed drone frames designed entirely by the agent
  • 12,000+ automated tests, every night
  • Engines Open CASCADE, MuJoCo, CalculiX, ngspice, KiCad
  • Runs on Windows, macOS and Linux

In the lab

The real autopilot firmware flying our physics, in lockstep with the simulation clock, so no sensor sample is late and nothing runs ahead.

  • 4 autopilots PX4, ArduPilot, Betaflight and INAV
  • 1,000 runs, 1 trajectory Betaflight on our lockstep fork, every run identical
  • 54 million handshakes 1,000 INAV return-to-home flights, no deadlock
  • 0 of 5.5 million flight-log values changed through our telemetry format
  • Failsafes our simulated GNSS loss, low battery and RC loss trigger PX4's and ArduPilot's own

Next

Close the loop: power transients in flight, sensors and faults, and studies under uncertainty, joined to every autopilot and run until the goal is met.

  • Dec 2026 open to the first drone and robot builders
  • Then the first drone designed by the loop, flown a thousand times in simulation, and built
  • After robots: arms, legs and aerial manipulators
06Team

Two engineers who crashed a drone.

CEO

Saarthak Agarwal

Builds AI agents and infrastructure for a 64,000-GPU AI supercomputer. At Hooke he leads the agent, the electronics and the 3D modelling.

CTO

Alex Torres

Over ten years writing software for hardware: embedded firmware, a GPU neural-network engine, computer vision. At Hooke he leads the architecture and the simulation.

Based in Dublin, Ireland.

07The name

ceiiinosssttuv

ut tensio, sic vis

In 1676 Robert Hooke published a law of nature as an anagram, ceiiinosssttuv, to claim the discovery without giving it away. Two years later he gave the answer: ut tensio, sic vis. As the extension, so the force.

Every stress check Machina runs still starts there.

x 49.0 mm F = kx 1.96 N k 40 N/m
Pull the mass, and let go.

Build the first one with us.

We're opening Machina to the first drone and robot builders in December 2026. Tell us what you're building.