One world.
As many servers as it needs.
Tessera cuts your world into zones and spreads them over servers. When a crowd gathers, the zone splits. When it leaves, the zones merge. Players walk across every border without noticing one.
A zone changes servers in seven steps
The game keeps ticking through all of them. Ownership flips at one named tick, on both servers at once.
Prepare
The coordinator names the zone, the new server and a new epoch.
Shadow
The new server receives the zone's entities and follows every change.
Ready
It reports that it has caught up.
Commit
The flip tick is written to the map. From here it will happen.
Flip
At that tick the old server stops simulating the zone and the new one starts.
Switch
Players in the zone are handed to the new server. Their prediction carries on.
Clean
The old server drops its copies.
Every part of a seamless world
The map
Quadtree zones
Big zones where the world is quiet, small ones where it is busy.
Any shape per server
A server owns one zone or a connected group of them.
Instant split and merge
Cutting a zone moves no data. Only the map changes.
A floor on zone size
You set the smallest zone. A crowd never splits the world into dust.
The map is a log
Every change is one record in a Rune topic. Replay it to see any moment.
One writer
Only the coordinator changes the map. Servers follow it.
Crossing a border
Entity handoff
A character walking into the next zone is passed to its server mid-stride.
No ping-pong
Standing on a border does not bounce a player between two servers.
Prediction survives
The client changes servers and keeps its inputs, its history and its feel.
See across the line
Each server keeps read-only mirrors of what is just over its border.
Act across the line
A fireball that lands next door is delivered as an effect, exactly once.
Parties stay together
Linked entities, such as a rider and a mount, cross as one.
The scheduler
Recover first
A zone without a server is always the first thing fixed.
Shed load
An overloaded server gives a zone to a neighbour with room.
Split hot spots
Above 60% of the tick budget, the busiest zone is cut in four.
Pack and merge
Below 25%, zones are gathered onto fewer servers and merged back.
No thrashing
A zone that just changed is left alone for 60 seconds.
Your hints
Split ahead of a world boss. Pin the capital to its own server.
Failure and capacity
Fenced by epoch
A server that lost a zone cannot write to it again, however late it wakes up.
Recovery from saved rows
A dead server's zones restart elsewhere from what was saved.
Stop, never guess
A server that is unsure of its ownership stops simulating that zone.
Two calls for capacity
"Give me a server" and "release this server". Nothing else to implement.
Static list or Kubernetes
Run on machines you name, or let Tessera ask your cluster for pods.
Built on Aether
Your Aether game runs in every zone, unchanged.
It follows the players
Tessera watches how much of each tick a server spends. That one number drives every decision.
Four rules that always hold
- One owner per point, per tickEvery spot in the world is simulated by exactly one server at a time.
- One real copy of every entityA character is never duplicated and never lost at a border.
- Every effect lands at most onceA hit across a border is never applied twice.
- Only the current owner savesA stale server cannot overwrite a player's saved state.
Stop sharding your players
One world, one community, on as many servers as tonight needs.