Deployment & Self-Hosting
Clone it, own it, self-host it. Run as a single deployable today and split into services later, with zero module-code changes.
Openora.ai is free forever under AGPLv3, or available under a commercial license - clone the repo, self-host on any infrastructure, and keep 100% of your revenue. There's no seat pricing, no GGR share, and no vendor lock-in.
Monolith today, microservices later
A fresh scaffold runs as a single deployable. The no-cross-domain-imports rule and the broker seam are what make a later split cheap: when a domain like Wallet or Gaming needs to scale independently, the module code shouldn't have to change, only the deployment topology. Note this is a design property, not a shipped feature - extracting a module to its own deployable is still on the roadmap.
$ pnpm create:app my-gaming-core
$ cd my-gaming-core && pnpm install
$ docker compose up -d # postgres
$ pnpm db:migrate && pnpm dev # api on :3001The scaffolded app ships a docker-compose.yml for Postgres and a thin createApp() entry. How you build and ship the image is up to you - the framework has no opinion and no deploy command of its own.
Where to run it
Openora.ai has no opinion about hosting: bare metal, your own Kubernetes cluster, or any major cloud all work, since the framework only assumes a Postgres-compatible database and a Node runtime.
Licensing
The core framework, adapters, and tooling are distributed under AGPLv3 by default. You can use, modify, and extend the framework freely; if you distribute a modified version as a network service, the AGPLv3 asks that you share those modifications back.
If sharing your modifications isn't an option, Openora.ai also offers a commercial license: the same framework, without the AGPLv3 copyleft obligations, sold alongside dedicated infrastructure, certification and licensing support for teams that need a license-grade backend without building the compliance layer themselves - see Pricing.