iGaming RGS & Game Aggregation Platform Architect

ABOUT US We are a licensed online gaming group operating multiple B2C brands, with an in-house content studio in build-out. Our B2C operations currently run on a third-party turnkey platform. We are now building our own game aggregation layer: a single integration point that hosts our proprietary game content and connects it to multiple operator brands - ours first, third-party operators after that. WHAT WE ARE BUILDING The first title is a crash / instant multiplier game. We have a browser-based visual prototype that establishes the theme and UX, but it is client-side only - the multiplier, the outcome and the wallet all live in the browser. It is a look-and-feel reference, not production code. We need it rebuilt properly: - Server-authoritative outcomes. Certified RNG generates the crash point server-side; the client renders, never decides. - Provably fair. Server-seed commitment published pre-round, revealed post-round, client-seed contribution, publicly verifiable. - Shared-round multiplayer. One round, many players, live cash-out feed, real-time transport at scale. - Aggregation layer. Our own RGS plus aggregation platform: game catalogue and launch service, per-operator seamless wallet adapters (auth / balance / debit / credit / rollback), idempotency and reconciliation, round history and game recall, per-brand configuration (currencies, bet limits, RTP variants, theming), back-office reporting, and hooks for bonuses, free bets and tournaments. - Certification-ready. Architected from day one to pass RNG and game certification (GLI-19 / BMM style), with the audit trail, round recall and responsible-gaming controls that requires. THIS CONTRACT: PAID DISCOVERY FIRST We are not asking you to start building. The first engagement is a paid discovery and specification phase, hourly, expected 2-4 weeks. If it goes well - and we intend for it to - you continue straight into the build on the same hourly contract, long term. Discovery deliverables: 1. Architecture document - services, data stores, real-time transport, deployment topology, failure and recovery behaviour, scale targets, and the reasoning behind each choice. 2. Game math model - crash curve distribution, RTP and house edge, max multiplier cap, per-round and per-player exposure limits, bet limits by currency, and the simulation that evidences the stated RTP. 3. API surface - operator-facing integration spec (launch URL and session token, seamless wallet endpoints, rollback and reconciliation semantics, error taxonomy) plus the internal RGS contracts. 4. Provably-fair design - seed commitment scheme, verification method, and the public verifier UX. 5. Certification and compliance path - what a test house will require, what has to be true of the architecture before submission, responsible-gaming controls, and geo / jurisdiction configuration. 6. Build plan - phased milestones, dependencies, realistic timeline, team shape (what you would do yourself vs. what we should hire alongside you), and cost estimate. We will review the discovery output before extending hours into the build. Either side can stop there cleanly. WHO WE ARE LOOKING FOR Required: - You have built or been a core engineer on a remote game server (RGS) or casino game backend that went through certification. Not a social or play-money game - a real-money one. - Hands-on experience with seamless wallet integration against operator platforms or aggregators. You can name the providers. - Real-time, high-concurrency systems - WebSocket at scale, shared game state, sub-second determinism across thousands of connected clients. - You understand why the outcome cannot live in the client, and you can explain the audit and recall requirements that follow from that. - Clear written English. The discovery deliverable is a document - writing is the job. Strong plus: - Direct experience with crash / instant-win / Aviator-style mechanics. - A provably-fair implementation you can point us at. - Prior work on an aggregation or content-distribution layer serving multiple operator brands. - Familiarity with test houses (GLI, BMM, iTech Labs) and the submission process. - Exposure to Curacao / Anjouan / MGA regulatory requirements. Not a fit if: your experience is play-money or social casino only, you have not worked behind a real-money wallet, or you would need us to specify the architecture for you. We are hiring judgement, not hands. TERMS - 20-30 hours per week during discovery, scaling up for the build. - At least 4 hours daily overlap with AEST (UTC+10). - Work is done under NDA with full IP assignment to us. We will send both before the contract starts. - All work through Upwork for the duration of the contract. IN YOUR PROPOSAL Please answer these - they matter more to us than your portfolio: 1. Describe an RGS or real-money game backend you have built or worked on. What was your role, and what was the certification path - which test house, and what did they push back on? 2. How would you architect a shared-round crash game so that 5,000 concurrent players see the same curve with minimal divergence, and a cash-out at 2.41x is honoured fairly under latency? 3. Which seamless wallet APIs have you implemented against? Name the platforms or aggregators. 4. How do you handle a debit that succeeds at the operator but times out at your service? Walk through your idempotency and reconciliation approach. 5. Describe your provably-fair seed commitment scheme for a crash game, and how a player independently verifies a past round. 6. Your availability in hours per week, and your time zone. Begin your proposal with the word CAROUSEL so we know you read this post. Proposals that open with a generic pitch are not read.