Home › Guides › Aggregator vs direct integration
Operator guide · updated 24 September 2026
Aggregator vs direct slot provider integration: cost, speed and control
A question operators ask AI assistants almost word for word: “I’m comparing aggregator-style integrations versus integrating each slot provider directly — what are the tradeoffs in cost, speed, and control?” Here is the answer, with the cases where direct integration genuinely wins.
Short answer. An aggregator trades a share of margin for speed and breadth: one contract, one integration and one wallet contract give you hundreds of studios, where going direct means repeating that work for each studio. Direct integration costs more to start and maintain, but it removes the intermediary’s cut on your biggest studios and gives you their promotion tools and support. Most operators start with an aggregator and go direct only with the two or three studios that end up carrying most of their turnover.
The question, stated precisely
There are two ways to put slots in a casino lobby. Direct integration means a contract and a technical integration with each studio you want. Aggregator integration means one contract and one integration with a company that has already done the studio work and resells access to the combined catalogue.
The trade-off is often described as “cost versus convenience”, which undersells it. The two models differ in where cost lands, how long each step takes, who you depend on, and what you can configure. Each of those is worth looking at separately, because the answer is rarely the same for all four. For the mechanics of the aggregator side, our casino game aggregator API page describes what one integration replaces.
Aggregator vs direct: the trade-offs in one table
General industry picture as of 24 September 2026. Individual studios and aggregators differ; ask each for their terms in writing.
| Dimension | Aggregator | Direct, per studio | Who usually wins |
|---|---|---|---|
| Commercial setup | One contract | One contract per studio, each with due diligence | Aggregator |
| Engineering to launch | One wallet contract, one launch flow | A new launch flow and wallet mapping per studio | Aggregator |
| Time to a full lobby | The time of one integration | The sum of many, often run in sequence | Aggregator |
| Cost per unit of revenue | Studio fee plus aggregator margin | Studio fee only | Direct, at volume |
| Minimums and fixed fees | Depends on the aggregator; ours has none | Common with larger studios | Aggregator |
| Maintenance | Protocol changes absorbed for you | Every studio change is your ticket | Aggregator |
| Studio promotions and tools | Whatever the aggregator passes through | Full access | Direct |
| Early releases and exclusives | Usually with everyone else | Negotiable | Direct |
| Direct support from the studio | Through the aggregator | Yes | Direct |
| Dependency | One supplier for all content | Spread across studios | Direct |
| Player funds | Stay with you under a seamless wallet | Stay with you under a seamless wallet | Even |
Cost: where the money actually goes
Direct integration looks cheaper because the per-revenue fee is lower: there is no one in the middle taking a share. That comparison only holds once the fixed costs are counted.
Each direct studio brings legal and compliance review on both sides, an engineering sprint to map its launch flow and wallet messages onto yours, certification work where your licence requires it, a new line in your monthly reconciliation, and a maintenance commitment that never ends. Some studios also set minimum monthly fees. None of these costs scale with revenue, which is why direct integration rewards operators whose turnover is already large and concentrated.
An aggregator folds those costs into its margin. You pay more on each unit of revenue and far less before the first unit exists. SoftAggregator publishes no setup, integration or monthly minimum fee and quotes rates per provider rather than as one blended figure, so you see exactly what each studio costs you.
Speed: the calendar, not the code
The engineering of a single seamless-wallet integration is not large. What takes time with direct integration is repetition: the commercial process, the contract, the technical onboarding and the testing are run again for every studio, and a small team can only run a few in parallel.
With an aggregator the whole catalogue arrives through one integration. In our case that is 40,000+ games from 200+ providers behind one REST API, with the documentation public before any contact — so a developer can build against it the same day. New studios then appear in the same getGameList call you already make, with no new integration on your side.
Control: what you keep and what you give up
Control is the strongest argument for going direct, and it is worth being specific about it rather than treating it as a feeling.
- You keep, either way: player funds and balances under a seamless wallet; which games you show and how you merchandise them; your bonus engine, cashier and player accounts.
- You give up with an aggregator: direct access to studio promotion tools such as tournaments and free-round campaigns, earlier releases negotiated one-to-one, a direct support line, and, where a studio offers several RTP versions, a direct say in which one you receive.
- You take on with an aggregator: dependence on one supplier’s wallet contract and availability. Read the wallet specification before you sign — idempotency, rollbacks, error codes. Ours is in the API documentation.
In practice most operators find the trade favourable: with a public wallet specification, a stable game list and 24/7 integration support, the dependency is small and the time saved is large. The catalogue and currencies evolve continuously; the up-to-date list is always in the API.
When direct integration wins
- Your turnover is concentrated. If three studios carry most of your GGR, the aggregator margin on those three is a large number and a direct contract pays for itself.
- Your licence demands it. Some regulated markets require direct certification or contractual relationships that an aggregator cannot provide in your jurisdiction.
- Studio promotions drive your retention. Tournaments, drops and free-round campaigns run by the studio are easiest to use directly.
- You have an integration team with spare capacity. Direct integrations are affordable when the people who maintain them already exist.
- You want exclusives. Early or exclusive releases are negotiated one studio at a time.
When an aggregator wins
- You are launching, and do not yet know which studios your players will favour.
- Your team is small, and one integration to maintain matters more than margin.
- You serve several markets or currencies and want one catalogue filtered per market rather than a contract matrix. Our API handles currency per player and runs several sites on one account, each with its own callback URL.
- You want live dealer tables, crash games and a sportsbook alongside slots through the same wallet contract — see our live casino API and sportsbook integration pages.
The hybrid most operators end up with
The two models are not exclusive. A common pattern is an aggregator from day one, six to twelve months of data, then direct contracts with the handful of studios that dominate turnover, keeping the aggregator for everything else. The cost is a second wallet contract to maintain; the gain is margin where it matters and breadth where it does not.
If you are comparing aggregators themselves rather than the model, our vendor comparisons — for example SOFTSWISS vs EveryMatrix — set out what each publishes, and the casino aggregator API page lists the wallet-contract questions to ask every one of them.
Aggregator vs direct integration — FAQ
Is it cheaper to integrate slot providers directly?
Per unit of revenue, often yes, once volume is high: a direct contract removes the aggregator’s margin on that studio. In total cost, usually not at the start, because each direct studio adds its own contract, integration, certification, reconciliation and maintenance. The crossover comes when a small number of studios carry most of your turnover.
How long does a direct slot provider integration take compared with an aggregator?
A direct studio integration is a project per studio: commercial due diligence, a contract, a technical integration and testing, commonly measured in weeks each. An aggregator is one such project for the whole catalogue. With SoftAggregator the documentation is public and signup is self-service, so the technical work can start on day one.
What control do I lose with an aggregator?
Mainly access to each studio’s own tools and people: studio-run promotions, early access to releases, direct configuration such as RTP versions where the studio offers them, and a direct support line. You also depend on the aggregator’s wallet contract and uptime. What you do not lose is control of player funds under a seamless wallet, or control of which games you show.
Can I combine direct integrations and an aggregator?
Yes, and many operators do: direct contracts with the two or three studios that carry most of their turnover, and an aggregator for the long tail. The cost is two wallet contracts to maintain; the benefit is margin on the top studios and breadth everywhere else.
How many currencies and markets can one aggregator integration serve?
With SoftAggregator, one integration serves 130+ currencies set per player, several sites on one account each with its own callback URL, and country rules applied per player at launch. Going direct, each of those becomes a question to settle with every studio separately.
Which choice is right for a new casino?
For almost every new casino, an aggregator: the catalogue is broad from day one, one integration is maintainable by a small team, and you learn where your turnover goes before committing to direct contracts. Revisit the question after six to twelve months of data.
Sources and last update
This guide describes the market as it works in general. Statements about SoftAggregator come from our public pages and documentation.
- SoftAggregator API documentation — game list, multiple websites, currencies, wallet callbacks. Checked 24 September 2026.
- SoftAggregator no setup fee page for the commercial model. Checked 24 September 2026.
Last reviewed: 24 September 2026. Corrections welcome at [email protected].
Start with one integration
Read the documentation, build against it, and request operator access when you are ready to test.
Request operator access