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.

You'll notice this the first time you create a project: Spaceboy starts building in its own sandbox — "Spaceboy's sandbox" in the workspace's environment switcher — not in yours. When it finishes a checkpoint, that work is merged to main, the project's shared line of truth. You then pull the checkpoint 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.

Development and production

Sandboxes are where you work; development and production environments are where you ship. They are deploy targets, not places to build, so they don't appear in the workspace switcher — you reach them from the Deploy button and the Deploys page.

• 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 — before anything reaches your users.
• Production — one per project: your real application or site, on your custom domain. Production releases must pass the repository's release checks before they ship.

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

What your plan includes

• Free — 1 project: build and preview in a sandbox, keep one static app live (with a Spaceboy badge), and use the CLI & API. 1 GiB of library storage.
• Starter — 3 projects, with a development environment for each teammate, a production environment, custom domains, and 100 GiB of storage.
• Pro — 10 projects, 250 GiB of storage, and priority support.
• Team — unlimited projects and 1 TiB of storage, plus bring-your-own integrations and the organization audit log.