The United States is not one iGaming market. It is, today, seven legal online-casino markets — New Jersey, Pennsylvania, Michigan, West Virginia, Connecticut, Delaware and Rhode Island — each with its own gaming control board, its own technical standards, and its own approved-supplier list. Operators expanding state by state need a platform architecture that treats jurisdictional differences as configuration, not as forks. Sudonex builds that architecture.
The State-by-State Reality
New Jersey's Division of Gaming Enforcement (DGE) sits at the technical-rigour ceiling — its requirements around system integrity, geolocation, and ICS (internal control standards) are the de facto reference for every other state. Pennsylvania Gaming Control Board (PGCB) follows closely, with its own technical standards and supplier-licence regime. Michigan Gaming Control Board (MGCB) brought a more streamlined framework. West Virginia Lottery, Connecticut DCP, Delaware Lottery and Rhode Island Lottery each add their own variants. Every state requires GLI-19, GLI-33 and applicable state-specific test-lab certification.
Why US Operators Choose Sudonex
We architect for the state-by-state reality. The platform's licence-management layer treats each state as an independent regulatory tenant — geolocation, payment routing, RG controls, reporting feeds and supplier integrations are configurable per state. Adding the next state is a configuration and certification exercise, not a re-platforming.
Services for US Casino Operators
Sudonex delivers casino app development for native iOS, Android and web — with the geolocation SDK integration (GeoComply or equivalent), the multi-state account framework, and the state-aware bonus engine US operators need. Sportsbook adjacencies run on our sports exchange development stack. Operators with proprietary IP ambitions use our slot game development team. iGaming API integration connects every GLI-certified studio supplier — IGT, Light & Wonder, NetEnt, Evolution, Pragmatic — into the operator wallet. New entrants begin with iGaming MVP consultancy for a market-entry roadmap that respects the state-by-state economics.
Payments and KYC
US payments are a layered problem: ACH, debit cards (with MCC 7995 routing realities), PayPal, Play+ prepaid, and the state-specific cage and bank-transfer rails. KYC integrates with LexisNexis, Experian, and the state-mandated identity verification providers. The platform's source-of-funds and AML monitoring is tuned to FinCEN reporting thresholds and state-level AML guidance.
Geolocation and Player Protection
Geolocation is enforced at session start and continuously through play. State-mandated RG controls — deposit limits, loss limits, time-outs, self-exclusion via the state-level voluntary exclusion lists — are platform primitives. Multi-state self-exclusion screening (where states share data) is wired in.
Engineering Standards
US data residency, GLI-19 and GLI-33 ready architecture, ICS-aligned access controls, and state-specific reporting feeds in the formats each control board consumes.
FAQ
Are you a licensed US gaming supplier?
Sudonex provides technology and platform services. Supplier licences are state-specific and held where the operator's strategy requires.
Which states do you have direct experience with?
NJ, PA and MI are the primary engagement footprint, with the platform architecture extending to WV, CT, DE and RI.
Can you handle GLI certification?
We deliver the platform and the technical documentation; certification is performed by GLI or BMM directly. We have shipped multiple certifications without remediation cycles.
How long does a multi-state launch take?
First state in twenty to twenty-six weeks; each additional state in eight to twelve.
Multi-State Wallet Architecture
The single hardest engineering question in US iGaming is the multi-state wallet. State licences typically require state-segregated player accounts, state-segregated AML monitoring, and state-segregated funds. Operators that build a single multi-state platform anyway — with the segregation enforced in the data layer rather than the code path — ship faster across states and reconcile cleaner. Sudonex builds this architecture.
Geolocation Engineering
GeoComply's SDK is the de facto standard, but the operator-side integration is where compliance is actually won or lost. Continuous geolocation, jurisdiction-boundary edge-case handling (state lines, tribal land, military bases), and the appeals UX for legitimate players incorrectly flagged are all engineering surfaces. Sudonex platforms address each of them.
Tribal and Commercial Distinctions
Several states layer tribal-state compacts on top of the commercial framework. Platforms positioned for those markets need to respect tribal regulatory authority distinctions without splitting the codebase.
ICS Documentation Engineering
Each state's Internal Control Standards demand documented procedures across access control, change management, financial controls, RG enforcement, AML monitoring and incident response. Operators that produce ICS documentation as a continuous artifact — flowing from the actual platform configuration — survive audits cleanly. Operators that hand-write ICS documentation accumulate drift between document and reality. Sudonex platforms generate ICS-relevant documentation as a build artifact, keeping documentation aligned with running configuration.
Native App Submission Realities
iOS and Android app stores have specific requirements for real-money gambling apps. Apple's policies vary by state. Google's policies require state-specific submission and approval. The submission process itself is part of the engineering critical path. Sudonex teams handle store-submission engineering as part of the launch sequence, not as an afterthought.
Tribal-State Compact Considerations
Several states layer tribal-state compacts on top of commercial frameworks. Connecticut, Michigan and others have tribal-operator licensing inside the broader online framework. Platforms positioned for these markets respect tribal regulatory authority distinctions without splitting the codebase.
Engagement Models for US Operators
US iGaming engagements run as fixed-scope MVP for first-state launch, expanding into embedded squad for multi-state rollout. The squad model fits the multi-state cadence — each state launch reuses the same operational knowledge — better than vendor-style project engagement.
Operational Maturity
Each state gaming control board expects operational maturity from launch. Documented incident response, regulator-notification timelines, change-management gates, and the SRE depth continuous compliance requires. Sudonex platforms ship with this posture.
Brief Engineering
If you are entering the US, expanding state by state, or re-platforming for multi-state efficiency, brief Sudonex.