This is how one person ships all of it.
Not by writing every application. By building the thing that writes them: you give it a goal, an agent lays out the plan, other agents carry it out, other agents grade the result, and anything under the bar goes back round until it passes. It runs on Morax infrastructure today, driven by hand. This page announces the product, it doesn't open it.
Start a build — indisponible. The engine runs on Morax infrastructure, driven internally. No public interface, no queue, no accounts.
No public interface exists yet.
What this product does
It plans, then it builds
From a goal in plain words, one agent writes the plan and others execute it. What comes back is the work itself, not a checklist of steps for you to run by hand.
It grades its own work
Other agents check the result against a test bench wired for the target, and score it. Under 90 out of 100, it isn't done: the work goes back round with the grade attached, and nobody has to be watching.
It runs on whichever model you have
Wire in an open model that costs almost nothing, or the coding plan you already pay for. The engine is not tied to a provider, so the day one closes its door or changes its prices, the work carries on somewhere else.
In detail
The engine already runs, internally
Morax Builder isn't an idea: the engine works today on Morax infrastructure. What's missing isn't the machine, it's the way in.
Outside this repo
Its code doesn't live in Morax One. This hub knows neither its state nor what it's working on.
The first version wasn't worth what it burned
It worked, and it cost more in tokens than the work it produced. Making it cheap enough to leave running took longer than making it run at all — and that, not the demo, is the reason the rest of the ecosystem exists.
No queue
There's no public queue, no account, and no way to submit a goal from this page.
An announcement, not a launch
This page describes what the engine does and what it will become online. The button opens nothing until the interface exists.
Who it is for
- Prototype from a goal
- Describe what the result has to do, and let the engine build then grade it, instead of assembling it yourself.
- Repetitive, checkable work
- Hand over a task whose result can be checked mechanically, so the iteration runs unwatched.
- Everything else on this site
- The applications in this catalogue come out of this engine, which is the honest answer to how one person has this many of them.
Soon, online
The public interface is still to build. When it exists, this button will open something. Until then it announces, it doesn't run.
Start a build — indisponible. The engine runs on Morax infrastructure, driven internally. No public interface, no queue, no accounts.