iGaming Software Cost: 12-Month Operator Budget and Vendor Quote Worksheet

The cost of iGaming software is a contract and operating-model question, not a single licence price. Operators need to budget for the platform, games or odds, payment and compliance integrations, hosting, support, changes and the right to leave. A low setup quote can become expensive when minimums, revenue share and migration work are excluded. This worksheet is for business owners and procurement teams comparing a turnkey, white-label or modular stack; it is not a market-wide price list.

Copy the line items below into a spreadsheet and request the same 12-month quote format from every bidder. Record the contract definition of gross gaming revenue (GGR), net gaming revenue (NGR) and chargeable transactions rather than assuming vendors use the same denominator. Jurisdiction, vertical, volume and risk allocation all change the quote.

Choose the operating model before comparing prices

Model	What the operator often buys	Budget question
White label	Brand/front end on a provider-controlled operating stack	Who holds the licence, player relationship, data and exit rights?
Turnkey	Broad platform and operational components with implementation support	Which services are included and which need separate contracts?
Modular	PAM/wallet, casino or sportsbook, payments, compliance and CRM from separate suppliers	Who owns integration, incident response and reconciliation?
In-house build	Operator-developed core with purchased feeds and services	What are the engineering, certification and ongoing support obligations?

Labels are not standardized. A supplier may call a product “turnkey” while excluding licence, payment processing or managed trading. Require a responsibility matrix and bill of materials before comparing headline fees. The cheapest model on a sales slide may transfer the most delivery risk to the operator.

The 12-month software-cost worksheet

Cost line	Ask for	Calculation cell
Platform setup	Configuration, branding, environments, training and go-live	One-time fixed + change requests
Platform recurring	Base licence, brand, market, player, event and support tiers	12 × monthly charge or usage schedule
Revenue share	Exact GGR/NGR definition, exclusions, minimum and audit right	Forecast base × rate, subject to minimum
Casino games or sportsbook	Aggregator/studio/odds fees, minimum guarantees and feed costs	Setup + 12 × fixed + variable
Payments	Gateway, processing, payout, fraud, FX and reserve terms	Transaction mix × fee + liquidity cost
Compliance	Identity, AML, safer-gambling and reporting vendors	Checks/cases/players × contracted price
Infrastructure	Cloud, CDN, observability, backups, security and environments	Usage forecast + support and contingency
Integration	API work, data mapping, testing, certification and rework	Quoted project + contingency
Migration/exit	Data export, token transfer, parallel run and termination assistance	One-time quote or contractual formula

For each row, record the vendor, currency, tax treatment, start date, billing basis, minimum commitment, overage rate, escalation clause, owner and documentary source. Keep unknown visible. An empty cell should trigger a question, not an invented “industry average.” Public supplier pages such as Aggregator.gg’s pricing page can illustrate one vendor’s disclosed model, but should not be extrapolated to the whole market.

A worked example—arithmetic, not a market quote

Suppose a purely hypothetical operator receives these invented numbers: $20,000 one-time platform setup, $4,000 monthly base, 4% of a hypothetical $1.2 million annual contract-defined NGR, $15,000 one-time integration and $6,000 annual support. The simple first-year sum is $20,000 + $48,000 + $48,000 + $15,000 + $6,000 = $137,000. That does not include games or odds, PSP charges, reserves, compliance checks, hosting, staff, tax, licences, marketing or migration. It is a formula demonstration, not a typical price or expected budget.

Now run downside and upside scenarios. If contract-defined NGR falls below plan, does a monthly minimum replace the percentage? If volume rises, do event, player or support tiers change? If a second brand launches, is the platform base charged twice? Model cash timing as well as accounting expense, especially for PSP reserves and settlement delay. A 12-month total without these sensitivities is not a decision tool.

Where quotes most often hide risk

• Revenue definitions: Ask for sample transactions showing bonus, jackpot, tax, chargeback, refund and fee treatment in the revenue-share base.
• Minimums: Identify whether a fixed minimum and percentage are additive or the greater of two amounts; model launch months separately.
• Integration ownership: A platform may provide an API while the operator still pays to map wallet, payments, games, compliance and reporting events.
• Market expansion: New currencies, languages, payment methods, regulators and hosting locations can create change fees and extra review.
• Support and availability: Confirm which response times are included, who handles incidents outside business hours and whether service credits have useful remedies.
• Data portability: A low monthly fee can be offset by expensive exports, limited token transfer, long notice periods or a mandatory parallel-run period.

Ask bidders to show a redlined sample contract and an illustrative invoice. A contract with vague “additional services at prevailing rates” is not quote-complete. Require written treatment of overages, project delays caused by each party and post-termination support for disputes and regulatory evidence.

Separate casino API cost from the rest of the stack

Game aggregation can be a major variable component, but it should not be blended into the platform line. Direct studio, aggregator and turnkey arrangements may allocate setup, revshare, minimum guarantees and QA differently. Our casino games API cost worksheet breaks out those quote fields and technical tests. Use it as a separate tab and then roll its contracted totals into the master 12-month model.

Likewise, a gateway integration quote is not the same as processing fees. The integration project covers event flow and reconciliation; the processor contract covers underwriting, acquiring route, settlement, reserves and transaction economics. Keep them separate even if one company sells both.

Acceptance tests before a price is comparable

• Demonstrate a complete registration-to-withdrawal journey in the target market, with identity and safer-gambling controls where applicable.
• Show how wallet, game or bet settlement, refunds and reversals reconcile at transaction level.
• Test duplicate events, late updates and a failed supplier connection without creating inconsistent balances.
• Export player, transaction, ledger and marketing-consent data in documented formats and exercise an exit rehearsal.
• Show a named implementation plan, security responsibility matrix, support escalation and evidence-retention process.

Scoring price before these tests rewards a quote that omits necessary functions. Mark each capability demonstrated, documented, planned or unavailable. A planned feature should not be priced as if it were already in production.

Questions to send every vendor

• What is included in the quoted licence for our exact legal entity, markets, brands and verticals?
• How is every variable fee calculated, and can we audit the input data?
• Which third-party contracts must we sign and pay separately?
• Which integrations are certified and live today, and which need new work?
• What happens financially if launch slips, volume differs or a market becomes unavailable?
• How do we export data, transfer operations and close the contract without losing access to evidence?

Frequently asked questions

How much does iGaming software cost? There is no defensible single figure without product scope, licence, markets, deployment model, volume and contract terms. Request line-item quotes and run the 12-month formula above with your own inputs.

Is white label always cheaper than turnkey or modular? Not necessarily. It may lower initial work but change revenue share, control, data ownership and exit cost. Compare the same operating obligations across models.

Should we choose the lowest first-year total? Only after mandatory controls and exit rights pass. A cheaper quote that excludes a critical integration or reliable support is not the same product.

Method note: This is a budgeting framework, not vendor pricing research or financial advice. The numeric example is explicitly invented for arithmetic. Any real quote, licence rule or third-party price should be verified with the responsible provider before procurement. Sources and framework were reviewed on 17 September 2026.