How WhatsApp scales to civilization level.

Nothing travels until your phone seals it. End-to-end encryption — complete since April 5, 2016 — locks every message with keys that never leave either device.

What to watch — the wax seal. It closes at your phone and never opens until the far one.

To the relay, your message is an envelope it cannot open. It reads only the address on the outside — inside stays scrambled all the way across.

The double tick is the handover moment: the envelope reaches the right phone, opens — and the server's copy is deleted. Store-and-forward, with the emphasis on forward.

Friend offline? The sealed envelope waits in an encrypted queue for at most 30 days — then it is deleted whether or not it was ever collected.

Every online user gets their own tiny Erlang process — about 2.7 kilobytes when it starts. Not a thread, not a container: a worker so small one server can hold a small country of them.

In January 2012, one FreeBSD box held 2,277,845 simultaneous connections — with 41.9% of its CPU still idle.

What to watch — the counter. It stops on a real number from a real night, not a round one.

2,277,845 processes × 2.7 KB ≈ 6.2 GB of a 103 GB machine (computed live). This density is how ~550 servers and ~11,000 cores served ~465 million users — run by ~32 engineers.

By 2014 they deliberately backed off to about a million per box. Photos and video had made each connection heavier — headroom for spikes beat bragging rights.

You type once. A family group of eight — our demo group — means eight sealed envelopes leave your phone, each locked for exactly one reader.

What to watch — the fan. One bubble in, eight envelopes out.

Measured in 2014, the asymmetry was already huge: 19 billion messages in per day, 40 billion out — every send more than doubling on average (the ratio is computed beside the counters).

Since 2021 your phone does the multiplying itself: multi-device encrypts one copy per recipient device, and the server just routes sealed envelopes it can never open.

The server's whole memory of a conversation is whatever is in flight right now. Delivered means deleted — the copy evaporates on confirmation.

What to watch — envelopes dissolving at the phone. The kept counter never moves.

Undelivered envelopes wait encrypted, at most 30 days. Then they are gone too — no archive, no backlog, no history.

The queue stays shallow because people read fast: in 2014, more than half of queued messages were read within 60 seconds, and 98% of reads came straight from the hot cache.

The counters track this scene's own envelopes — every poof you can count was rendered. Kept after delivery: 0. That zero is the design.

New Year's Eve is the biggest day, every year — and a regular day is already over 100 billion messages and 2 billion calls.

What to watch — the strip. Each bar is a timezone; each strike is its midnight.

The storm arrives as a wave: midnight strikes first at UTC+14 and rolls westward for more than a day until UTC−12. Every crest is a region's worth of simultaneous greetings.

Measured on the 2014 fleet: 342,000 messages in per second, 712,000 out — fan-out again — plus 230,000 logins per second. NYE 2019 alone topped 100 billion messages.

A relay that forgets never grows with its history — only with its storm. That is the whole trick.