Four delivery models. One platform.
Engagement begins with solution design — not instant self-serve setup. Pick the integration depth that fits your stack, team, and rollout timing.
Delivery models supported out of the box.
White-label
MiroFish powers the full experience under the partner's brand.
Best for
Operators launching new branded offerings end-to-end.
Co-branded
Joint go-to-market with a co-branded wrapper around MiroFish modules.
Best for
Strategic partnerships and category launches.
Embedded module
MiroFish components integrated into an existing partner platform.
Best for
Media, fantasy, and engagement platforms extending product surface.
API-led delivery
MiroFish business logic and workflows exposed into a partner environment.
Best for
Technical partners with custom UX and a mature platform stack.
A staged delivery process — not a code dump.
- 01
Solution design
Use case, partner model, scope, target launch window.
- 02
Configuration
Modules, branding, roles, commercial rules, integration depth.
- 03
Build & integrate
Embed snippet, API wiring, branded surface — staged on a non-prod environment.
- 04
Validate & launch
Operational checks, governance review, rollout, and post-launch iteration.
What MiroFish brings vs. what you control.
MiroFish managed
- Backend services, auth, and data layer
- Simulation engine and knowledge graph
- Reporting and insight loop
- Credit ledger and billing core
- Platform updates and operational tooling
Partner controls
- Branding, theme, and surface customization
- Pricing, charging rules, and packaging
- Game and product settings via admin backend
- Customer / partner identity passed via snippet or API
- Region, compliance, and rollout governance