Thermostats, e-bikes, lab instruments, factory panels, coffee machines: every device with a screen is still built by hand. Agents could do much of the work, but on embedded they're coding blind. They can't run what they write, and nobody sees the real thing until hardware arrives.
The factory compiles device software to a WebAssembly container that doesn't care which hardware it's on. That gives agents a closed loop: build, run, check against the spec, fix, repeat. All of it happens before anything is flashed to a board.
$ aperitivo build --spec thermostat-t4/spec.md › reading spec ............ 38 requirements › agents: screens, logic, bindings › compiling (ui → wasm) ok › binding pipes sensor.temperature → f32 setpoint.target ← f32 schedule.active ← enum › testing in twin ...... 36/38 passed › agents fixing 2 failures ok › testing in twin ...... 38/38 passed › flashing dev board (STM32) ok $
A general coding agent knows a bit about everything. The factory gives it what it needs to ship a real device: the right stack, the right context, and a way to prove the result works.
The factory builds the app container. You own the C connectors and drivers. In between sits a standard schema of named values, the pipe. Agents build against it, and it's the reason the twin behaves exactly like the device.
Where agents test their work, and where your team reviews and shares the real device from a link, long before hardware exists.
Flash it onto a small MCU and run it against real or simulated signals.
The identical container ships in the device. What you approved is what customers get.
We first built this architecture inside the HQ of a global appliance maker in 2024. Drivers were in C, and everything on screen ran in a WebAssembly runtime, because a screen should never be able to crash the machine. It also turned out to be exactly what AI agents need: a safe box they can build, run and test on their own.
Product and design teams get working device software they can change themselves, without waiting for a firmware cycle. Embedded teams stay focused on drivers and hardware.
Ship your MCU with an AI-ready software factory, so customers get from evaluation board to a working product on your silicon far sooner.
aperitivo
In Italy, aperitivo is the hour between work and dinner. We named the company after it because that's what the factory gives back: the time your team spends hand-building device software, returned to work on the product itself. Tell us about the device you're building next.