How to Create Arbitrage Betting Software: An Honest Build-vs-Buy Guide

By the AUOdds team · Updated 26 Oct 2026 · 7 min read

If you're searching for how to create arbitrage betting software, you probably already know the maths. When two or more bookmakers price every outcome so the implied probabilities add up to under 100%, you can stake across them and lock in a return at the prices shown. The maths is the easy part. The hard parts are getting reliable prices quickly and matching the same event across different sites. You also have to stay inside each bookmaker's terms and keep the whole thing running week after week. This guide walks through each piece honestly. It puts a rough cost and effort picture on a home build, then compares that with subscribing to an alert service. That way you can decide which route suits your time, skills and budget.

How to create arbitrage betting software: what are the moving parts?

Before writing a line of code, it helps to see the whole program. A working scanner is not one script. It is a small system with several jobs that all have to work at once.

• Collectors that fetch prices from each bookmaker on a schedule
• A normaliser that turns every site's format into one shape: event, market, outcome, price and time seen
• An event matcher that recognises the same game and the same market across different books
• An arb engine that checks every matched market for a combined implied probability under 100%
• A stake calculator that splits your total stake so each outcome returns the same amount
• Alerts and monitoring, so you hear about a lock quickly and know when a collector has broken

The arb engine is the simplest piece. Here is the maths it runs on a two-way NRL head-to-head market:

• Bookmaker A: Storm at 2.05, implied probability 1 ÷ 2.05 = 48.78%
• Bookmaker B: Panthers at 2.00, implied probability 50.00%
• Combined: 98.78%, so the market locks at about 1.2%

To split $500, stake $500 × 48.78 ÷ 98.78 = $246.91 on the Storm and $253.09 on the Panthers. Either result returns about $506, which locks in roughly $6 at the prices shown.

That calculation takes milliseconds. Everything around it is where the real work and most of the failures sit. That includes getting both prices and being sure they belong to the same match.

Where does the price data come from, and is collecting it allowed?

Your scanner is only as good as its prices. There are three broad ways to get them.

Paid odds data. Some commercial providers sell odds feeds through an API. This is the cleanest route technically. Check carefully which Australian bookmakers and which markets are covered, and how often prices refresh. Also check what the licence lets you do with the data. Coverage of local books and local sports such as AFL and NRL can be patchy.

Collecting prices yourself. This is what most home-built projects do, and it is the route the abandoned code repos online tend to take. It is also where the practical friction sits. Many websites' terms of use restrict automated access, so read each bookmaker's terms before you point any program at their site. Breaching them can put your account at risk. That matters a great deal when the account is what you need to place the bet. Sites also change their layout and data structures without notice, so collectors break.

Manual comparison. Checking odds by hand across a few books is slow, but it costs nothing and sits within normal use. It is a sensible way to learn how often locks appear before you invest in anything.

Whichever route you take, only include licensed Australian bookmakers. The ACMA lets you check whether a gambling operator is legal to offer services to Australians. An offshore site's price has no place in your scanner. If a lock only exists because of an unlicensed site, it is not a lock you should act on.

Why is latency the hardest part to get right?

An arb exists because prices disagree for a short time. One bookmaker moves its price and another has not caught up yet. Your software is racing that gap, so the age of each price is the number that matters most.

Think about how prices age in a home build. Say you track 9 bookmakers and poll each one every 60 seconds to keep the load light. In the worst case, the two prices behind a lock are each nearly a minute old before the engine even sees them. Then you still have to send the alert, open two apps and type in two stakes. A fresh-looking lock may already be gone by the time you place the second leg.

For comparison, AUOdds data shows prices are about 10 seconds old, with roughly 15,000 prices across 9 bookmakers tracked at any moment. Getting a home build close to that means many more requests, more servers and more ways for things to fail.

Questions to ask of your own design:

• How old is the oldest price in any lock you alert on?
• Do you drop prices that have not refreshed within a set window?
• What happens when one collector stalls but others keep running?
• How quickly does an alert reach your phone?
• Do you re-check both prices before you place a bet?

Prices still move before the start, often sharply in the final minutes as money comes in. Online in-play sports betting is not offered to Australians, so your scanner should only look at pre-match and pre-race markets.

How do you match events and markets across bookmakers?

This is the part most code repos skip. It is also where home-built arb betting software produces its most dangerous false alerts. A price is useless unless you know for certain that it belongs to the same event and the same market as the price on the other side.

Bookmakers name things differently. One lists "Melbourne Storm v Penrith Panthers" and another lists "Storm vs Panthers". A third might use a short code. Start times may be stored in AEST, AEDT or UTC. Tennis players can appear with full names, initials or different spellings. Your matcher needs aliases and time tolerances, plus a way to flag anything it is unsure about.

Markets are harder still:

• Lines. A -3.5 line at one book only pairs with +3.5 at another. Pair -4.5 with +3.5 and a four-point margin loses both legs.
• Totals. Over 42.5 only pairs with under 42.5. Pair over 43.5 with under 42.5 and a total of 43 loses both legs.
• Three-way vs two-way. A soccer win market that includes a draw cannot be paired with a draw-no-bet price.
• Settlement rules. Bookmakers can settle the same market differently, for example when a tennis player retires. Read each book's rules for any market you scan.

A mismatch is worse than a missed lock. Your software shows an attractive margin and you stake both legs, but one result can leave you behind. Build in a human check. Before placing anything, confirm the teams, start time, market, line and rules on both sites.

What does a home-built scanner really cost in time and money?

The code repos and freelancer briefs that show up for this search rarely put a number on the effort. Here is a rough, illustrative budget. Your figures will differ, so treat these as assumptions to replace with your own.

Build phase (assumed)

• Collectors for 9 bookmakers at 8 to 12 hours each: around 90 hours
• Normaliser and event matcher: 40 hours, plus ongoing alias fixes
• Arb engine, stake calculator and alerts: 20 hours
• Testing against real markets: 20 hours

That is roughly 170 hours. If you value your time at $40 an hour, the build costs about $6,800 of your time before you place a bet.

Running phase (assumed)

• Hosting and any paid data, at whatever your providers charge
• Fixing collectors when sites change: say 2 hours a week, or about $350 a month of time
• Adding aliases, new markets and new sports as seasons change

Now look at the return side. At a typical lock of around 1.5%, turning over $10,000 in stakes in a month locks in about $150 at the prices shown. That is before any errors, voids or limits. On these assumptions, upkeep alone can exceed the return for a casual user.

Building can still make sense in some cases:

• You enjoy the engineering and treat it as a learning project
• You already have data access you are entitled to use
• You want to cover a niche market that no service covers

If none of those fit, the cost picture usually points the other way.

What does subscribing to arbitrage betting software save you?

If you look at arbitrage betting software Australia options, the subscription route takes over the collection, matching and alerting work. You get the lock, the bookmakers involved and the stake for each outcome. You spend your time checking and placing bets rather than fixing collectors.

For scale, AUOdds data shows 3,058 locks in the last 30 days and 1,186 in the last 7 days, with a typical lock of 1.5% across 9 licensed bookmakers. Matching that volume yourself would need every piece described above working reliably at once.

When you compare services, ask the same questions you would ask of your own build:

• Which licensed Australian bookmakers are covered?
• How old are prices when an alert goes out?
• Are stakes shown for every outcome?
• How are stale or mismatched alerts handled?

A subscription does not change the risk you carry. Prices move between the alert and the bet. Bookmakers can limit your stakes. Bets can be voided under a book's rules. You can type the wrong stake or pick the wrong line. Each of these can turn a lock into a loss, so check both legs before you commit. If tax is a question for you, the ATO's ruling IT 2655 explains how it treats gambling winnings. Get advice if your situation is unusual.

Arb betting is still gambling, and you must be 18 or over. If betting stops feeling like a choice, BetStop, the National Self-Exclusion Register, lets you exclude yourself from licensed online and phone bookmakers. Gambling Help Online offers free, confidential support at any hour.

Frequently asked questions

Sources

1. Check if a gambling operator is legal, Australian Communications and Media Authority
2. Taxation Ruling IT 2655: gambling and betting winnings, Australian Taxation Office
3. BetStop: the National Self-Exclusion Register, Australian Communications and Media Authority
4. BetStop, Australian Government

More guides

• What Is Arbitrage Betting in Tennis? AU Retirement Rules
• Arbitrage Betting Guide: Splitting a Bankroll Across 9 Books
• Surebet Review: We Score AUOdds Against Our Own Checklist
• Horse Racing Dutch Betting Calculator: Scratchings Fixes

18+ only. Betting involves risk, and prices and limits can change before you place a bet. If gambling isn't fun any more, Gambling Help Online (1800 858 858) is free and confidential, and BetStop lets you exclude yourself from every licensed Australian bookmaker.