Sportsbook software development company: what gets built, in what order, and what to ask

What is a sportsbook platform made of?

A feed can be large: BetConstruct's sportsbook page lists "140K+ pre-match events every month", "90K+ live matches every month" and "120+ sports types"^[4]. Volume like that is why intake, market state and suspensions are engineered as a stream, not loaded as a batch.

Which decisions shape the build?

Rent the prices or trade in-house. Pricing and trading are a desk of people and models, not only software. Rented trading shortens the route to launch and keeps a variable cost; an own desk makes margins and bet types yours and adds traders to the payroll.

Suppliers sell both options: Sportradar's Managed Trading Services page reads "Whether you want to trade in-house or entrust it to us, MTS offers flexibility that's tailored to your needs"^[2]. Kambi's report describes its fee as "based on a number of variables including fixed fees, the number of live events offered and commission based on a revenue share of operators' Gross Gaming Revenue (GGR) less deductible costs"^[3].

Live-event volume, in other words, is a cost line whichever side of the contract you are on, so it belongs in the architecture brief from day one. What the rented sportsbooks publish is on Kambi alternative and BetConstruct alternative.

How acceptance handles a moving price. Live odds change while a player is confirming. The choices are to reject, to accept at the new price only with the player's consent, or to accept within a tolerance. Some markets fix the answer in their technical rules, so the policy is configured per market rather than hard-coded; Brazil's published texts, read for what they ask of the platform, are on Brazil sportsbook platform requirements.

Where the wallet lives. A sportsbook next to a casino should share one wallet and one ledger, or players see two balances and the back office reconciles two systems. Debit on acceptance, credit on settlement, and every call idempotent, so a retried request cannot move money twice. The cashier is part of the same loop, and some regulators close it by rule.

The SPA states that every bettor has to be identified with documents and a "sistema de reconhecimento facial com prova de vida", and has to register a bank or payment account in their own name that is "a origem e o destino de todos os recursos que enviar ou receber da empresa de apostas"; operators are forbidden to accept deposits from any other account^[5].

Settlement as a pipeline. Results arrive in bursts: the final whistle of a popular match settles thousands of bets at once, and a corrected result resettles them. Settlement runs as a queue with idempotent grading and a record of every regrade, separate from the path that accepts new bets. The failure pattern in detail, with the database side, is in settlement lag at match peaks.

Records the regulator can ask for. Retention and backup rules reach into the data model, so they are decided before it exists.

The SPA states that operators must keep an updated backup, for at least five years, of all data relating to bettors and operations, under Annex I of Ordinance SPA/MF 722/2024, updated at least every 24 hours and integrity-tested at least every seven days^[5]. The regulator's own index describes that ordinance as setting the general rules for the operation of betting systems and for supplying data to Sigap^[6].

Certification from the first sprint. Labs test the platform you run, so module boundaries, version identification and release records are architecture decisions, not documentation chores.

GLI-33 v1.1 is the Gaming Laboratories International standard for event wagering systems^[1]. Brazil adds its own layer: the SPA's index lists Ordinance SPA/MF 300/2024 as setting the requirements for authorising the entities that certify betting platforms and online games^[6].

In what order is a sportsbook built?

What shows up late?

• Settlement and bet acceptance share one database table, so a big result slows new bets.
• Result corrections were not designed, and resettlement becomes a manual script.
• Liability is computed in a nightly job while live betting needs it per bet; the live path is described in live betting architecture.
• The feed adapter trusts the feed; duplicates and out-of-order suspensions reach the market.
• Load tests use average traffic instead of the busiest event of the season.
• Nobody owns the list of critical components, so every release becomes a certification question.
• Responsible-gambling limits are bolted onto the front end instead of enforced at bet acceptance; the controls that hold are in responsible gaming technology.

What should you ask a sportsbook development company?

1. 1.What happens when the price changes between the player's tap and acceptance, and how is that configured per market?
2. 2.How are bets resettled when a result is corrected, and what does the audit record show?
3. 3.How is settlement kept from slowing bet acceptance during a big match, and what was measured?
4. 4.Which parts are rented (feed, trading, KYC, payments) and where are the seams if you replace one later?
5. 5.Which standards and markets has the platform design been prepared for, and who talks to the lab?
6. 6.Who owns the code, the data model and the deployment scripts when the work ends?

Who should not build a custom sportsbook?

• An operator who needs one market live quickly and has no plans to change the product: a turnkey sportsbook is cheaper to start, and what a sportsbook platform costs shows the published fees.
• A team without budget for on-call operations after launch: an own sportsbook is a system someone answers for at every match.
• A buyer looking for a licence: licences are held by operators, and a development company does not supply one.
• An operator whose casino side is the larger build: start from custom casino platform development, where the shared wallet and ledger are set out.

Related on this site: iGaming platform case study.

Product and company names are trademarks of their respective owners and are used only to identify their products and published documents. No vendor named here reviewed or endorsed this page. The regulatory passages are an engineering reading of the SPA's own pages, read on 2026-09-23, not legal advice, and nothing here says which operators hold authorisations.