An autonomous software factory · invite-only beta

Describe an app.
Get it built, reviewed and live.

An architect turns your sentence into a plan. An engineer builds each change in a sandbox. An independent reviewer approves it or refuses it. Approved work deploys to a URL — inside a daily budget the factory cannot exceed.

New shipyard Invite-only beta

Free during the beta. Sign in with an email link or Google — you're either in, or on the list with this brief.

  • Runs on Cloudflare's network
  • Every build sandboxed
  • Hard budget ceilings
  • Reviewed before anything ships

How it works

Four moments from one factory.

Quake Watch was described in one sentence and cost $3.95 to build. These are the dashboard's own screens along the way.

  1. 01

    Describe it

    One sentence. The repository is created, the page is online, and Alex the architect writes a plan you can read — tickets with acceptance criteria, not a spinner. Close the tab; it runs on the server.

    The setting-up card: the brief at the top, Alex has written the plan, Sam is about to start the first change, Riley will read it when it is written.
  2. 02

    Watch it get built

    Sam the engineer works in a sandbox that is destroyed after the run: reads the files, runs the project's own checks, and hands the diff to Riley. Every step lands on the timeline with what it cost.

    A live run: the pipeline at Review, the timeline of reads, edits and a passing test run, each with its cost, and Riley reading the change.
  3. 03

    It asks when it should

    Riley reviews without ever seeing Sam's reasoning, and refuses when a test is missing. When the team can't settle it, you get the question, a preview of the change, and three buttons.

    A question card: should this change go live as it is, with a preview of the page, the checks passing, and Ship it, Send it back and Drop it buttons.
  4. 04

    It ships

    Approved work merges and deploys to a URL you can open. The factory looks at the live page itself and says whether it shows what was asked for. Five changes, $3.95, nobody sat and watched.

    The finished product on the dashboard: the live Quake Watch page, five changes merged for $3.95, and the factory's own verdict that it shows what was asked for.

Staged states of a real product. Quake Watch's brief, its cost and the page in the picture are from the ledger; the run and the question are the dashboard as it looks mid-build.

On the factory's own ledger, since it started building for other people:

98
pull requests merged

Each on a repository you own, that you can still read.

$0.51
of model spend per merged change

Everything it spent, divided by what shipped — not by what ran.

44 of 124
changes the reviewer refused first

Sent back for repair or handed to a person. Not a rubber stamp.

Read from the factory's own database, 30 August 2026.

Why a factory

Prototyping tools make demos.
Factories make products.

v0, Bolt and Lovable are great for a Friday-afternoon prototype. Shipyard is built for the application you will still be running in five years.

Prototyping tools
Shipyard
What you get
A demo link that looks right
A deployed app, plus the repository behind it
Definition of done
The model says it's done
Your project's tests and checks pass
Review
You eyeball the output
An independent reviewer that never sees the engineer's reasoning
Cost
Open-ended metering
A daily ceiling you set, enforced in the payment path itself
Where code runs
A shared cloud workspace
An isolated sandbox, destroyed after every run
When it's stuck
It keeps generating
It stops, says what it tried and what it spent, and asks

Your credentials stay out

The sandbox never holds your tokens. Repository access goes through an authenticated proxy outside the box — code inside can't leak a credential it never had.

Every change is a pull request

An audit trail and a revert point, on a repository you can download whole. Approved work merges on its own; the pull request is your record of it.

Nothing ships that the reviewer rejected

Work it refuses comes to you with a preview and three buttons, and anything touching the factory's own rules waits for a person whatever else is true.

Questions

Asked and answered.

What does it cost?

Nothing during the beta. There is no card, and every factory has a ceiling of $2 a day that it cannot spend past — you can lower it, and the factory stops at it rather than asking. What you can already see is the arithmetic we will price from: the ledger above is $0.51 of model spend per change that shipped. When there is a price it will be per change, and you will meet it before it costs you anything.

Why is it invite-only?

Every factory on the platform draws on one shared spending limit, so a handful of very busy factories could leave a newcomer with an error nobody explained. We let people in as that room exists. Describe your product above and sign in: you are on the list with your brief, and the sign-in link arrives by email when it is your turn. Already have an account? You are in — nothing changes for you.

Who owns the code?

You do, under your license. Download the whole thing as a zip whenever you like — no GitHub account needed — and if you leave Shipyard tomorrow you keep the code and the deployed app. Want it in your own GitHub instead? Ask and we will transfer it.

Is it safe to let it run unattended?

Every build runs in a fresh sandbox on Cloudflare's infrastructure, created for the run and destroyed after it, with no credentials inside. The budget is a precondition the code checks before every model call, not a policy someone follows. And a run that stops early is a short report on the dashboard and one email, never a surprise bill.

What happens when the factory gets stuck?

It stops and says so, plainly, with what it tried and what it spent. If the reviewer and the engineer cannot settle it, you get the question, a preview of the change, and the choice to ship it, send it back with a note, or drop it.

Which stacks do you support?

Web products first: a static site with a small server for fetching data, in JavaScript, deployed on Cloudflare. TypeScript and Node.js applications next, and more as we learn which ones people actually ask for. Tell us what you run — [email protected] reaches a person.

Is my code used to train models?

No.

What will your factory ship?

Describe the product. Watch a team plan it, build it, review it, and ship it — inside a budget it cannot exceed. Free during the beta; invite-only for now.

Start building

One email, with your sign-in link. Nothing else.