How Spacetime stacks up against the databases and backends you might be weighing it against.
Comparing the reactive backends. Same programming model, much faster, usually cheaper.
Comparing Spacetime’s realtime application runtime with Postgres’s traditional relational model
Comparing Spacetime’s unified engine to Supabase’s layered Postgres services.
| Feature | Spacetime | Convex | Postgres | Supabase |
|---|---|---|---|---|
| Max transactions per secondTransfer benchmark, single machine | ~300k | ~1k | ~11k | ~7k |
| Data model | Relational tables and SQL | Documents, optional schemas | Relational tables and SQL | Relational tables and SQL |
| Where your server logic runs | Inside the database | A separate function service | Stored procedures, or external services | Edge Functions, outside the database |
| Server languages | TypeScript, Rust, C#, C++ | TypeScript, JavaScript | SQL and stored procedure languages | SQL, plus Edge Functions |
| ACID transactions | ||||
| Self-hosted or managed cloud | ||||
| Built-in authentication | ||||
| Live queries pushed to clients | Change listeners added in client code |