Explainer
iGaming Software Explained: Platform, PAM, RGS and Game Aggregator

The short answer
An iGaming platform coordinates operator services; PAM handles the player-account layer; an RGS supplies server-side game services; and an aggregator connects game content through a distribution layer. Vendor products can combine several roles, so a useful comparison names both the product and its included functions.
In this article
An iGaming software stack becomes easier to understand when it is divided into jobs. One component manages accounts, another delivers game content, and another provides the services behind an individual game. A supplier may offer several of those jobs within one commercial package.
The four terms that organize most introductory conversations are platform, PAM, RGS and aggregator. Mapping them to real products gives the vocabulary substance. Following one clearly labeled sample session then shows how the pieces can work together.
Four software roles and the questions they answer
PAM stands for player account management. RGS stands for remote game server. “Platform” is a broader product label, while “aggregator” describes a content-connection role.
| Role | Main question it helps answer | Example item to discuss |
|---|---|---|
| Operator platform | How are the operator's services coordinated? | Account, reporting and integration scope |
| PAM | How is the customer account managed? | Identity, account state and wallet services |
| RGS | How are server-side game services supplied? | Hosted game service and play records |
| Aggregator | How is content connected and distributed? | Supplier connections and content routing |
This is an editorial map of functions, rather than a mandatory diagram for every supplier. A particular architecture can combine roles or connect specialized services. The product schedule and technical documentation explain that actual arrangement.
That distinction is useful when researching the market. A company offering game content, a casino-management system and an account platform participates in several categories. Naming the product provides a more precise comparison than using the company name alone.
Real products make the categories concrete
Playtech PAM+ describes centralized management of the player lifecycle through a single account and wallet. It provides a direct example of the account-management layer. PAM+ product page.
EveryMatrix Aggregation, also presented through SlotMatrix, describes content access through a single integration with a platform. EveryMatrix Casino, associated with CasinoEngine, is presented separately as casino-management and integration software. The two pages demonstrate distinct product scopes within one supplier. Aggregation, casino management.
Promatic GamePRO supplies a concrete RGS example. Its November 2023 announcement describes server-based game hosting, reporting services and infrastructure options. GamePRO announcement.
These are examples of published product descriptions. Their value here is explanatory: each makes a software role tangible. An operator considering a specific US deployment would connect those capabilities to its actual market, configuration and approval documentation.
Follow a sample game launch through the stack
Consider an imaginary operator called Example Casino. It uses a separate account platform, aggregation connection and game server. This is an original architecture example chosen to explain the roles.
A customer signs in through Example Casino's account service. The account layer provides the relevant account state for the session. The customer then selects a game from the operator's catalog.
The catalog entry identifies a game supplied through the aggregation route. The aggregator helps connect that content to the relevant game service. The RGS supplies the server-side game services for the selected title under the agreed integration.
For this sample design, the components keep references that allow the operator to associate the player session, game identifier and play records. A later report can connect the activity to the relevant product and accounting period.
| Sample reference | What it identifies |
|---|---|
| Account ID | The operator account in this example |
| Session ID | The particular login or game session |
| Game ID | The selected content item |
| Round or play reference | The individual recorded game activity |
| Reporting period | The time window used by the report |
Actual field names and responsibilities come from the relevant integration specifications. The sample is useful because it shows why a game catalog, an account service and a game server can all contribute to one visible experience.
Compare suppliers by scope, connections and records
A practical software comparison begins with the work to be done. List the required account services, content connections, hosting arrangements and reporting outputs. Then associate each requirement with the product expected to supply it.
For example, a content discussion might ask which studios are included in the proposed catalog and how game identifiers are mapped. An account discussion might focus on the wallet and lifecycle services. A reporting discussion might identify which component produces each data extract.
The resulting comparison sheet can contain six columns:
- Required function.
- Named supplier product.
- Included service.
- External connection.
- Supporting document.
- Commercial fee line.
That last column connects technology to the revenue-share and flat-fee comparison. Assessment documentation has its own role; the gaming laboratory guide explains how a defined build relates to a technical report.
For the data handoff, our software version-trail article supplies additional context on identifying releases. Together, those documents turn a broad technology conversation into a concrete product specification.
A content-specific example appears in our live-dealer industry overview, which provides additional context for discussing a defined game category within the stack.
Frequently asked questions
What is an iGaming platform?
It is a supplier's system or product bundle for operating defined gaming services. Its actual functions are established by its product description and service schedule.
What is an RGS in iGaming?
A remote game server supplies server-side game services. Promatic's GamePRO announcement is one published example of an RGS offering.
How does an aggregator differ from a game studio?
The aggregation role connects and distributes content. A studio creates game content. A supplier can participate in both activities, so identify the named product and role being discussed.
What belongs in an iGaming software market comparison?
Separate account platforms, casino-management software, game-serving technology and content aggregation. Then compare actual product scope, connections, reporting and commercial components within each category.


