Most operators do not need a custom build. Buying a white label, plugging in a games aggregator, and competing on marketing is the right call for the median brand. Custom iGaming software is for the minority of operators who have a thesis the templates cannot express: a novel game mechanic, a hybrid sportsbook-exchange-casino product, a B2B platform sold to other operators, or a player experience that requires owning every layer down to the matching engine. Sudonex builds those when the case is real.
When off-the-shelf does not fit
There are five tells. First, the product roadmap names features that no aggregator or white label vendor can ship — peer-to-peer betting, social casino mechanics tied to a token, AI-driven personalization at the math layer, exotic markets a turnkey sportsbook cannot model. Second, the operator plans to license the platform to others and so cannot ship a vendor's white label. Third, regulatory ambition exceeds what a white label vendor will entertain — a US state-by-state expansion with internal control standards, a publicly listed parent with SOX implications. Fourth, performance targets exceed white label SLAs — sub-100ms bet placement, 100k+ concurrent in a single region, deterministic latency for live dealer or exchange. Fifth, the cost model breaks down: at sufficient scale, a white label revenue share costs more per year than a senior engineering team.
If none of those tells apply, custom is wrong. Read the white label casino solutions page and save 18 months.
Discovery to launch
A Sudonex custom build runs through five phases. Phase 1, discovery (3 to 6 weeks): product workshops, regulatory mapping, architecture options, build-vs-buy decisions per module, fixed scope, and a budget envelope. Phase 2, foundation (6 to 10 weeks): the platform spine — identity, wallet, ledger, observability, deployment pipeline. Phase 3, vertical build (12 to 32 weeks depending on scope): the game or product layer that justifies custom in the first place. Phase 4, integration and certification (6 to 12 weeks): payments, KYC, RNG certification, regulator audits, security audits. Phase 5, launch and stabilization (4 to 8 weeks).
Architecture decisions
Three decisions dominate every custom build. Monolith vs services: we default to a modular monolith for the first 12 months, extracting services as load and team size justify. The cost of premature microservices on a 6-engineer team is hard to recover. Database choice for the wallet and ledger: PostgreSQL with append-only event tables and materialized balance views, not a NoSQL store, because regulators want auditable double-entry accounting. Real-time layer: WebSockets backed by Redis pub/sub for game state, with idempotency keys on every action — losing a bet to a network blip is a regulatory event, not a bug.
Services in the build
A custom build commonly assembles modules from across the Sudonex catalog: casino app development for native clients, slot game development for proprietary titles, sports exchange development where peer-to-peer markets are part of the product, igaming UI/UX design for the player-facing experience, and igaming MVP consultancy when the founder still wants outside review on the product thesis itself before committing to a 12-month build.
Directional cost ranges
Public ranges, not quotes. A focused custom MVP — single vertical, single jurisdiction, in-house games — runs 350k to 700k USD over 6 to 9 months. A multi-vertical platform with sportsbook, casino, and exchange in two jurisdictions runs 1.2M to 2.5M over 12 to 18 months. An enterprise platform supporting B2B licensing, multiple brands, and 100k+ concurrent runs north of 3M and is best handled under the enterprise iGaming platforms track. These are build costs only and exclude licensing, marketing, and games provider fees.
Use cases
Funded startups with a non-obvious product thesis, established operators building a second-generation platform to replace an aging white label, B2B platform vendors entering the supplier market, and US-facing operators where regulatory granularity makes off-the-shelf untenable.
FAQ
Do we own the source code
Yes. Source code, infrastructure-as-code, and documentation are delivered to a repository you control. There is no Sudonex license on the output.
Can we start with white label and migrate to custom later
Yes, but migrate the player base, not the code. The codebases share little. Plan a 9-month custom build running parallel to white label operations, then a phased player migration.
Who writes the game math
For proprietary titles, our math team produces the PAR sheets, RTP modeling, and volatility curves, then certifies through GLI or iTech.
What happens if scope changes mid-build
Fixed scope per phase. Changes inside a phase are absorbed if minor; material changes trigger a re-scope and re-quote at the phase boundary.
Do you provide ongoing engineering after launch
Yes, through a managed engineering retainer or by transitioning the build to your in-house team with knowledge transfer baked into the final phase.
Start the discovery
Book a discovery call with Sudonex. We will tell you within an hour whether your problem is a custom-build problem or whether a faster, cheaper path exists.