Openora: an open-source, AI-native Casino Platform Framework Self-hosted. Headless. Modular. Zero GGR share. https://openora.ai/ |
https://github.com/blurifycom/openoraHi Guys,
We’re the team behind Openora, built by Blurify (iGaming software since 2015). Operators usually have three options: build from scratch, go with a white-label/turnkey, rent a white-label with a GGR share and someone else’s roadmap, or stay stuck on legacy. Openora is a fourth one: own your platform without rebuilding the core from zero.
What it is- Open source (AGPL-3.0), with a commercial licence for closed-source setups
- Self-hosted, zero GGR share: your servers, your data, your revenue
- Headless + plugin-based: bring your own frontend, extend it without forking
- Swappable providers: PSP, KYC, aggregators and CRM connect through adapters
- Hash-chained audit log for every state-changing action
- AI-native: machine-readable contracts and MCP tooling, so AI agents can work with the codebase
Honest status: alpha (pre-1.0); Player management, wallet, compliance/KYC, casino integrations, backoffice and audit are available. Lobby/CMS and bonuses are in progress. Our first operator deployment is planned to go live in mid-November.
Example use cases
Launch a new casino: start from a ready backend instead of building the common layer yourself. You bring the brand, frontend and providers.
Extend a legacy platform: keep what you have and add Openora where your current platform blocks you (e.g. a new loyalty or payments capability).
Replace one provider: swap a PSP, KYC or aggregator through an adapter without touching business logic.
Migrate step by step: Connect → Extend → Replace → Migrate, one capability at a time and no big-bang replatforming.
AI-assisted engineering: scaffold a module, adapter or plugin with one command (contract, service, tests). AI helps your team move faster; it doesn't replace engineering accountability.
💥 Crash test: what we’re asking youDevs: clone it, run it, try to break the wallet and audit log. Issues and PRs welcome.
Operators: what’s your biggest pain with your current platform? Which crypto PSP or provider should we support first? What should we build next: bonuses, tournaments, affiliates, jackpots?
Everyone: would an open-source casino backend make you trust a site more? What would you want to verify?
Criticism and "this will never work because..." are welcome. We'll reply in this thread, and the best ideas go onto the public roadmap.
📆 We’ll be at
SIGMA World in Rome from 3rd to 5th of November, booth
H7-7065. If you’d rather tell us your feedback face to face, see a live demo, or just discuss whether open source belongs in iGaming, come say hi. Drop a reply here or message us on Telegram (@blurify) to book a time.
