About

We build the boring part of live-ops: getting content onto players' devices, reliably, without a store release standing in the way.

Why we started

We spent years on live game teams, and the same thing kept happening. A season would be ready on a Tuesday and land on a Thursday the following week, because the content was welded to the binary and the binary had to go through review. Everyone had built some version of a patcher to work around it, and everyone's version was slightly broken in a different way.

The problem is not interesting, which is exactly why it never gets the good engineers. It is also unforgiving: get it wrong and you brick installs at scale, in public, on a weekend. So teams keep rebuilding it, carefully, instead of working on the game.

What we do about it

Sablecrest is a delivery endpoint and an SDK. You publish a manifest; clients resolve it and pull what they don't already hold. Bundles are immutable and content-addressed, so a rollback is just pointing the manifest back at the previous one — no migration, no cleanup, no support thread about a half-applied patch.

We are deliberately not a game backend. We don't hold your player data, run your economy, or want to. There are good products for that, and being in that path means being in the way.

Where we're at

We're early. We run in one region, we onboard studios one at a time, and we say no to work that would take us away from making delivery boring and predictable. If that sounds like the right stage for you, we'd like to hear from you.