How building with SPOE works in practice, from your first prompt to an app running on your own server.
Sign up with an email, Google or GitHub: you get 250 credits, topped back up to 30 every day you are below that, and 3 projects. Press New Project, describe what you want, and choose a web app (Next.js, Fastify and Postgres) or a website (plain HTML). You can also start from an app idea, from a stack you put together, or from a site you already have.
Credits pay for the AI models. Before a change runs you see an estimate; you are charged once, when the change is ready, from each model's real price. A build that fails is never charged, and rejecting a finished change does not refund it. A build costs about 22 credits on average. Credits never expire, and a balance never goes below zero.
A coding model writes your change into the project's files, inside the scaffold SPOE provides. A second model from a different family reviews it. A critical finding blocks the change whatever the reviewer's verdict, and a review that times out or errors is never a pass: it waits for you. With auto-apply on (the default) a change the review passes goes in as a version. A blocked or unreviewed change, one with a high or critical finding, and one touching files you edited yourself wait in the diff view. Your own edits are never silently overwritten.
Every applied change is a version. Roll back to any version, byte for byte; a rollback asks you to confirm and is recorded in your account's audit log.
The studio runs your app in a live preview as you build. A website previews instantly. On a bigger request the build agent reads the preview's own output and fixes what broke.
Check scans the project for leaked keys and risky code. Fix sends a finding to the builder; Accept risk records it in SECURITY.md as a version. A critical finding holds a publish until you choose Publish anyway, which is recorded. Exports are never held. The same check ships in every export as check.mjs.
Press Publish in the studio and the app goes live at its own address on spoe.dev, a website in seconds. Publish again after a change to update it, or unpublish it. Every live app is listed under Deployments.
Find a domain and its price, then connect it from the Publish dialog: SPOE gives you one CNAME record to add where you bought the domain and checks it for you. Point it at the name SPOE shows, not at your app's spoe.dev address.
Export a ZIP or push to your own GitHub. An export holds the code, the database migrations, a docker-compose.yml, the signed PROVENANCE.json and PROVENANCE.sig, the verifier verify-provenance.mjs and check.mjs. It runs with docker compose up and depends on nothing of SPOE. Export unlocks for good with your first payment of any size; your code is visible and copyable in the editor either way.
Drop an export's ZIP on spoe.ai/verify: it checks every file against the signed manifest, and that spoe.ai signed it, in your browser, uploading nothing. Offline, run node verify-provenance.mjs inside the export, or npx @spoe/cli verify ./my-app.
Link a repository you own and every version is pushed to it as a commit. Changes made on GitHub can be pulled back into the project, and land as a version like any other.
Put together the stack you want (database, auth, hosting) and start a project from it. SPOE writes the deploy files for it: render.yaml, fly.toml, netlify.toml, wrangler.toml, firebase.json, .do/app.yaml or a GitHub Pages workflow, plus DEPLOY.md and the rules the builder keeps to in AGENTS.md.
Pro holds 3 people and Studio 10, the owner included. Send an invite link from Settings, Team. Members spend the plan's credits and can export; each person's projects stay private to them.
Use your own Venice or OpenRouter key to pay the provider directly; it stays in your browser, and a call on it costs a flat 1 credit. An app's own secrets, like a Stripe key, go in the project's secrets, sealed at rest and never written to a log.
Chats, bots, prompts, images, voice, books and workflow drafts are kept in your browser, for your account only, never on SPOE's server. Model calls pass through SPOE, which records the model, the token counts and the credits, never the words. Back it all up, restore it or delete it in Settings, Your data.
The SPOE API serves the same models in OpenAI's shapes, paid from your credits. SPOE is also an MCP server for Claude, Cursor and ChatGPT, and npx @spoe/cli checks names and verifies exports from a terminal.
Write to access@spoe.ai with anything. Security reports go to the same address; the security page says how.
How it works · Features · Models · Pricing · Docs · Blog · Handle checker · App ideas · Compare builders · Verify an export · Developer API · Start free
This page needs JavaScript to run the app itself. Everything above is a plain description of it.