gitwtfhub

wtf is universe?

kidandcat/universe — explained in plain English

Analysis updated 2026-08-10 · repo last pushed 2026-03-26

GoAudience · ops devopsComplexity · 3/5MaintainedSetup · moderate

TL;DR

Universe continuously streams SpacetimeDB data files to a second machine in real time, giving you an always-up-to-date backup or replica without scheduled backup jobs.

Mindmap

mindmap
  root((repo))
    What it does
      Streams DB changes live
      Copies data directory
      Resumes after drops
    How it works
      Sender on DB server
      Receiver on backup server
      Checksums verify data
    Use cases
      Disaster recovery
      Standby replica
      Hardware migration
    Tech stack
      Go
      SpacetimeDB
      File system watching
    Limitations
      No built-in encryption
      No monitoring or alerting
      Raw data only

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Set up a standby replica of your SpacetimeDB data on a second server for disaster recovery.

REASON 2

Keep a continuously updated copy of your database files in another data center.

REASON 3

Migrate SpacetimeDB to new hardware by syncing everything first, then switching over with no downtime.

What's in the stack?

GoSpacetimeDB

How it stacks up

kidandcat/universe0verflowme/cloudflared0verflowme/pulumi-vultr
LanguageGoGoGo
Last pushed2026-03-262024-10-192022-12-26
MaintenanceMaintainedStaleDormant
Setup difficultymoderatemoderatehard
Complexity3/52/53/5
Audienceops devopsdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires running separate sender and receiver processes on two machines, plus a SpacetimeDB instance to replicate from.

Wtf does this do

Universe is a tool that continuously copies your SpacetimeDB data to a second machine, so you always have an up-to-date backup or replica. It works like Litestream does for SQLite: instead of running a full backup job on a schedule, it watches your database files and streams every new change over the network in real time. To use it, you run a receiver process on your backup server and a sender process on your database server. The sender watches the SpacetimeDB data directory for any file changes and immediately transmits the new bytes to the receiver, which writes them into a matching folder structure. If you are setting up a brand-new replica, an optional flag tells the sender to copy everything first before switching to live-watching mode. The system handles network interruptions gracefully. The receiver keeps track of exactly how many bytes it has received from each file and periodically sends that information back to the sender. If the connection drops and reconnects, the sender simply resumes from where the receiver left off, so no data is duplicated or missed. Each chunk of data is also verified with a checksum to make sure nothing was corrupted in transit. This would be useful for teams running SpacetimeDB who need a standby replica in another data center, want a continuously updated copy for disaster recovery, or are preparing to migrate to new hardware without downtime. It is a straightforward, single-purpose tool: it replicates the raw data directory and nothing else. The README does not go into detail on monitoring, alerting, or encryption, so you would need to handle those concerns separately.

Yoink these prompts

Prompt 1
Write a setup guide for using Universe to replicate SpacetimeDB data from a primary server to a backup server, including how to start the sender and receiver processes.
Prompt 2
Create a shell script that launches the Universe receiver on a backup machine and the Universe sender on the database server, including the initial full-copy flag for a new replica.
Prompt 3
Help me add a health-check and alerting layer on top of Universe so I get notified if my SpacetimeDB replication stream stops or falls behind.
Prompt 4
Compare Universe-style continuous file replication for SpacetimeDB against taking scheduled snapshot backups, and explain the pros and cons of each approach for disaster recovery.
Prompt 5
Draft a runbook for recovering from a network outage between my Universe sender and receiver, including how to verify no data was lost or duplicated.

Frequently asked questions

wtf is universe?

Universe continuously streams SpacetimeDB data files to a second machine in real time, giving you an always-up-to-date backup or replica without scheduled backup jobs.

What language is universe written in?

Mainly Go. The stack also includes Go, SpacetimeDB.

Is universe actively maintained?

Maintained — commit in last 6 months (last push 2026-03-26).

How hard is universe to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is universe for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.