Phase-0 · design-partner stage
The managed game backend that respects your workflow.
Identity, economy, cross-store IAP, leaderboards, config and cloud code — one meta-game backend, with GitOps, first-class TypeScript and open Apache-2.0 client SDKs. The standout: set real breakpoints in your live cloud code (design-partner preview).
Your data and your client code are yours.
Open Apache-2.0 SDKs and a day-one data-export SLA — a managed game backend you can always walk away from with your data intact, built for how you actually work.
The AI-native game backend.
Governed, opt-in AI ops tooling on a managed game backend — with open Apache-2.0 client SDKs and a day-one data-export SLA. Built for live-service studios.
01 / the problem
The problem was never the features.
It was that you couldn't debug your server-side logic, version it like code, or leave with your data — so when a vendor sunset or a pricing change came, your live game's fate sat in someone else's roadmap.
Identity, economy, leaderboards — the meta-game layer is table stakes. Owning it is not.
02 / how it works
A meta-game backend you control.
Jacent runs the live-service layer your game needs — player identity, virtual economy and cross-store IAP, leaderboards, teams, challenges, and server-side cloud code — as a managed service with open Apache-2.0 client SDKs and a contractual data-export SLA from day one.
We integrate the free floor (identity, voice and anti-cheat via EOS) and game-server hosting (Edgegap, Photon) rather than reselling them — so you adopt us for the high-value layer, and keep what already works.
03 / capabilities
The meta-game layer, plus the developer experience to run it.
-
available now
The meta-game layer, in one backend
Identity and social, virtual economy and cross-store IAP, leaderboards, teams and challenges, config and deploy — the live-service layer your game needs, run as one managed service.
-
available now
Built for your workflow
GitOps with a CLI and CI/CD, first-class TypeScript, and local testing. Version, review, promote and roll back your backend config like code.
-
design-partner preview · our differentiator
Step-debug your cloud code
Set real breakpoints in your server-side logic — a gap we don't see managed-only incumbents filling. Stop reverse-engineering production from log lines.
-
available now
Your data & code, portable
A contractual data-export SLA today, plus open Apache-2.0 client SDKs. Your data and your client code are yours — if we ever disappear, you keep both and can walk.
-
our commitment
Pricing that won't ambush you
Predictable, capped and transparent — no per-install surprises, no retroactive changes, no egress shock. Pricing is a wedge, not a trap.
● now · ◐ in progress / preview · ◆ commitment — we label what ships, what's in progress, and what we promise. We won't claim validated security or scale, or SOC 2 certification, before the evidence lands.
04 / why now
The category is consolidating — and stranding studios.
- Mar 2026 Unity exits Multiplay game-server hosting.
- May 2026 Hathora switches off.
- 2022 GameSparks fully decommissioned — no AWS successor.
Studios are re-choosing their backend right now, and "will this vendor still be here in three years?" is the first question on the list. So we make it answerable: your data exports on a contractual SLA and your client code is open Apache-2.0 — table stakes, not a nice-to-have.
05 / who it's for
Built for mid-core and mid-size live-service studios.
A fit if you…
- run or are building a live game with an economy and social systems;
- have a backend team that wants control and portability;
- are re-choosing a backend after a sunset or a pricing change.
Probably not yet if you…
- are a solo hobby project — the free tiers serve you well today;
- are a top-grossing studio with a bespoke in-house platform.
06 / where we are
Early, and building in the open.
Our client SDKs are open Apache-2.0 and your data is portable by a contractual export SLA; security is built in by design and our SOC 2 Type II programme is in progress. We'd rather show you evidence as it lands than claim it before — so we won't show you logos we don't have or numbers we made up.
We're at design-partner stage, choosing a small group of studios to build the first version with, on founding-partner terms. That's the offer: shape the backend you'll depend on.
07 / questions
Straight answers.
I already use PlayFab / UGS.
They're managed too — but we ship a step-through debugger (design-partner preview), open Apache-2.0 client SDKs and a data-export SLA, so your data and client code stay yours. Integrate us for the meta-game layer and keep what works.
You're new — won't you sunset too?
Don't trust the promise, trust the mechanism: a contractual data-export SLA today, plus open Apache-2.0 client SDKs. If we're gone, you keep your data and your client code, and can walk.
Is it secure? Will it scale?
Designed for tenant isolation; SOC 2 Type II in progress; scale architecture in validation. We'll share the reports as they land — we won't claim them before.
Is this an "AI" backend?
No. It's a backend you control. AI is optional, governed ops tooling — not the product.
Is it ready?
It's Phase-0 / design-partner stage. That's the point — shape it with us on founding-partner terms.
08 / founding partners
Build the first version with us.
We're taking on a handful of founding design partners — direct roadmap influence, founding-partner pricing, hands-on onboarding. Tell us what you're building.