https://api.alakazam.gg — it’s the
fastest path and everything in these docs works out of the box. For a small set
of teams with strict data-residency, procurement, or capacity requirements, we
also support running your own backend under an enterprise agreement.
This is not self-serve. There is no signup, no toggle, and no public
setup — it’s arranged directly with the Alakazam team.
What it is
Under an enterprise agreement, your team can operate its own instance of the Game-Creation backend (conjure-service) pointed at your own Reactor account (REACTOR_BASE_URL / REACTOR_API_KEY). That keeps generation and runtime
under your infrastructure and billing while your app keeps talking to the same
API surface documented here.
Typical reasons teams ask about this:
- data residency or a private network boundary,
- dedicated capacity and runtime billing on your own Reactor account, or
- procurement and compliance requirements a shared tenant can’t meet.
How to get it
This offer is gated and configured with you directly — we scope requirements, set up the agreement, and hand over the deployment details. A ready-made deployment kit (consolidated schema, a private runbook, and bootstrap + smoke scripts) exists and is shared only under an enterprise agreement — it is not published or self-serve. There are no public setup steps.Talk to us
Email the Alakazam team at hello@alakazam.gg with your use case and
requirements, and we’ll take it from there.