Systems studio · LATAM
Your system, built to the measure of your company.
The system is built around how you actually operate, with the specifics your company needs in order to grow. It runs on your infrastructure. When it is done, it is yours.
Range
From the kernel to the counter.
We build from a machine's operating system up to the screen where your employee rings up a sale. If we can go that far down, yours is not a hard problem.
What we build
Four fronts, one craft.
Custom management
Inventory, sales, customers, bookings and invoicing in one place. One stock number, not five spreadsheets contradicting each other.
A system you can ask
Your team asks and the system answers. What sold today, what needs restocking, book Marta for Tuesday. No new screens to learn.
It shows up where your people work
Dashboard, register, self-service kiosk, WhatsApp. The interface follows where your team is, not where it suits us.
Foundational engineering
Kernels, real-time engines, measured performance. For when the problem does not get fixed by stacking another tool on top.
How it works
You start with a diagnosis. You end with the keys.
Three stages, with a clear yes or no at each one. No endless pilots and no licences that grow every year.
How you check it
No receipt, no effect.
It is the rule of the kernel we are writing: nothing happens without leaving a record that it happened. It holds for this site too. Every claim here carries the way to check it: a command, a test, or an address you can open right now.
- systems
- 4
- checkable receipts
- 20
- live surfaces
- 6
systems
checkable receipts
live surfaces
In the ledger
Four systems, with their evidence.
No mockups. These systems are running right now and you can open them.
- 01Being built
workaOS
operating systems
An operating system written from scratch. A no_std Rust kernel, deny-by-default capabilities and an append-only log where nothing happens without leaving a receipt.
- Rust no_std
- Limine
- QEMU/KVM
- virtio-vsock
Open case6 receipts - 02In production
Avícola Morales
commerce · retail
The customer serves themselves at the kiosk and the register charges against that same stock. Odoo as the single source of truth, behind a narrow API.
- Odoo Community 19
- PostgreSQL
- Caddy
- Docker
Open case5 receipts - 03In production
Wiilo
commerce · multi-branch
Several branches and three brands, operated by talking instead of learning screens. 37 business functions exposed over MCP on top of Odoo.
- Odoo
- MCP
- PostgreSQL
- POS
Open case4 receipts - 04In production
Breathline
real-time engines
A game that opens in the browser and runs at sixty frames per second. In-house engine, deterministic physics and headless route validation.
- TypeScript
- Three.js
- three-mesh-bvh
- WebAudio
Open case5 receipts
Also running
- Real estate: enquiries come in and get answered on their ownestate.waitdead.com
- Applications that land instead of getting spammedspear.waitdead.com
Method
How we know it is finished.
The difference between a studio and an agency is not the stack. It is what counts as finished.
- 01
The agreement first, the code after
Before writing anything we put in writing what has to happen for it to count as done, and how that gets checked. If it cannot be checked, it is not a requirement: it is a wish.
- 02
Tests that block the release
Nothing ships if a test fails: that stock reconciles, that bookings do not collide, that two people buying at once break nothing. A demo looking nice is not enough.
- 03
It all stays on the record
Every delivery leaves its evidence stored. It lets you argue with data six months later, when nobody remembers why it was decided that way.
- 04
We tell you no
When something cannot be done, we say so and cut the scope in plain sight. We never call finished what is not.
Talk to us
Tell us what is breaking.
Has your operation outgrown spreadsheets? Is there an old system nobody wants to touch? Write to us. We take few projects at a time.
We answer within the day.
Your system, not your subscription.