Open core. Pay only for enterprise or custom work.

Traditional platforms are closed, monolithic legacy systems that lock you into their ecosystem. Openora.ai is an open-source, infrastructure-first framework. It provides modular core gaming domains, contracts, and adapters, giving operators full ownership of their technology stack and the ability to customize every single component.

Yes. The core framework, adapters, and tooling are published on npm as @openora/core, open-source under AGPLv3 - you can use, audit, and modify it with no hidden GGR (Gross Gaming Revenue) share fees. AGPLv3 is a strong copyleft license: if you run a modified version of the core over a network, you're required to release the source of those modifications too. If that doesn't fit your business, we also offer a commercial license that removes that obligation.

It means our entire codebase, schemas, and contracts are optimized for AI readiness. Every module is strictly contract-driven and structured so that LLMs and AI agents can read, understand, generate, and troubleshoot code within your ecosystem natively, drastically accelerating your development cycles.

Not at all. Openora.ai is fully composable. You can adopt individual modular services (like specific gaming domains or integration adapters) and plug them directly into your existing legacy architecture without a complete rip-and-replace operation.

Because you host and fully own the technology stack, you have absolute control over compliance and data privacy. The framework ships an append-only, sha256 hash-chained audit log, responsible-gaming controls (limits, cool-off, self-exclusion), geo rules and a KYC port, and sealed tokens stop a plugin from quietly overriding a regulator-mandated service. Treat this as a baseline to build on, not a certification: the framework has not been through an external security or RNG audit, and licensing remains your responsibility.

Yes. Code you write in your own repository - plugins, adapters, custom modules, business logic - is entirely yours. AGPLv3 only requires that if you modify the framework's core itself and serve that modified core over a network, you release the source of those specific changes. Most operators extend Openora through plugins in their own repo rather than editing the core directly. If you need to modify the core without that obligation, our commercial license covers that.