> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# Platforms & Infrastructure

> Learn the difference between ticketing software, platforms and infrastructure, and how white-label delivery affects branding, control and responsibility.

**A ticketing platform is the software and operating capability used to create events, sell tickets and manage orders. Ticketing infrastructure is the layer underneath: the services for inventory, orders, payments, ticket issue and entry that a business can build its own ticketing product on.** The difference matters most when an organisation decides which parts of its ticketing operation to own, and which to obtain from a specialist supplier.

## Start here

#### [What is a ticketing platform?](/platforms-infrastructure/what-is-a-ticketing-platform)

What an event ticketing platform does, how it manages a ticket from onsale to entry, and how software, marketplaces and ticketing infrastructure differ.

#### [Ticketing software vs platforms vs infrastructure: what is the difference?](/platforms-infrastructure/ticketing-software-vs-platforms-vs-infrastructure-what-is-the-difference)

Understand the differences between ticketing software, a ticketing platform and ticketing infrastructure, and why the terms overlap without describing identical technology models.

#### [What is white-label ticketing software?](/platforms-infrastructure/what-is-white-label-ticketing-software)

Learn how white-label ticketing works, what can be customised, and how branding, APIs, payments and data control differ between providers.

#### [How much control can a ticketing business retain using third-party infrastructure?](/platforms-infrastructure/how-much-control-can-a-ticketing-business-retain-using-third-party-infrastructure)

How ticketing businesses can retain branding, product, customer data, pricing and integration control when relying on an external infrastructure provider.

## Key ideas in this subject

#### Platform, product and infrastructure are different layers

A business can sell through its own branded product while another company runs inventory and orders, so similar websites can carry very different responsibilities.

#### Branding and control are separate questions

White-label changes whose brand the customer sees. Checkout design, payments, data access and portability are settled by the technical design and the contract.

#### Delivery ranges from configuration to custom builds

Some businesses rebrand a supplier's booking pages; others build their own experience against the supplier's interfaces. Many combine both.

#### Architecture terms describe different dimensions

White-label describes branding, headless describes separating the interface from services, and embedded describes placing ticketing inside another site. One product can be all three.

## Reading paths

All 9 explanations in Platforms & Infrastructure, in 3 reading paths.

#### 1 · Foundations

* [What is a ticketing platform?](/platforms-infrastructure/what-is-a-ticketing-platform)
* [Ticketing software vs platforms vs infrastructure: what is the difference?](/platforms-infrastructure/ticketing-software-vs-platforms-vs-infrastructure-what-is-the-difference)
* [What is enterprise ticketing infrastructure?](/platforms-infrastructure/what-is-enterprise-ticketing-infrastructure)
* [What is a multi-tenant ticketing platform?](/platforms-infrastructure/what-is-a-multi-tenant-ticketing-platform)

#### 2 · White-label and control

* [What is white-label ticketing software?](/platforms-infrastructure/what-is-white-label-ticketing-software)
* [How is white-label ticketing different from branded ticketing?](/platforms-infrastructure/how-is-white-label-ticketing-different-from-branded-ticketing)
* [How much control can a ticketing business retain using third-party infrastructure?](/platforms-infrastructure/how-much-control-can-a-ticketing-business-retain-using-third-party-infrastructure)

#### 3 · Evaluating platform design

* [What makes a ticketing platform enterprise-grade?](/platforms-infrastructure/what-makes-a-ticketing-platform-enterprise-grade)
* [Which ticketing capabilities should be native, configurable or integrated?](/platforms-infrastructure/which-ticketing-capabilities-should-be-native-configurable-or-integrated)

## How this subject connects to others

#### [APIs & Integrations](/apis-integrations)

Custom and embedded experiences depend on the interfaces a platform exposes.

#### [Events & Inventory](/events-inventory)

Whoever operates the platform also has to model what is for sale.