Spacetime Studio use cases: manage local, Maincloud and self-hosted databases

Most SpacetimeDB projects do not live in just one place. You might run a local server while developing, publish a test module to Maincloud, and keep another SpacetimeDB instance on infrastructure your team operates. Spacetime Studio gives you one desktop workspace for connecting to those different environments and seeing what is happening inside each database.

One place for one or many connections

Save connections for the SpacetimeDB servers and databases you work with, then switch between them from the app. Keep a local development database, a shared staging environment and a production database close at hand without having to remember and re-enter each server address every time.

Connections can point to different hosts and databases. A host may contain multiple modules, so you can save and select the database you want to inspect. Studio helps you work with those connections; it does not deploy modules or provision the server itself.

A useful everyday tool for an individual developer

When you are building alone, Studio gives you a graphical view of the module behind your app. Browse its tables and schema, inspect rows, run SQL, try reducers and follow logs from a single native app. That makes it easier to answer practical questions: did my reducer write the values I expected? Is the schema what my client code expects? What happened when I reproduced that bug?

You can use the same desktop workflow whether your database is on your machine or hosted remotely. For a production connection, enable read-only mode to inspect data while preventing writes from Studio.

A consistent workflow across a team

Each developer on a team can install Spacetime Studio and connect to the databases they are authorized to use. That gives teammates a common set of tools for inspecting schemas, checking data, running queries and investigating logs, even if they prefer different editors or client frameworks.

Studio stores credentials in the operating system keychain. Treat saved connections as local to each installation: teammates can share the server URL, database name and setup instructions through their normal team documentation, while each person signs in with their own credentials. Studio is a desktop client, not a centrally managed team console, so access still depends on the server's authentication and permissions.

A team can also use read-only connections for shared staging or production inspection. This reduces the chance that an accidental click or query changes live data while someone is debugging.

Develop against a locally hosted database

For local development, start SpacetimeDB on your machine and add a connection to its local URL, commonly http://localhost:3000. Connect to the database you are building and inspect changes as you update the module and exercise your app.

This local workflow is useful for testing data shapes, calling reducers by hand, and checking logs without mixing development data with a hosted environment. When you are ready to compare with a deployed instance, keep both connections saved and switch between them.

Connect to a Maincloud module

If you publish a database to SpacetimeDB Maincloud, add a hosted connection in Studio and choose the database you want to work with. You can use Studio's tables, SQL, reducer and log tools to inspect the module from your desktop, alongside the Maincloud web dashboard.

Maincloud is the hosting service; Studio is the client you use to connect and work with the database. That means you can use Studio for database inspection without moving your deployment or changing how you publish your module. See the SpacetimeDB Maincloud guide for hosting and publishing details.

Connect to a self-hosted server, including Railway

You can also connect Studio to a SpacetimeDB server running on infrastructure you manage or operate through another hosting provider. Add the server's reachable URL and the database name, then use the same inspection tools you use with a local or Maincloud connection.

For example, the official SpacetimeDB Railway deployment guide describes running a SpacetimeDB instance on Railway and publishing one or more databases to it. After deployment, you can add that instance's public domain as a Studio connection. Studio lets you inspect its modules and data; Railway remains responsible for the service and infrastructure.

The same idea applies to a server on a VPS or other self-managed host: make sure the server is reachable and configured securely, then connect with the appropriate URL and credentials. Studio does not replace the deployment platform or server administration tools.

More visibility into your SpacetimeDB modules

When you connect, Studio can help make a module's working state easier to understand. Inspect the schema, see table rows, export data, run SQL, call reducers and follow logs. These views can help you understand how the server behaves while you develop, test or diagnose an issue.

Because the same workflow works across local, Maincloud and self-hosted connections, you can build a clearer picture of how a change differs between environments. Keep production connections read-only when you only need to investigate, and use the server's own authentication controls to decide who can connect.

Spacetime Studio is free and open source under the MIT license. Explore the source on GitHub, or download the Windows installer to get started.

Frequently asked questions

Can I save multiple SpacetimeDB connections?

Yes. Save connections for different servers and databases, such as local development, staging and production, and switch between them in Studio.

Can everyone on my team use Spacetime Studio?

Yes. Each teammate can install the app and connect with their own credentials. Saved credentials stay in the operating system keychain on that person's device; Studio does not provide centrally shared team accounts or connection management.

Does Spacetime Studio deploy my module to Maincloud or Railway?

No. Studio is a database GUI for connecting to and inspecting SpacetimeDB servers. Use the SpacetimeDB CLI and your hosting provider's tools to deploy the server and publish modules.

Can I use it with local and self-hosted servers?

Yes. Studio supports local SpacetimeDB and remote self-hosted servers, as well as Maincloud. For a remote host, provide a reachable server URL and the database details and credentials needed to connect.