About us
We started because our origin kept falling over
Meridian began as an internal cache for a game studio's patch servers. The cache turned out to be the interesting part.
Origin
From one rack to sixty-one sites
In 2016 we were four people with a single rack in Frankfurt and a problem: every patch day took the origin down. The fix — a regional shield that collapsed concurrent misses — worked so well that three other studios asked to use it. We have been adding sites ever since, and the design has not fundamentally changed.
- Profitable since 2019, no outside capital
- Every engineer carries a pager, including the founders
- Hardware is owned, not rented — that is why the per-TB price works
One rack in Frankfurt
A shield cache for a single customer's patch servers.
Nine sites, first anycast prefix
The network gets its own address space.
Object slicing ships
The 8 MB slice design replaces whole-file caching.
Thirty sites, first petabit day
1.02 Pbps peak during a console launch.
Real-time logs
Unsampled delivery at 10 Gbps per customer.
Sixty-one sites
214 Tbps installed, 41.6 EB served in the last 30 days.
How we work
Boring on purpose
We would rather run software that is three years old and understood than something new that pages us at 04:00.
Own the path
We buy transit from multiple carriers and peer directly wherever it is possible, so a single bad hop is never a single point of failure.
Write it down
Every incident gets a public write-up. Every design decision gets an RFC. Institutional memory beats heroics.
Some of the people behind it
A quarter of the company has been here since the first rack.
We are hiring
Remote-first across EU time zones, with a small office network for people who prefer one.