Deployments

Publishing your app

Click Publish in the workspace top bar and your app goes live: Spaceboy ships the workspace you're looking at to production — there is never a target, branch, or source to pick. Publish again whenever you have something new; each publish is a fresh release of exactly what you see. Publishing is the purchase moment: every template is Premium at $20/month, and you can ship up to a full-stack app. The Publish button offers the purchase right there; nothing to configure.

The publish flow

Each publish runs as a clear, staged flow you can watch live: database migrations, then the backend, then the web app. A successful publish returns your live URL along with a full report of exactly what shipped at each stage.

Deploy history

Every deploy is recorded in the Deploys tab, so you can revisit any release later — what went out, where, and when. From the history you can also redeploy a past release, to production or to a development environment, when you want to test the genuine article away from your users.

Production releases

Production releases get an extra layer of protection: every one — whether you clicked Publish or a task auto-promoted its finished work — must pass the repository's own release checks before it merges. See Release checks for how the pipeline works.

Ship from anywhere

The Publish button is one of four ways to ship. Ask your agent in chat, run /spaceboy deploy production from a linked Slack channel, or deploy from your terminal:

spaceboy deploy --project <id> --target production   # waits, prints the live URL
spaceboy deploy --project <id> --target development --no-wait

Every surface follows the same rails — plan entitlements, the staged flow, and release checks for production — so a release is a release no matter where you start it.

Your live environment

A successful publish ends with a live URL on a Spaceboy domain, ready to share. From there, attach a domain you own on the project's Domains page, and watch the app run from the dashboard: Analytics for traffic, Data for the database, Users for sign-ups, and Jobs for background work.