Plain git, not a store
A normal git repository on infrastructure we run. git clone has to actually work from a stranger’s laptop, or "you can walk away with your code" is decoration.
Your code
A git repo from the first turn.
Not an export button. Not a zip at the end. A real repository that exists before the first file is written, receives a push after every turn, and outlives every machine that ever touches it.
Every project is plain git. Clone it onto your own laptop, mirror it to your GitHub, or walk away with it — there is nothing here that only works while you are a customer.
Mirror this to my own GitHub too.
1 push · both remotes updatedmirrored instantly · free to connect
Why it works this way
A machine lives an hour. Your work should not.
Machines are destroyed on a timer. Before this existed, that took the project with it — someone paid to have a site built and it was gone by lunchtime, with no copy anywhere. Now the machine clones the repo on boot and pushes after every turn, so the worst case is losing the machine, never the work.
Gone within the hour
- The machine
- Its filesystem
- Anything running on it
- Its credentials
Disposable by design. Nothing that matters is stored only here.
Kept
- Your git repo
- Every commit, one per turn
- The project's memory
- Your connected accounts
Held against your account, and handed to the next machine at boot.
Full history, not a snapshot
A commit per turn means you can see what changed when, and go back to the version before the one you did not like.
No proprietary format
Real files on a real filesystem. There is nothing to escape from later, because there is nothing holding you.
GitHub
Mirror it to the account you already have.
Connect GitHub once and every push is mirrored to a repository you own, as part of the push that triggered it rather than by a sync loop that drifts and fails quietly.
Being straight about this: GitHub sync is not unusual — Lovable, Bolt and v0 all offer it. The honest difference is that a repository exists here from the first turn without anyone asking for one, and that it is a mirror to your account rather than a copy of ours.
A real one
Every build gets its own repo.
“Build a one-page site for Ridgeline Tree Care, a tree trimming and removal company in Austin, Texas. People should see what we do, why to pick us, and how to get hold of us. Phone (512) 555-0148.”
GPT-5.6 Luna1 turn56s
$0.0092
See all 53 builds →
Access
Your machine gets your credential, and nothing else.
Each account gets its own git user and its own access token, and that token is what goes into the machine. The admin credential never does. Machines run agent-written code on behalf of strangers by design, so the credential inside one reaches only that account's own repositories — data the account already controls. More on that in security.
Build something and clone it.
The repo exists before the first file does. Try it and check.
Questions
Asked, answered
Can I take my code and leave?
Yes. Every project is plain git. Clone it from any machine, or mirror it to your own GitHub account.
What happens when the machine is destroyed?
Nothing. The machine lives an hour; the repository outlives every machine that touches it.