Version modules and client changes
Connect
SPIRITT
SpacetimeDBBuild together.
Stay in sync.
SPIRITT builds applications around SpacetimeDB's shared state, server-side logic, and live subscriptions, so teams and players work from the same changing picture.
What you can do with SpacetimeDB.
Share live state
Connect clients to the database rows their screens need. Subscriptions deliver the initial result and subsequent changes instead of making every view repeatedly poll for updates.
Keep actions consistent
Put business rules in server-side module functions and validate each state change. Transactional reducers help keep concurrent actions consistent rather than trusting individual clients.
Ship the whole experience
Build the interface, database module, generated client bindings, and access rules together. Verify synchronization and reconnect behavior with independent clients before release.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Create a SPIRITT workspace for your multiplayer product, collaborative tool, or live operating system.
02
Connect SpacetimeDB
Authorize the intended SpacetimeDB account and database, or configure your self-hosted instance. Define the data, identities, and roles your application needs.
03
Build and verify
Describe the shared experience. SPIRITT builds its module and clients, tests the rules across multiple sessions, and prepares the application for deployment.
Hand over a mission.
Choose a mission. Make it yours.
Put SpacetimeDB to work.
Build applications that move together
Questions
SpacetimeDB, with SPIRITT.
01What makes SpacetimeDB different from a database behind an API?+
SpacetimeDB lets you put application data and server-side module logic in the same system. Clients can invoke module functions and subscribe to query results through its SDKs. SPIRITT builds the module, client interface, and surrounding integrations as one application workflow.
02Is it only useful for multiplayer games?+
No. Multiplayer games are one fit, but shared task boards, support queues, booking capacity, live polls, and dispatch tools also depend on consistent state across multiple clients. The page's examples apply those capabilities to both products and business operations.
03Does every client receive the whole database?+
No. Clients subscribe to queries that define the rows they need, and receive an initial result followed by updates. The application must also implement the appropriate table visibility, identity checks, and access rules; a filtered interface is not itself an authorization boundary.
04How are concurrent actions kept consistent?+
Reducers execute inside database transactions. The module can validate a caller and the current state before applying an action, such as claiming a task or reserving remaining capacity. SPIRITT implements those rules and tests competing clients; business-specific conflict resolution is not assumed to be automatic.
05Can the app still use other services?+
Yes. SPIRITT can connect the application to tools such as Slack, GitHub, or Google Sheets. External side effects need an appropriate worker or supported procedure boundary rather than being treated as part of a reducer transaction. The design keeps database outcomes and external delivery status distinct.
06How will deployment and later changes work?+
SpacetimeDB supports managed Maincloud deployment and self-hosted operation. SPIRITT can build and publish modules, generate client bindings, and inspect logs and schema information using the configured access. Compatible schema updates and changes requiring a migration plan are handled differently; data deletion is not used as a routine deployment shortcut.