These guides map an industry's concepts onto the objects the platform has today (bouquets, lines, packages, partner accounts, nodes, the API). They are conceptual mappings, not industry-specific features, and a partner account is a delegated account, not an isolated tenant.
Conceptual mapping
Nothing in the panel is called a stage or a ticket. The table says which object plays which role; the chapters below set them up in that order.
| In your industry | On the platform | Where in the panel |
|---|---|---|
| Stage channel | Live channel: a stream with its sources, EPG and output formats | Streams → add a live stream (source URL or RTMP push) |
| Ticket type | Bouquet: a named set of channels, films or series that a package grants | Bouquets, from Streams and Movies / Series |
| Ticket or pass | Line: one access with its package, bouquets, expiry, connection limit and outputs | Lines → add, or activation codes, or the Reseller API |
| End of the event | Expiry date of the line, renewed by a package, a credit or the API | The line's expiry date and the package's duration |
| Devices per ticket | Max connections of the line: how many devices may watch at once | The line's max connections |
| Ticketing or registration integration | Reseller API and webhooks: the operations of the panel from your own system | Reseller API keys and webhooks in the reseller's dashboard |
| Venue node | Streaming nodes: edge servers enrolled from the panel, one per site or building | Servers → add a node, installed over SSH |
Prerequisites
What to have before installing.
- A server (Ubuntu 22.04 or 24.04) with a public address or a domain and uplink for the expected peak audience, and, for a venue node, a machine on the venue's network.
- An encoder per stage that can push RTMP, and the list of stages, days and ticket types.
- A decision on how tickets reach the panel: activation codes generated in bulk, or the ticketing system calling the Reseller API.
Infrastructure deployment
The origin first, then the venue.
- Run the installer on the management server and put the panel behind a reverse proxy with TLS; set the trusted proxies so IP rules see the viewer's real address.
- Set the playback base URL to the public address attendees reach.
- Enrol a node from Servers on the machine at the venue; the panel installs it over SSH, and the local screens are routed to it.
- Create a partner account (reseller) for the ticketing desk with permissions for lines and none for the catalogue.
Content organisation
Stages as channels, tickets as packages.
- Add categories per day or per track so the channel list reads like the programme.
- Create one bouquet per ticket type: the stages that ticket may watch.
- Create one package per ticket type with the length of the event as its duration, and a trial package for press and speakers if needed.
- Create a bouquet for the sponsors' stage or lounge feed and grant it only through the sponsor package.
Partner (reseller) configuration
The ticketing desk, if it issues the access.
- Create a group with line permissions and no catalogue permissions for the ticketing desk.
- Add the desk as a reseller with that group and enough credits for the codes it will issue.
- A co-organiser or a regional partner that sells its own tickets gets its own partner account and its own packages.
Attendee access configuration
One line per ticket.
- Generate activation codes in bulk, one per ticket, each tied to the package of its ticket type, and print or e-mail them with the ticket.
- For online ticket sales, install the connector of your commerce platform, or have the ticketing system call action=create_line with the package and a request id.
- Set max connections to one or two devices per ticket so a code cannot be shared across the audience.
- Test with a trial line before doors open, using the same player the attendees will use.
Session recordings
Recordings after the event.
- Record each stage and add the files to the library as episodes of a series per track, or ingest them with the VOD ingest job.
- Grant the recordings through a bouquet and a package of their own, so attendees keep access after the live lines have expired.
- Check playback of the recordings with a test line of that package before announcing them.
Stage channels
A stage as a live channel.
- Add a live stream per stage with the encoder's RTMP push, and place it in the bouquets of the ticket types that may watch it.
- Enable catch-up so an attendee who missed the start of a session can rewind.
- Check before the first session that the venue node takes each stage once from the origin and that the screens are routed to it.
Expiry
Access ends with the event.
- Give every ticket package a duration that ends with the last day of the event, so the lines lapse without any work.
- Extend one line, or issue a short-lived code, for a speaker or a late sponsor instead of making a new package.
- Disable a lost or shared ticket's line from Lines; the audit log keeps the record.
Integration with ticketing
Systems drive access; the player plays.
- The ticketing or registration system creates lines through the Reseller API and listens to webhooks such as line.created and line.expired.
- Online ticket sales on a supported commerce platform use its connector; there is no native connector for a specific ticketing product.
- There is no single sign-on for viewers: an attendee signs in to the player with the credentials of the line or with an activation code.
Security considerations
A ticket is one person.
- Serve the panel and the playback base URL over TLS and set TRUSTED_PROXIES to your reverse proxy.
- Two-factor sign-in for every panel account, and permission groups so the ticketing desk cannot change the stages.
- Signed and expiring playback links and a low connection limit per ticket.
- Encrypted database backups with an off-site copy, and the audit log for every change of lines and stages.
Troubleshooting
The usual first checks.
- An attendee cannot open a stage: check the line's package, the bouquet that holds the stage, and the expiry date.
- A stage freezes in the room but not online: check the venue node's heartbeat and the screens' route to it.
- An activation code is refused: check that it has not been used already and that its package is still valid.
- The audit log shows the proxy's address: set TRUSTED_PROXIES to the proxy and restart the panel.