> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/partner-portal-infrastructure/partner-portal-infrastructure.md).

# Partner Portal Infrastructure

PlayBlock’s Partner Portal infrastructure allows partners to launch fully featured gaming platforms on top of the same core technology that powers [PlayW3](https://playw3.com/) and [PlayQuack](https://playquack.com/).\
Partners can choose between two operational models — **Be the Boss** or **White Label** — while relying on the exact same games, settlement engine, and on-chain infrastructure.

This approach ensures consistency, scalability, and fairness across all portals, regardless of branding or commercial model.

***

### Partner Models

#### Be the Boss Program

The Be the Boss program is designed for partners who want a fast, low-friction launch without managing their own domain or infrastructure.

Key characteristics:

* Each partner receives a dedicated subdomain under the PlayBlock ecosystem\
  (e.g. `partner-name.playw3.com`)
* Fully managed infrastructure (backend, blockchain, payments, monitoring)
* Revenue share model defined per partner agreement
* Shared platform updates and feature rollouts

This model prioritizes speed to market and operational simplicity.

***

#### White Label Portals

White Label portals are built for partners who want full brand ownership and operate under their own domain.

Key characteristics:

* Portal runs on the partner’s custom domain
* Fully branded UI (logo, colors, content)
* Same backend, games, and settlement engine as [PlayW3](https://playw3.com/) / [PlayQuack](https://playquack.com/)
* Independent marketing and user acquisition
* Customizable revenue share terms

Despite the branding independence, White Label portals are not separate systems. They are first-class citizens of the PlayBlock infrastructure.

### Shared Core Infrastructure

Regardless of the partner model, all portals run on the same production-grade stack:

* Identical game catalog (casino, arcade, prediction games)
* Same settlement and accounting logic
* Same GCoin-based reward and balance system
* Same performance, scalability, and reliability guarantees
* Same security, monitoring, and anti-fraud systems

There is no feature downgrade or “partner tier” infrastructure.

### Revenue Share Logic

Revenue sharing varies by partner model and agreement, but is always enforced at the infrastructure level, not via manual reporting.

Typical dimensions include:

* Net Gaming Revenue (NGR)
* Player activity and volume
* Geographic or regulatory scope
* Partner-specific incentive programs

All calculations are:

* Deterministic
* Transparent
* Auditable
* Aligned with on-chain settlement data

This ensures partners and the platform always operate from the same source of truth.

### Isolation & Scaling

While infrastructure is shared, logical isolation is enforced at every level:

* Separate partner identifiers
* Isolated analytics and reporting
* Independent configuration and feature flags
* Controlled access to admin and operational tools

Scaling one partner never impacts another — capacity is elastic and horizontally scalable across the platform.

This unified partner portal infrastructure allows PlayBlock to:

* Launch new partners in days, not months
* Maintain consistent performance and fairness
* Avoid fragmentation of liquidity and game logic
* Ship new features once, deploy everywhere
* Keep settlement, rewards, and compliance deterministic

For partners, it means enterprise-grade infrastructure without enterprise-grade overhead.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.playnance.com/partner-portal-infrastructure/partner-portal-infrastructure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.