How it works
Four moves. One loop. Live URL.
Spawn runs on your machine. Create a real app, run it locally, change it in chat, then publish — without leaving the builder.
-
Create your app
Blank workspace or your own files. Tell Spawn what you’re building — a landing page, a dashboard, a billing flow — and it scaffolds a real project on your machine.
You’re not stuck in a cloud sandbox. The files are yours from the first keystroke.
-
Run a preview
Hit Run and the app starts on localhost. Same process you’ll ship — not a mock render or a temporary cloud preview.
Iterate until it feels right. Deploy stays optional until you’re ready.
-
Change it in chat
Open Build and ask in plain English. Spawn edits the files, shows the diff, and refreshes the preview — no hunting through code first.
After you ship, the same chat is how you iterate. The loop doesn’t end at publish.
-
Publish a public URL
Go Live opens your app to the internet with a real HTTPS URL you can copy or scan — from the same machine you built on. Fast path: Ship → Open to the internet.
For a lasting custom domain, point DNS at your WAN IP and forward the Forge port; keep the PC awake (Auto-start Public URL helps). Tunnel links can refresh after reconnect — Reconnect keeps the saved URL current. Secrets and plugins stay inside Spawn.
On your machine vs public
Clear line between what stays private and what the world can see.
Private Stays on your machine
- Source files and local git history
- Secrets, API keys, and env vars
- Build chat and uncommitted diffs
- Local preview process until you publish
Public Goes live when you ship
- The built app behind your public URL
- Shareable public HTTPS from your machine
- Optional custom domain (DNS + port-forward)
- Only what you choose to publish
- Iterate afterward — Build chat still works
How public actually works
Same product — precise about the internet path so beta expectations stay honest.
- Share now Ship → Open to the internet → copyable HTTPS URL and phone QR. No separate host console.
- Lasting domain A-record to your WAN IP + router port-forward for the Forge port. Spawn shows the steps.
- Machine stays on Traffic from this path needs your PC (and Spawn) running. Tunnel URLs can refresh after reconnect.
What you get
- A private builder Runs on your machine — code and secrets don’t leave until you publish.
- A live public HTTPS link Shareable from your machine via Open to the internet — copy or QR.
- Domains, secrets, plugins Wire hostname, API keys, and plugins inside Spawn — lasting domains need DNS + port-forward.
Ready to try the loop?
Private beta — building in public on spawnapp.org.