Environments

Every builder gets a sandbox

Environments are how a team coordinates on Spaceboy. Everyone who builds on a project — you, each teammate, and Spaceboy's agents — gets a sandbox environment of their own: a private, running copy of the app where you build and preview with your agent. Work in one sandbox never disturbs another. Everyone builds in isolation, branching against the same shared code repository.

Your own sandbox is the live preview you see from the moment you open the workspace. Agents get the same deal: when they run a full setup build (see Advanced setup), they build in a sandbox of their own — "Spaceboy's sandbox" in the workspace's environment switcher — and merge each finished checkpoint to main, the project's shared line of truth. You pull that work into your own sandbox with Sync with main, review it in your live preview, and build on top of it.

The pattern is called git

This way of working has a name: git — the branching-and-merging workflow professional software teams have coordinated with for decades. Everyone works on their own branch of the code; finished work merges into a shared main line; nobody overwrites anyone. Spaceboy runs the entire pattern for you behind the scenes, which is what makes it possible for non-engineers and agents to build with real engineering discipline:

• Isolation — an experiment in your sandbox can't break what your teammates see, or what your users see.
• History — every change is recorded permanently, so any earlier version of the project can be revisited or restored.
• Deliberate merges — work reaches main through checkpoints and reviews, never by accident.
• Parallel work — any number of people and agents build at the same time without stepping on each other.

Working with your team

The workspace's environment switcher lists every sandbox on the project: yours first, then Spaceboy's (with a live building badge while an agent works there), then your teammates'. You can peek at anyone's sandbox, but each one belongs to its builder.

Coordination always flows through main. When main moves ahead of your sandbox — an agent merged a checkpoint, a teammate's work landed — the workspace tells you how many updates you're behind and offers Sync with main to pull them in. Your own work travels the same road in the other direction: it reaches main through reviewed merges, so nothing collides no matter how many people are building.

Where your app ships

Sandboxes are where you work; deployed environments are where you ship. The Publish button always ships the workspace you're looking at to production — there is never a target to pick. Deployed environments are not places to build, so they don't appear in the workspace switcher; you meet them on the Deploys page and in the environment picker on the data pages (Users, Data, Files, Analytics).

• Production — one per project: your real application or site, on its live URL and your custom domain. Every Publish lands here, and production releases must pass the repository's release checks before they ship.
• Development — a deployed copy of your app on real infrastructure, with its own database and configuration. Use it to test the genuine article — real sign-ins, real data, real URLs — without touching what your users see; redeploy any release there from the Deploys page.

Spaceboy provisions and manages each environment's infrastructure, configuration, and secrets in the background — there is nothing to set up.

What every account includes

• Build free — create and remix projects with a full live preview in a sandbox, use the CLI & API, and run agent tasks in parallel, on every account.
• Paid publishes — each published project is $20/month, with a development environment for each teammate, a production environment, custom domains, and hosting, storage, and traffic included.
• Ceilings, not gates — organizations can run up to 50 projects with up to 100 members; those are abuse limits, the same on every account.