Skip to content

Realtime state, solved

One shared state, everywhere at once.

Lattice keeps every client, server and edge worker on the same version of the truth. Conflict-free merges, presence and offline replay come as one primitive instead of four services.

Scroll, or drag the mass

The merge runs where the user is.

Writes apply locally first and reconcile in the background. A document held by two hundred editors converges to the same bytes without a lock, a queue, or a retry loop in your code.

Local-first writes
Mutations commit to the local replica in under a millisecond, then replicate.
Deterministic replay
Every session keeps an ordered log, so an offline client rejoins without a reload.
Presence included
Cursors, selections and away-state travel on the same socket as your data.

Four primitives, nothing else to wire.

01

Doc

A typed, versioned object any number of clients can hold open.
02

Room

Membership, permissions and presence scoped to one session.
03

Query

Live reads that push updates instead of being polled.
04

Hook

Server-side handlers that run on commit, close to the data.

By the numbers

0.8 ms
Median local commit
34
Edge regions
99.99%
Replication uptime, trailing year
12 kB
Client runtime, gzipped

Put the state layer behind you.

Free while you build. Keys issued instantly, no card, no sales call.