Databases

Managed in the background

Your sandbox runs its own instant database inside your live session, so you can build, experiment, and reset freely. When you deploy an app that needs one — anything with a backend, auth, or stored data — each environment gets a fully hosted, production-grade database that Spaceboy provisions and connects automatically; you never touch credentials or connection strings. Static apps and games deploy without a database at all.

One database per environment

Every environment's data is its own: your sandbox database, each development environment's database, and production's are fully separate. Test data stays in testing — you can fill your development environment with fake orders and throwaway accounts, and production never sees any of it. This is the same data-isolation discipline professional teams enforce, applied automatically.

Your data is also protected from billing hiccups: if a deployed environment lapses, the app stops serving but its database is kept for two weeks, so topping up and redeploying restores everything.

Migrations, handled by agents

When your agent changes the data model, it writes a versioned migration, reviews it, and runs it as a stage of every deploy — you can watch the migration step in the deploy flow. Your schema evolves safely, in lockstep with your code — no manual database work, ever.

Browsing your data

You never touch credentials, but you can always see your data. The Data page in the dashboard is a SQL browser for any deployed environment: pick the environment, browse its tables with column types and row counts, preview rows, or run a query — written by hand or generated from a plain-language question with AI.

Reads are one click; anything that writes asks for explicit confirmation first. The page is available to organization owners and admins, and every query lands in the audit log.

File storage

Apps that accept uploads get managed file storage alongside the database, isolated per environment the same way. The Files page in the dashboard lists everything your app has stored — visibility, size, type, and owner — with direct links to public files.