clockworklabs/SpacetimeDBPublic

Development at the speed of light

AI summary: A unified platform merging relational databases and application servers via WebAssembly for ultra-low latency apps.

Stars
25.6K
+16 today
Forks
1.1K
Watchers
90
Open issues
793
Open PRs
186
Contributors
~133
Commits
3.9K
Branches
1.8K

RustOtherCreated Jun 17, 2023Last push 2d agoLatest release v2.15.0+28 stars this week+250 this month

Quick answers

What is SpacetimeDB?
A unified platform merging relational databases and application servers via WebAssembly for ultra-low latency apps.
What does SpacetimeDB do?
SpacetimeDB radically merges the traditional relational database layer directly with the application logic layer, compiling everything seamlessly into WebAssembly. This highly innovative architecture completely eliminates the absolute need for separate, complex backend servers and databases, entirely removing network latency between the app tier and data tier. By running the critical application code directly alongside the stored data in the exact same process space, it consistently delivers incredible microsecond latency. It is particularly targeted at empowering multiplayer games and highly real-time collaboration applications that demand massive speed. Developers simply write their backend logic as highly modular server-side functions that are automatically and instantly exposed to clients with real-time state synchronization.
Who is SpacetimeDB for?
SpacetimeDB is built for dedicated game developers, advanced backend engineers, and expert full-stack developers actively building incredibly real-time, stateful applications. The platform simplifies complex workflows and accelerates development timelines.
How do I get started with SpacetimeDB?
spacetime server start
How popular is SpacetimeDB on GitHub?
clockworklabs/SpacetimeDB has 25,566 stars and 1,121 forks on GitHub, and gained 28 stars in the last 7 days.
What license does SpacetimeDB use?
clockworklabs/SpacetimeDB is released under the Other license.

Star history

since Jul 30, 2023
010K20KJul 2023Aug 2024Oct 2025Nov 2026
25.6K stars as of Nov 18, 2026. Before Jul 29, 2026, reconstructed from public GitHub event archives (checked against the repository's real star total); since then measured daily.

Update history

5 recorded
  • Nov 18, 2026New release v2.15.0 (previously v2.14.1).
  • Nov 7, 2026New release v2.14.1 (previously v2.13.0).
  • Oct 28, 2026New release v2.13.0 (previously v2.12.0).
  • Oct 17, 2026New release v2.12.0 (previously v2.11.0).
  • Oct 8, 2026New release v2.11.0 (previously v2.10.1).

Contribution activity

commits per day, last 52 weeks
NovDecJanFebMarAprMayJunJulAugSepOctNovMonWedFri2025-11-23: 0 commits2025-11-24: 12 commits2025-11-25: 8 commits2025-11-26: 12 commits2025-11-27: 1 commit2025-11-28: 0 commits2025-11-29: 0 commits2025-11-30: 0 commits2025-12-01: 3 commits2025-12-02: 9 commits2025-12-03: 2 commits2025-12-04: 10 commits2025-12-05: 3 commits2025-12-06: 0 commits2025-12-07: 1 commit2025-12-08: 1 commit2025-12-09: 7 commits2025-12-10: 6 commits2025-12-11: 2 commits2025-12-12: 1 commit2025-12-13: 0 commits2025-12-14: 0 commits2025-12-15: 0 commits2025-12-16: 8 commits2025-12-17: 8 commits2025-12-18: 8 commits2025-12-19: 5 commits2025-12-20: 0 commits2025-12-21: 1 commit2025-12-22: 0 commits2025-12-23: 1 commit2025-12-24: 0 commits2025-12-25: 0 commits2025-12-26: 0 commits2025-12-27: 0 commits2025-12-28: 0 commits2025-12-29: 1 commit2025-12-30: 5 commits2025-12-31: 2 commits2026-01-01: 0 commits2026-01-02: 1 commit2026-01-03: 0 commits2026-01-04: 0 commits2026-01-05: 0 commits2026-01-06: 8 commits2026-01-07: 1 commit2026-01-08: 3 commits2026-01-09: 6 commits2026-01-10: 0 commits2026-01-11: 2 commits2026-01-12: 7 commits2026-01-13: 12 commits2026-01-14: 11 commits2026-01-15: 4 commits2026-01-16: 7 commits2026-01-17: 1 commit2026-01-18: 0 commits2026-01-19: 1 commit2026-01-20: 6 commits2026-01-21: 3 commits2026-01-22: 7 commits2026-01-23: 8 commits2026-01-24: 0 commits2026-01-25: 0 commits2026-01-26: 6 commits2026-01-27: 9 commits2026-01-28: 7 commits2026-01-29: 5 commits2026-01-30: 10 commits2026-01-31: 0 commits2026-02-01: 1 commit2026-02-02: 4 commits2026-02-03: 8 commits2026-02-04: 4 commits2026-02-05: 10 commits2026-02-06: 4 commits2026-02-07: 1 commit2026-02-08: 0 commits2026-02-09: 1 commit2026-02-10: 10 commits2026-02-11: 23 commits2026-02-12: 19 commits2026-02-13: 9 commits2026-02-14: 1 commit2026-02-15: 1 commit2026-02-16: 8 commits2026-02-17: 9 commits2026-02-18: 15 commits2026-02-19: 16 commits2026-02-20: 14 commits2026-02-21: 2 commits2026-02-22: 1 commit2026-02-23: 18 commits2026-02-24: 12 commits2026-02-25: 7 commits2026-02-26: 13 commits2026-02-27: 4 commits2026-02-28: 2 commits2026-03-01: 3 commits2026-03-02: 6 commits2026-03-03: 13 commits2026-03-04: 8 commits2026-03-05: 6 commits2026-03-06: 3 commits2026-03-07: 3 commits2026-03-08: 0 commits2026-03-09: 2 commits2026-03-10: 4 commits2026-03-11: 10 commits2026-03-12: 3 commits2026-03-13: 4 commits2026-03-14: 1 commit2026-03-15: 0 commits2026-03-16: 2 commits2026-03-17: 3 commits2026-03-18: 2 commits2026-03-19: 10 commits2026-03-20: 10 commits2026-03-21: 4 commits2026-03-22: 1 commit2026-03-23: 3 commits2026-03-24: 2 commits2026-03-25: 2 commits2026-03-26: 1 commit2026-03-27: 1 commit2026-03-28: 0 commits2026-03-29: 0 commits2026-03-30: 3 commits2026-03-31: 0 commits2026-04-01: 3 commits2026-04-02: 0 commits2026-04-03: 1 commit2026-04-04: 1 commit2026-04-05: 0 commits2026-04-06: 4 commits2026-04-07: 2 commits2026-04-08: 2 commits2026-04-09: 2 commits2026-04-10: 1 commit2026-04-11: 1 commit2026-04-12: 0 commits2026-04-13: 4 commits2026-04-14: 8 commits2026-04-15: 12 commits2026-04-16: 5 commits2026-04-17: 4 commits2026-04-18: 1 commit2026-04-19: 0 commits2026-04-20: 2 commits2026-04-21: 10 commits2026-04-22: 11 commits2026-04-23: 7 commits2026-04-24: 2 commits2026-04-25: 0 commits2026-04-26: 0 commits2026-04-27: 6 commits2026-04-28: 7 commits2026-04-29: 4 commits2026-04-30: 8 commits2026-05-01: 2 commits2026-05-02: 0 commits2026-05-03: 0 commits2026-05-04: 6 commits2026-05-05: 3 commits2026-05-06: 4 commits2026-05-07: 4 commits2026-05-08: 5 commits2026-05-09: 2 commits2026-05-10: 0 commits2026-05-11: 4 commits2026-05-12: 1 commit2026-05-13: 4 commits2026-05-14: 1 commit2026-05-15: 0 commits2026-05-16: 1 commit2026-05-17: 0 commits2026-05-18: 3 commits2026-05-19: 1 commit2026-05-20: 3 commits2026-05-21: 4 commits2026-05-22: 5 commits2026-05-23: 1 commit2026-05-24: 0 commits2026-05-25: 0 commits2026-05-26: 1 commit2026-05-27: 3 commits2026-05-28: 7 commits2026-05-29: 3 commits2026-05-30: 0 commits2026-05-31: 0 commits2026-06-01: 6 commits2026-06-02: 14 commits2026-06-03: 3 commits2026-06-04: 6 commits2026-06-05: 4 commits2026-06-06: 0 commits2026-06-07: 0 commits2026-06-08: 2 commits2026-06-09: 7 commits2026-06-10: 4 commits2026-06-11: 7 commits2026-06-12: 6 commits2026-06-13: 2 commits2026-06-14: 4 commits2026-06-15: 7 commits2026-06-16: 11 commits2026-06-17: 5 commits2026-06-18: 5 commits2026-06-19: 2 commits2026-06-20: 1 commit2026-06-21: 1 commit2026-06-22: 3 commits2026-06-23: 6 commits2026-06-24: 1 commit2026-06-25: 1 commit2026-06-26: 6 commits2026-06-27: 1 commit2026-06-28: 2 commits2026-06-29: 7 commits2026-06-30: 4 commits2026-07-01: 4 commits2026-07-02: 4 commits2026-07-03: 1 commit2026-07-04: 1 commit2026-07-05: 0 commits2026-07-06: 0 commits2026-07-07: 3 commits2026-07-08: 7 commits2026-07-09: 2 commits2026-07-10: 3 commits2026-07-11: 0 commits2026-07-12: 0 commits2026-07-13: 2 commits2026-07-14: 4 commits2026-07-15: 4 commits2026-07-16: 4 commits2026-07-17: 2 commits2026-07-18: 0 commits2026-07-19: 0 commits2026-07-20: 0 commits2026-07-21: 5 commits2026-07-22: 2 commits2026-07-23: 2 commits2026-07-24: 2 commits2026-07-25: 0 commits2026-07-26: 0 commits2026-07-27: 4 commits2026-07-28: 6 commits2026-07-29: 1 commit2026-07-30: 1 commit2026-07-31: 4 commits2026-08-01: 0 commits2026-08-02: 2 commits2026-08-03: 7 commits2026-08-04: 3 commits2026-08-05: 5 commits2026-08-06: 3 commits2026-08-07: 1 commit2026-08-08: 3 commits2026-08-09: 1 commit2026-08-10: 3 commits2026-08-11: 7 commits2026-08-12: 4 commits2026-08-13: 5 commits2026-08-14: 3 commits2026-08-15: 1 commit2026-08-16: 0 commits2026-08-17: 1 commit2026-08-18: 1 commit2026-08-19: 1 commit2026-08-20: 0 commits2026-08-21: 4 commits2026-08-22: 1 commit2026-08-23: 0 commits2026-08-24: 5 commits2026-08-25: 6 commits2026-08-26: 5 commits2026-08-27: 4 commits2026-08-28: 0 commits2026-08-29: 0 commits2026-08-30: 0 commits2026-08-31: 3 commits2026-09-01: 4 commits2026-09-02: 4 commits2026-09-03: 6 commits2026-09-04: 2 commits2026-09-05: 0 commits2026-09-06: 0 commits2026-09-07: 0 commits2026-09-08: 0 commits2026-09-09: 3 commits2026-09-10: 6 commits2026-09-11: 2 commits2026-09-12: 2 commits2026-09-13: 1 commit2026-09-14: 1 commit2026-09-15: 1 commit2026-09-16: 1 commit2026-09-17: 1 commit2026-09-18: 1 commit2026-09-19: 0 commits2026-09-20: 0 commits2026-09-21: 2 commits2026-09-22: 3 commits2026-09-23: 1 commit2026-09-24: 6 commits2026-09-25: 1 commit2026-09-26: 2 commits2026-09-27: 2 commits2026-09-28: 1 commit2026-09-29: 4 commits2026-09-30: 4 commits2026-10-01: 2 commits2026-10-02: 2 commits2026-10-03: 0 commits2026-10-04: 0 commits2026-10-05: 4 commits2026-10-06: 6 commits2026-10-07: 5 commits2026-10-08: 5 commits2026-10-09: 2 commits2026-10-10: 1 commit2026-10-11: 1 commit2026-10-12: 1 commit2026-10-13: 6 commits2026-10-14: 8 commits2026-10-15: 8 commits2026-10-16: 5 commits2026-10-17: 0 commits2026-10-18: 0 commits2026-10-19: 3 commits2026-10-20: 3 commits2026-10-21: 3 commits2026-10-22: 3 commits2026-10-23: 2 commits2026-10-24: 0 commits2026-10-25: 1 commit2026-10-26: 1 commit2026-10-27: 2 commits2026-10-28: 2 commits2026-10-29: 3 commits2026-10-30: 6 commits2026-10-31: 0 commits2026-11-01: 2 commits2026-11-02: 5 commits2026-11-03: 4 commits2026-11-04: 5 commits2026-11-05: 6 commits2026-11-06: 10 commits2026-11-07: 0 commits2026-11-08: 0 commits2026-11-09: 3 commits2026-11-10: 3 commits2026-11-11: 4 commits2026-11-12: 5 commits2026-11-13: 0 commits2026-11-14: 0 commits2026-11-15: 0 commits2026-11-16: 4 commits2026-11-17: 2 commits2026-11-18: 2 commits2026-11-19: 0 commits2026-11-20: 0 commits2026-11-21: 0 commits
1,221 commits in the last yearLessMore

Signals and awards

derived from tracked data
  • Widely adopted

    25,566 stars

  • Very active

    1,221 commits in 52 weeks

  • Community-driven

    ~133 contributors

  • Continuous integration

    Automated checks passing

What SpacetimeDB does

SpacetimeDB radically merges the traditional relational database layer directly with the application logic layer, compiling everything seamlessly into WebAssembly. This highly innovative architecture completely eliminates the absolute need for separate, complex backend servers and databases, entirely removing network latency between the app tier and data tier. By running the critical application code directly alongside the stored data in the exact same process space, it consistently delivers incredible microsecond latency. It is particularly targeted at empowering multiplayer games and highly real-time collaboration applications that demand massive speed. Developers simply write their backend logic as highly modular server-side functions that are automatically and instantly exposed to clients with real-time state synchronization.

SpacetimeDB is built for dedicated game developers, advanced backend engineers, and expert full-stack developers actively building incredibly real-time, stateful applications. The platform simplifies complex workflows and accelerates development timelines.

  • Unified Architecture: Completely combines the complex application server and the massive database into a single, highly cohesive execution engine.
  • WebAssembly Runtime: Rapidly executes user-provided business logic compiled directly to WASM for incredibly high performance, deep portability, and strong security.
  • Zero Network Overhead: Entirely eliminates the typical, massive latency associated with querying a traditional database from an entirely separate external server.
  • Real-Time Subscriptions: Actively allows connected clients to easily subscribe to complex database queries and rapidly receive instant structural data updates.
  • Multi-Language Support: Empoweringly enables developers to write rapid server logic in popular, typed languages like Rust, C#, and TypeScript.
  • ACID Compliant: Strictly maintains traditional, highly rigid relational database transaction guarantees while simultaneously acting as a blazing fast web server.

Where teams use it

Multiplayer Game Backends

Dramatically simplifies complex backend development for highly real-time multiplayer games by seamlessly handling both volatile state and core logic in one place.

Real-Time Collaborative Apps

Efficiently powers highly interactive applications like massive document editors or dense whiteboards that absolutely require instant state synchronization across clients.

High-Frequency Trading Platforms

Heavily leverages the incredible microsecond latency to effectively build ultra-fast, massively concurrent financial and dense trading systems.

Serverless Edge Applications

Actively acts as a highly capable edge database and dense compute layer combined, massively reducing overall deployment complexity and infrastructure costs.

Getting started: spacetime server start

README

master branch

SpacetimeDB Logo SpacetimeDB Logo

SpacetimeDB SpacetimeDB

Development at the speed of light.

         

   

     

Discord   Twitter   GitHub   Twitch   YouTube   LinkedIn   StackOverflow


What is SpacetimeDB?

SpacetimeDB is a relational database that is also a server. You upload your application logic directly into the database, and clients connect to it without any server in between. It is built for reactive applications, where every client sees changes as they happen: web apps like collaborative tools, dashboards, and chat, as well as multiplayer games.

Write your schema and business logic as a module in Rust, C#, TypeScript, or C++. SpacetimeDB compiles it, runs it inside the database, and automatically synchronizes state to connected clients in real-time.

Instead of deploying a web or game server that sits in between your clients and your database, your clients connect directly to the database and execute your application logic in your module. You can write all of your permission and authorization logic right inside your module just as you would in a normal server.

This means that you can write your entire application in a single language and deploy it as a single binary. No more separate webserver, no more containers, no more Kubernetes, no more VMs, no more DevOps, no more caching later. Zero infrastructure to manage.

SpacetimeDB Architecture

SpacetimeDB application architecture
(elements in white are provided by SpacetimeDB)

SpacetimeDB is optimized for maximum speed and minimum latency. SpacetimeDB provides all the ACID guarantees of a traditional RDBMS, with all the speed of an optimized web server. Hot data stays in memory for fast access and colder data lives on disk, while a commit log provides durability and crash recovery. The entire backend of our MMORPG BitCraft Online runs as a single SpacetimeDB module: chat, items, terrain, player positions, everything, synchronized to thousands of players in real-time.

Quick Start

1. Install

# macOS / Linux
curl -sSf https://install.spacetimedb.com | sh

# Windows (PowerShell)
iwr https://windows.spacetimedb.com -useb | iex

2. Log in

spacetime login

This opens a browser to authenticate with GitHub. Your identity is linked to your account so you can publish databases.

3. Start developing

spacetime dev --template chat-react-ts

That is it. This creates a project from a template, publishes it to Maincloud, and watches for file changes, automatically rebuilding and republishing on save. See pricing for details.

How It Works

SpacetimeDB modules define tables (your data) and reducers (your logic). Clients connect, call reducers, and subscribe to tables. When data changes, SpacetimeDB pushes updates to subscribed clients automatically.

// Define a table
#[spacetimedb::table(accessor = messages, public)]
pub struct Message {
    #[primary_key]
    #[auto_inc]
    id: u64,
    sender: Identity,
    text: String,
}

// Define a reducer (your API endpoint)
#[spacetimedb::reducer]
pub fn send_message(ctx: &ReducerContext, text: String) {
    ctx.db.messages().insert(Message {
        id: 0,
        sender: ctx.sender,
        text,
    });
}

On the client side, subscribe and get live updates:

const [messages] = useTable(tables.message);
// messages updates automatically when the server state changes.
// No polling. No refetching.

Use Cases

SpacetimeDB is well suited to web application backends, from everyday CRUD apps to reactive ones like collaborative tools, live dashboards, and chat. Write your module in TypeScript and connect from the browser with the TypeScript SDK, which includes React hooks like useTable and integrations for Vue, Svelte, Angular, and other frameworks. Each reducer runs as an ACID transaction, and subscribed clients receive committed changes automatically, so you don't need polling, a separate API server, or a pub/sub layer to keep them in sync. The chat-react-ts template from the Quick Start is a working example.

SpacetimeDB is optimized for low-latency transactional workloads like these, rather than batch processing or analytical queries.

Durability

Every transaction that changes data is written to an on-disk commitlog, which is replayed to recover the database after a crash. Transactions are fsynced in batches, so many transactions share a single fsync (group commit) (local.rs).

Since SpacetimeDB 2.0, clients get confirmed reads by default: the server holds back a transaction's subscription updates, and the caller's reducer result, until that transaction is durable (client_connection.rs), so the data a client receives from its subscriptions and reducer calls will survive a crash. SQL queries over HTTP wait for durability by default too. On Maincloud and other replicated deployments, durable instead means persisted by the replicas the database's replication settings require. Apps that can tolerate a client occasionally seeing a write that is then lost in a crash, like many games, can opt out with withConfirmedReads(false) for lower latency.

Language Support

Server Modules

Write your database logic in any of these languages:

Language Quickstart
Rust Get started
C# Get started
TypeScript Get started
C++ Get started

Client SDKs

Connect from any of these platforms:

SDK Quickstart
TypeScript (React, Next.js, Vue, Svelte, Angular, Node.js, Bun, Deno) Get started
Rust Get started
C# (standalone and Unity) Get started
C++ (Unreal Engine) Get started

Running with Docker

docker run --rm --pull always -p 3000:3000 clockworklabs/spacetime start

Building from Source

If you need features from master that have not been released yet:

# Prerequisites: Rust toolchain with wasm32-unknown-unknown target
curl https://sh.rustup.rs -sSf | sh

git clone https://github.com/clockworklabs/SpacetimeDB
cd SpacetimeDB
cargo build --locked --release -p spacetimedb-standalone -p spacetimedb-update -p spacetimedb-cli

Then install the binaries:

macOS / Linux
mkdir -p ~/.local/bin
STDB_VERSION="$(./target/release/spacetimedb-cli --version | sed -n 's/.*spacetimedb tool version \([0-9.]*\);.*/\1/p')"
mkdir -p ~/.local/share/spacetime/bin/$STDB_VERSION

cp target/release/spacetimedb-update ~/.local/bin/spacetime
cp target/release/spacetimedb-cli ~/.local/share/spacetime/bin/$STDB_VERSION
cp target/release/spacetimedb-standalone ~/.local/share/spacetime/bin/$STDB_VERSION

# Add to your shell config if not already present:
export PATH="$HOME/.local/bin:$PATH"

# Set the active version:
spacetime version use $STDB_VERSION
Windows (PowerShell)
$stdbDir = "$HOME\AppData\Local\SpacetimeDB"
$stdbVersion = & ".\target\release\spacetimedb-cli" --version |
    Select-String -Pattern 'spacetimedb tool version ([0-9.]+);' |
    ForEach-Object { $_.Matches.Groups[1].Value }
New-Item -ItemType Directory -Path "$stdbDir\bin\$stdbVersion" -Force | Out-Null

Copy-Item "target\release\spacetimedb-update.exe" "$stdbDir\spacetime.exe"
Copy-Item "target\release\spacetimedb-cli.exe" "$stdbDir\bin\$stdbVersion\"
Copy-Item "target\release\spacetimedb-standalone.exe" "$stdbDir\bin\$stdbVersion\"

# Add to your system PATH: %USERPROFILE%\AppData\Local\SpacetimeDB
# Then in a new shell:
spacetime version use $stdbVersion

Verify with spacetime --version.

To find your way around the code, see the architecture diagram of what runs inside SpacetimeDB Standalone.

Documentation

To set up a coding agent such as Claude Code, Codex, or Cursor, paste this prompt into it. It points the agent to the agent setup guide.

Set yourself up to build with Spacetime (SpacetimeDB).

1. Read https://spacetimedb.com/agent-setup.md carefully, in full rather than a summary, and follow it. Run the commands yourself, and ask me only for approvals, logins, or restarts.
2. Read https://spacetimedb.com/docs/intro/misconceptions/ carefully, in full. Spacetime has changed a lot, so what you remember about it, and older articles online, may be out of date. When you describe Spacetime or compare it with other backends, go by the current docs.
3. Tell me what you installed, what you verified, and anything I still need to do.

Full documentation is available at spacetimedb.com/docs, including:

License

SpacetimeDB is licensed under the Business Source License 1.1 (BSL). It converts to the AGPL v3.0 with a linking exception after a few years. The linking exception means you are not required to open-source your own code if you use SpacetimeDB. You only need to contribute back changes to SpacetimeDB itself.

Why did we choose this license? We chose to license SpacetimeDB under the MariaDB Business Source License for 4 years because we can't compete with AWS while also building our products for them.

We chose GPLv3 with linking exception as the open source license because we want contributions merged back into mainline (just like Linux), but we don't want to make anyone else open source their own code (i.e. linking exception).

View on GitHub

Recent activity

commits and pull requests

Releases and announcements

70 total
  1. Release v2.15.0v2.15.0Nov 10, 202616.5K downloads

    ## Features ### New TypeScript module packages Four new opt-in TypeScript packages are available for SpacetimeDB modules, each with documentation, tests, and examples: - **Agents**: provider adapters, tool calls, conversation summaries, embeddings, and stale-lock cleanup. - **Auth**: password and OAuth handlers, ES256 sessions, connection binding, and profiles. - **Files**: upload, listing, deletion, per-file visibility, and HTTP serving helpers. - **PostHog**: server-side analytics and feature-flag evaluation, with durable queued events and explicit batch flushing. ([#5905](<https://github.com/clockworklabs/SpacetimeDB/pull/5905>), [#5907](<https://github.com/clockworklabs/SpacetimeDB/pull/5907>)) ### Rust `outbox!` shorthand for async IDC Rust modules can now declare an outbox table with `spacetimedb::outbox!(receiver::reducer)`, which generates the message ID, target, and reducer argument columns from the module bindings. Optional `accessor` and `name` arguments are supported; manual `#[spacetimedb::table(...)]` declarations remain available. ([#6460](<https://github.com/clockworklabs/SpacetimeDB/pull/6460>)) ## Breaking Changes ### C# module build:

  2. Release v2.14.1v2.14.1Nov 4, 202614.8K downloads

    ## Bug Fixes ### Refresh TLS trust following the eMudhra/emSign CA incident Updated TLS certificate verification dependencies and refreshed certificate trust stores in distributed container images to address the eMudhra/emSign certificate authority key compromise. The updated WebPKI verifier rejects the compromised intermediate keys, and affected roots are removed from the Nix development environment's CA bundle. Operators should upgrade their SpacetimeDB binaries and container images. See the [RustSec advisory](<https://rustsec.org/advisories/RUSTSEC-2026-0382.html>) for details about the upstream incident. ([#6366](<https://github.com/clockworklabs/SpacetimeDB/pull/6366>)) ### Preserve UUID and branded primitive types in TypeScript TypeScript type inference now preserves `Uuid` values and branded primitives instead of expanding them into structural records. UUID columns retain their `Uuid` type, and branded strings remain assignable to `string`. This is a types-only fix with no runtime behavior change. ([#5971](<https://github.com/clockworklabs/SpacetimeDB/pull/5971>)) ### Restore Nix development builds Updated the Nix flake to Rust 1.97.1 and pinned th

  3. Release v2.14.0v2.14.0Oct 30, 202619.9K downloads

    ## New Features ### 🚀 Async inter-database communication 🚀 Rust and TypeScript modules can now call reducers in other databases asynchronously through declared dependencies and generated receiver bindings. A module declares its dependencies in `spacetime.json`, referencing either a local module path or a published database, and `spacetime generate` produces typed receiver bindings for each dependency, while `spacetime dev` publishes dependency databases alongside the main one. Senders enqueue calls by inserting rows into generated outbox tables, which are insert-only and map their columns to the receiver's reducer parameters with compile-time type checking. Delivery is handled by a new IDC actor that manages concurrent outbox streams over HTTP/2, and optional `on_result` / `onResult` callbacks report delivery outcomes back to the sender. Dependencies are namespaced by name, so a module can depend on two databases that export identically named types. Note: C# and C++ Async IDC are coming in a future release. ([#6156](<https://github.com/clockworklabs/SpacetimeDB/pull/6156>), [#6313](<https://github.com/clockworklabs/SpacetimeDB/pull/6313>), [#6364](<https://github.

  4. Release v2.13.0v2.13.0Oct 21, 202629.6K downloads

    ## New Features ### Reusable TypeScript submodules TypeScript modules can now use a collection of reusable submodules for common application needs. The initial packages provide cron-style and interval scheduling, retry with exponential backoff, fixed-window rate limiting, cryptographic and encoding helpers, and Resend email integration. The packages include typed APIs, installation documentation, tests, and examples. They can be installed in projects using SpacetimeDB 2.12 or later. ([#5903](<https://github.com/clockworklabs/SpacetimeDB/pull/5903>), [#6158](<https://github.com/clockworklabs/SpacetimeDB/pull/6158>), [#6309](<https://github.com/clockworklabs/SpacetimeDB/pull/6309>)) ### C# module submodules and namespaces C# modules can now compose separately built module assemblies as submodules. Assembly-level namespace declarations control how a dependency is exposed in C# and, optionally, its canonical database namespace. Namespaced tables, indexes, views, query builders, reducers, procedures, schedules, generated clients, subscriptions, and row-level security are supported. A module assembly can be published independently or referenced as a dependency withou

  5. Release v2.12.0v2.12.0Oct 13, 202637.3K downloads

    ## New Features ### Persistent typed database environments SpacetimeDB modules can now declare typed environment variables for configuration and secrets. Rust, TypeScript, C#, and C++ modules can read declared values through their execution context, with support for required and optional strings as well as constrained sets of allowed values. Values can come from project configuration or the publishing process's environment. They are validated against the module's declarations and updated atomically with a module publish. Stored values are preserved by default across publishes, while `--env-only`, `--unset-env`, and `--replace-env` support configuration changes without replacing the module. Authorized users can inspect published values with `spacetime env get` and `spacetime env list`. ([#5887](<https://github.com/clockworklabs/SpacetimeDB/pull/5887>), [#5961](<https://github.com/clockworklabs/SpacetimeDB/pull/5961>), [#6004](<https://github.com/clockworklabs/SpacetimeDB/pull/6004>)) ### Automatic reconnect for TypeScript and C# clients The TypeScript and C# SDKs can now keep a `DbConnection`, its client cache, subscriptions, table handles, and registered callbacks

Code frequency

additions and deletions
+178.5K-178.5KWeek of 2025-11-23: +35,658 linesWeek of 2025-11-23: -28,733 linesWeek of 2025-11-30: +7,060 linesWeek of 2025-11-30: -1,536 linesWeek of 2025-12-07: +25,331 linesWeek of 2025-12-07: -23,040 linesWeek of 2025-12-14: +35,549 linesWeek of 2025-12-14: -28,228 linesWeek of 2025-12-21: +25,890 linesWeek of 2025-12-21: -25,601 linesWeek of 2025-12-28: +9,196 linesWeek of 2025-12-28: -806 linesWeek of 2026-01-04: +69,661 linesWeek of 2026-01-04: -8,076 linesWeek of 2026-01-11: +42,045 linesWeek of 2026-01-11: -24,571 linesWeek of 2026-01-18: +47,623 linesWeek of 2026-01-18: -33,861 linesWeek of 2026-01-25: +20,872 linesWeek of 2026-01-25: -7,289 linesWeek of 2026-02-01: +61,381 linesWeek of 2026-02-01: -11,458 linesWeek of 2026-02-08: +178,529 linesWeek of 2026-02-08: -36,505 linesWeek of 2026-02-15: +78,523 linesWeek of 2026-02-15: -22,996 linesWeek of 2026-02-22: +36,759 linesWeek of 2026-02-22: -41,028 linesWeek of 2026-03-01: +9,468 linesWeek of 2026-03-01: -3,879 linesWeek of 2026-03-08: +7,151 linesWeek of 2026-03-08: -1,504 linesWeek of 2026-03-15: +14,292 linesWeek of 2026-03-15: -19,737 linesWeek of 2026-03-22: +12,675 linesWeek of 2026-03-22: -7,022 linesWeek of 2026-03-29: +375 linesWeek of 2026-03-29: -55 linesWeek of 2026-04-05: +1,890 linesWeek of 2026-04-05: -3,813 linesWeek of 2026-04-12: +5,178 linesWeek of 2026-04-12: -2,726 linesWeek of 2026-04-19: +8,826 linesWeek of 2026-04-19: -6,584 linesWeek of 2026-04-26: +9,886 linesWeek of 2026-04-26: -8,529 linesWeek of 2026-05-03: +5,776 linesWeek of 2026-05-03: -5,289 linesWeek of 2026-05-10: +13,868 linesWeek of 2026-05-10: -46,537 linesWeek of 2026-05-17: +8,306 linesWeek of 2026-05-17: -1,006 linesWeek of 2026-05-24: +11,637 linesWeek of 2026-05-24: -1,641 linesWeek of 2026-05-31: +26,109 linesWeek of 2026-05-31: -3,425 linesWeek of 2026-06-07: +25,114 linesWeek of 2026-06-07: -3,974 linesWeek of 2026-06-14: +58,051 linesWeek of 2026-06-14: -18,271 linesWeek of 2026-06-21: +6,804 linesWeek of 2026-06-21: -1,588 linesWeek of 2026-06-28: +12,805 linesWeek of 2026-06-28: -844 linesWeek of 2026-07-05: +3,007 linesWeek of 2026-07-05: -560 linesWeek of 2026-07-12: +5,484 linesWeek of 2026-07-12: -1,250 linesWeek of 2026-07-19: +3,540 linesWeek of 2026-07-19: -2,549 linesWeek of 2026-07-26: +1,256 linesWeek of 2026-07-26: -616 linesWeek of 2026-08-02: +14,917 linesWeek of 2026-08-02: -4,192 linesWeek of 2026-08-09: +16,128 linesWeek of 2026-08-09: -4,892 linesWeek of 2026-08-16: +11,867 linesWeek of 2026-08-16: -12,204 linesWeek of 2026-08-23: +3,249 linesWeek of 2026-08-23: -1,881 linesWeek of 2026-08-30: +4,551 linesWeek of 2026-08-30: -1,386 linesWeek of 2026-09-06: +2,049 linesWeek of 2026-09-06: -573 linesWeek of 2026-09-13: +12,828 linesWeek of 2026-09-13: -520 linesWeek of 2026-09-20: +5,669 linesWeek of 2026-09-20: -1,875 linesWeek of 2026-09-27: +6,506 linesWeek of 2026-09-27: -1,420 linesWeek of 2026-10-04: +21,702 linesWeek of 2026-10-04: -4,492 linesWeek of 2026-10-11: +84,465 linesWeek of 2026-10-11: -25,442 linesWeek of 2026-10-18: +53,338 linesWeek of 2026-10-18: -14,229 linesWeek of 2026-10-25: +10,991 linesWeek of 2026-10-25: -1,168 linesWeek of 2026-11-01: +43,957 linesWeek of 2026-11-01: -13,578 linesWeek of 2026-11-08: +9,585 linesWeek of 2026-11-08: -1,361 linesWeek of 2026-11-15: +17,276 linesWeek of 2026-11-15: -4,399 linesNov 23, 2025Nov 15, 2026
+1.2M lines added, -528.7K removed over the last year.

Commits per week

last 52 weeks
650Week of 2025-11-23: 33 commitsWeek of 2025-11-30: 27 commitsWeek of 2025-12-07: 18 commitsWeek of 2025-12-14: 29 commitsWeek of 2025-12-21: 2 commitsWeek of 2025-12-28: 9 commitsWeek of 2026-01-04: 18 commitsWeek of 2026-01-11: 44 commitsWeek of 2026-01-18: 25 commitsWeek of 2026-01-25: 37 commitsWeek of 2026-02-01: 32 commitsWeek of 2026-02-08: 63 commitsWeek of 2026-02-15: 65 commitsWeek of 2026-02-22: 57 commitsWeek of 2026-03-01: 42 commitsWeek of 2026-03-08: 24 commitsWeek of 2026-03-15: 31 commitsWeek of 2026-03-22: 10 commitsWeek of 2026-03-29: 8 commitsWeek of 2026-04-05: 12 commitsWeek of 2026-04-12: 34 commitsWeek of 2026-04-19: 32 commitsWeek of 2026-04-26: 27 commitsWeek of 2026-05-03: 24 commitsWeek of 2026-05-10: 11 commitsWeek of 2026-05-17: 17 commitsWeek of 2026-05-24: 14 commitsWeek of 2026-05-31: 33 commitsWeek of 2026-06-07: 28 commitsWeek of 2026-06-14: 35 commitsWeek of 2026-06-21: 19 commitsWeek of 2026-06-28: 23 commitsWeek of 2026-07-05: 15 commitsWeek of 2026-07-12: 16 commitsWeek of 2026-07-19: 11 commitsWeek of 2026-07-26: 16 commitsWeek of 2026-08-02: 24 commitsWeek of 2026-08-09: 24 commitsWeek of 2026-08-16: 8 commitsWeek of 2026-08-23: 20 commitsWeek of 2026-08-30: 19 commitsWeek of 2026-09-06: 13 commitsWeek of 2026-09-13: 6 commitsWeek of 2026-09-20: 15 commitsWeek of 2026-09-27: 15 commitsWeek of 2026-10-04: 23 commitsWeek of 2026-10-11: 29 commitsWeek of 2026-10-18: 14 commitsWeek of 2026-10-25: 15 commitsWeek of 2026-11-01: 32 commitsWeek of 2026-11-08: 15 commitsWeek of 2026-11-15: 8 commitsNov 23, 2025Nov 15, 2026
1.2K commits in the last 52 weeks.

When work happens

weekday and hour
SunMonTueWedThuFriSat036912151821Sun 0:00 — 3 commitsSun 1:00 — 3 commitsSun 2:00 — 2 commitsSun 3:00 — 1 commitsSun 4:00 — 0 commitsSun 5:00 — 3 commitsSun 6:00 — 1 commitsSun 7:00 — 0 commitsSun 8:00 — 0 commitsSun 9:00 — 0 commitsSun 10:00 — 2 commitsSun 11:00 — 2 commitsSun 12:00 — 0 commitsSun 13:00 — 2 commitsSun 14:00 — 3 commitsSun 15:00 — 2 commitsSun 16:00 — 2 commitsSun 17:00 — 3 commitsSun 18:00 — 7 commitsSun 19:00 — 3 commitsSun 20:00 — 1 commitsSun 21:00 — 7 commitsSun 22:00 — 1 commitsSun 23:00 — 2 commitsMon 0:00 — 1 commitsMon 1:00 — 1 commitsMon 2:00 — 3 commitsMon 3:00 — 2 commitsMon 4:00 — 2 commitsMon 5:00 — 1 commitsMon 6:00 — 4 commitsMon 7:00 — 10 commitsMon 8:00 — 12 commitsMon 9:00 — 29 commitsMon 10:00 — 37 commitsMon 11:00 — 50 commitsMon 12:00 — 42 commitsMon 13:00 — 55 commitsMon 14:00 — 51 commitsMon 15:00 — 38 commitsMon 16:00 — 41 commitsMon 17:00 — 51 commitsMon 18:00 — 61 commitsMon 19:00 — 35 commitsMon 20:00 — 35 commitsMon 21:00 — 28 commitsMon 22:00 — 17 commitsMon 23:00 — 20 commitsTue 0:00 — 15 commitsTue 1:00 — 12 commitsTue 2:00 — 12 commitsTue 3:00 — 3 commitsTue 4:00 — 1 commitsTue 5:00 — 6 commitsTue 6:00 — 7 commitsTue 7:00 — 10 commitsTue 8:00 — 27 commitsTue 9:00 — 38 commitsTue 10:00 — 43 commitsTue 11:00 — 56 commitsTue 12:00 — 85 commitsTue 13:00 — 81 commitsTue 14:00 — 52 commitsTue 15:00 — 53 commitsTue 16:00 — 54 commitsTue 17:00 — 45 commitsTue 18:00 — 55 commitsTue 19:00 — 36 commitsTue 20:00 — 36 commitsTue 21:00 — 43 commitsTue 22:00 — 26 commitsTue 23:00 — 19 commitsWed 0:00 — 22 commitsWed 1:00 — 7 commitsWed 2:00 — 5 commitsWed 3:00 — 10 commitsWed 4:00 — 5 commitsWed 5:00 — 2 commitsWed 6:00 — 8 commitsWed 7:00 — 25 commitsWed 8:00 — 28 commitsWed 9:00 — 36 commitsWed 10:00 — 51 commitsWed 11:00 — 80 commitsWed 12:00 — 58 commitsWed 13:00 — 58 commitsWed 14:00 — 44 commitsWed 15:00 — 49 commitsWed 16:00 — 55 commitsWed 17:00 — 54 commitsWed 18:00 — 44 commitsWed 19:00 — 37 commitsWed 20:00 — 38 commitsWed 21:00 — 37 commitsWed 22:00 — 34 commitsWed 23:00 — 20 commitsThu 0:00 — 20 commitsThu 1:00 — 18 commitsThu 2:00 — 16 commitsThu 3:00 — 10 commitsThu 4:00 — 5 commitsThu 5:00 — 12 commitsThu 6:00 — 10 commitsThu 7:00 — 4 commitsThu 8:00 — 19 commitsThu 9:00 — 46 commitsThu 10:00 — 43 commitsThu 11:00 — 47 commitsThu 12:00 — 51 commitsThu 13:00 — 59 commitsThu 14:00 — 55 commitsThu 15:00 — 52 commitsThu 16:00 — 53 commitsThu 17:00 — 47 commitsThu 18:00 — 37 commitsThu 19:00 — 42 commitsThu 20:00 — 32 commitsThu 21:00 — 40 commitsThu 22:00 — 16 commitsThu 23:00 — 21 commitsFri 0:00 — 19 commitsFri 1:00 — 17 commitsFri 2:00 — 11 commitsFri 3:00 — 4 commitsFri 4:00 — 6 commitsFri 5:00 — 6 commitsFri 6:00 — 12 commitsFri 7:00 — 9 commitsFri 8:00 — 22 commitsFri 9:00 — 44 commitsFri 10:00 — 52 commitsFri 11:00 — 46 commitsFri 12:00 — 44 commitsFri 13:00 — 68 commitsFri 14:00 — 54 commitsFri 15:00 — 41 commitsFri 16:00 — 34 commitsFri 17:00 — 39 commitsFri 18:00 — 32 commitsFri 19:00 — 26 commitsFri 20:00 — 23 commitsFri 21:00 — 11 commitsFri 22:00 — 16 commitsFri 23:00 — 21 commitsSat 0:00 — 14 commitsSat 1:00 — 12 commitsSat 2:00 — 5 commitsSat 3:00 — 6 commitsSat 4:00 — 4 commitsSat 5:00 — 2 commitsSat 6:00 — 3 commitsSat 7:00 — 0 commitsSat 8:00 — 4 commitsSat 9:00 — 7 commitsSat 10:00 — 5 commitsSat 11:00 — 3 commitsSat 12:00 — 7 commitsSat 13:00 — 7 commitsSat 14:00 — 5 commitsSat 15:00 — 4 commitsSat 16:00 — 3 commitsSat 17:00 — 8 commitsSat 18:00 — 5 commitsSat 19:00 — 2 commitsSat 20:00 — 2 commitsSat 21:00 — 2 commitsSat 22:00 — 4 commitsSat 23:00 — 5 commits
Commit volume by weekday and hour (UTC). Larger dots mean more commits.
DateListRankStars gained
Feb 25, 2026daily#22+155
  • ultraworkers/claw-code

    An agent-managed museum exhibit, built in Rust with Gajae-Code / LazyCodex — developed and maintained with no human intervention.

    194.8K stars · Rust

  • flutter/flutter

    Flutter makes it easy and fast to build beautiful apps for mobile and beyond

    181.3K stars · Dart

  • farion1231/cc-switch

    A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode,DeepSeek Harness and more. Only official website: ccswitch.io

    156K stars · Rust

  • openai/codex

    Lightweight coding agent that runs in your terminal

    136K stars · Rust

  • rust-lang/rust

    Empowering everyone to build reliable and efficient software.

    122.3K stars · Rust

  • pbakaus/impeccable

    The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.

    114.1K stars · Rust