A desktop GUI for SpacetimeDB.

Stargate is a desktop client for SpacetimeDB. You can browse tables, inspect the schema, call reducers, stream logs, run SQL, watch live data, and manage scheduled tasks.

Stargate runs on macOS, Windows, and Linux as a native app. There is no separate runtime to install.

Stargate isn't notarized by Apple yet, so macOS blocks it on first launch. To open it anyway: double-click Stargate, and in the warning click Done (do not move it to the Trash). Then open System Settings → Privacy & Security and scroll down to the Security section. You'll see a message that "Stargate" was blocked, with an Open Anyway button next to it — click it, then enter your login password to confirm. The app launches and is saved as an exception, so afterwards you can open it normally by double-clicking. On macOS Sequoia and later the old right-click → Open shortcut no longer works; you have to use the Open Anyway button in Privacy & Security, which stays available for about an hour after you try to launch the app.

The installer isn't code-signed yet, so Microsoft Defender SmartScreen warns about it. The download is safe to run: when the "Windows protected your PC" dialog appears, click the More info link, then click the Run anyway button that appears, and the installer continues. If Run anyway doesn't show, right-click the downloaded .exe, choose Properties, tick Unblock in the Security section at the bottom of the General tab, click OK, then run it again.

Reading is free. A per-device license unlocks read-write mode for mutating reducers and write SQL. You can connect, browse, and query without paying.

Stargate talks to SpacetimeDB's HTTP and WebSocket API. Sign in with your CLI credentials or a token, pick a server and database, and connect. There is nothing extra to deploy.

Yes. Stargate connects to any SpacetimeDB host. Point it at a database on Maincloud, at a server you self-host, or at a local instance on localhost while you develop. You just enter the server URL and sign in.

For everyday inspection it can be. Stargate covers what you would otherwise run through commands like spacetime sql, call, describe, and logs, in a visual window. You still use the CLI to publish modules.

Stargate talks straight to your SpacetimeDB host. Credentials and saved logins stay on your machine, and connections default to read-only, so a write only happens when you choose it.

Download Stargate, connect to your database, and open the Tables view. You get a visual table browser for any SpacetimeDB database, so you can page through rows, filter them, and read the schema without typing a single spacetime command.

In Stargate, enter the URL of your self-hosted SpacetimeDB server, sign in with your CLI credentials or a token, and choose a database. The same flow works for a server on localhost during development and for a production server you host yourself.

Yes. Stargate is a desktop graphical client that connects to databases on SpacetimeDB Maincloud, the managed cloud. Sign in with your existing Maincloud login, pick a database, and browse it, run SQL, and watch live data from one window.

Open the SQL console in Stargate, type your query, and run it against the connected database. Results appear in a table you can read, scroll, and export to CSV or JSON. Read queries work for free; write SQL needs a read-write license.

Use the reducer console. Pick the reducer by name, fill in its typed arguments, and call it to reproduce a bug or seed test data, without writing a throwaway client. Reducers that mutate state require read-write mode.

Open the Logs view and turn on follow mode. Stargate streams new log lines as they arrive, with levels highlighted, so you can watch reducer output, panics, and timeouts live while you develop your module.

Browse the table or run a SQL query, then use the export action to save the rows as a CSV or JSON file through the native save dialog. It is handy for sharing data, attaching it to a bug report, or analysing it elsewhere.

Yes. Stargate talks to SpacetimeDB over its HTTP and WebSocket API, so it doesn't care which language your module is written in. Whether your tables and reducers are defined in Rust, C#, TypeScript, or C++, Stargate reads the live schema from the host and shows the same tables, reducers, and logs.

Yes. Stargate connects to the database your game talks to, not to the game engine, so it works alongside any Unity, Unreal, or custom client. While you playtest, watch the live view to see rows change as players connect and move, and call reducers by hand to reproduce bugs.

Yes. The table browser lets you page through rows and filter them without typing a query, so you don't need to write SQL to inspect your data. When you do want SQL, the SQL console is there for ad-hoc queries.

Point Stargate at the instance's URL. For a local server started with spacetime start or a Docker container, that's usually http://localhost:3000. Sign in with your CLI credentials or a token, choose the database, and connect. The same flow works for a remote self-hosted server.

Yes. Instead of deploying and hosting a separate web dashboard, Stargate is a native desktop app you download and point at any SpacetimeDB host. There's no extra service to run; it connects straight to Maincloud, a self-hosted server, or localhost.

Yes. SpacetimeDB powers chat apps, collaboration tools, dashboards, and IoT backends as well as games, and Stargate works with any of them. If your data lives in a SpacetimeDB database, you can browse it, query it, and watch it update live.

Yes. Save each server and database once, then switch between them in a click, which helps when a match- or room-based architecture spins up many SpacetimeDB instances. Each saved connection keeps its own login, so you don't retype credentials.

Stargate is source available — the full source code is published on GitHub so you can read it, audit it, and build from it.