Solutions
One streaming infrastructure, configured for the people it serves. Pick your industry to see what the platform does there, how a deployment looks and how to set it up — then the two programmes beside the price list: a free Professional licence for education and the hotel TV deployment on Enterprise.
Solutions
Every industry has its page and its setup guide: what it has to solve, how the platform is configured for it, and an example deployment.
Education & Training Course video, live classes and campus TV for schools, training providers and universities. 
Hotels & Resorts In-room television with the property's channels, information and guest services. 
Corporate Training Internal video, training libraries and live sessions for employees, by department. 
Broadcasting & Television OTT distribution of a broadcaster's own channels and archive, over its own infrastructure. 
Community Organisations Live events, assemblies and recordings for members, at the venue and at home. 
Fitness & Wellness Live classes and a library of recorded sessions for members of a studio or a chain. 
Sports Clubs & Academies Matches, training sessions and analysis video for members, players and families. 
Live Events Conferences, festivals and ceremonies streamed to ticket holders and partners. 
Media & Content Creators A studio's own channel and library, sold directly to its audience. 
Residential Communities Television and information for the residents of apartments, campuses and senior housing. 
Museums & Cultural Centres Exhibition video, archives and events for visitors and members. 
Retail & Franchise Networks Store screens and staff training video across a network of locations. 
Healthcare Patient television and information by bed, with the hospital's own content. 
Universities & Campuses Campus-wide television, lecture archives and halls of residence on one platform. 
Public Sector Council sessions, public information and training for institutions and their public. 
Telecom & ISPs A television service for an ISP's subscribers, on the operator's own network and nodes. Industry setup explorer
Choose an industry: the recommended deployment, how its concepts map onto bouquets, lines and partners, the configuration to look at, the integrations and the security points, and the setup guide.
Management server on the campus network, one streaming node per building, lecture captures and uploads as sources, the student system connected through the API.
Series and episodes for courses; bouquets per course collection; packages per programme with the access period as duration; lines with a concurrent-session limit; activation codes for enrolment day.
Reseller API from the student information system or LMS; webhooks for created, expiring and expired access; connectors for a commerce platform when courses are sold.
Connection limits and address binding on lines, signed playback links, staff accounts with two-factor and permission groups, personal data kept in the student system.
Central management server on the property network, a streaming node per building or wing, licensed channel feeds and hotel videos as sources, the PMS connected through the API.
One package per room category; bouquets of licensed channels and hotel videos; one line per room named by room number, with the stay as expiry and a single connection; nodes per wing.
Reseller API from the PMS for check-in and check-out; webhooks on line changes; the guest-service application and its back-office integration on the Enterprise plan.
One connection per room bound to the device, signed playback links, channels kept inside the property, staff accounts with two-factor and limited permissions.
Management server at headquarters, a streaming node per office, uploaded recordings and the auditorium feed as sources, HR or the LMS connected through the API.
Bouquets per department collection; packages per role; lines per employee with the contract end as expiry and a device limit; categories and series for the library.
Reseller API from HR or the LMS; webhooks on access changes; Admin API keys for internal tooling.
Platform on the internal network, signed and expiring playback links, device limits, two-factor and permission groups for staff, audit log, confidential bouquets granted by package only.
Origin next to the playout, a streaming node per region with GeoIP routing, playout feeds and the archive as sources, partners connected through their accounts and the API.
Live channels with EPG and catch-up settings; bouquets per channel bundle; packages per offer; country rules on lines; nodes per region; the VOD ingest job for the archive.
RTMP and transport-stream ingest, XMLTV EPG, Reseller API and webhooks for partners, the subscriber APIs for the viewers' apps.
Signed viewer-bound links, connection limits, GeoIP and ISP rules, brute-force blocking, two-factor and audit log for the panel; no DRM.
One server with the panel and the origin, the hall's encoder pushing RTMP, members watching on their devices, a node added when the audience grows.
One live channel per venue; bouquets for members and for the public programme; packages with the membership year as duration; lines or activation codes per member; categories per year for the library.
RTMP from the encoder; a commerce connector or the Reseller API from the membership tool; webhooks on access changes.
Connection limits, signed and expiring playback links, member-only bouquets, two-factor and limited permissions for volunteers.
Management server at the head office, each studio pushing RTMP, members on their devices, the commerce platform connected through a connector; a node for a large chain.
Live channels per studio room; bouquets per schedule and programme; packages per membership with its period as duration; lines with a connection limit; categories by instructor for the library.
A commerce connector or the Reseller API from the shop; webhooks on access changes; RTMP from the studios' encoders.
Connection limits per membership, signed and expiring playback links, studio accounts limited to their own members, two-factor and audit log at the head office.
Management server at the academy, stadium and training-ground encoders pushing RTMP, members and families on their own devices, the club's shop connected through a connector; a node when match days are busy.
Live channels per pitch camera; bouquets per squad and per match day; packages per membership with the season as duration; lines with a connection limit; categories by team and season for the analysis library.
A commerce connector or the Reseller API from the club's shop; webhooks on access changes; RTMP from the encoders at the ground.
Squad material granted by package only, connection limits per membership, signed and expiring playback links, coaching accounts limited to the library, two-factor and audit log for staff.
Management server before the event, an encoder per stage pushing RTMP, a node in the venue for the local screens, ticketing connected through the Reseller API; attendees on their own devices.
Live channels per stage; bouquets and packages per ticket type; activation codes in bulk; lines with a short expiry and a connection limit per ticket.
Reseller API and webhooks from the ticketing or registration system; the connector of a commerce platform for online ticket sales; RTMP from the stage encoders.
Short expiry on every ticket, connection limits per code, signed and expiring playback links, staff accounts with two-factor and permission groups, audit log.
Management server, the studio's playout pushing RTMP, supporters on their own devices, the shop connected through a connector, affiliates as partner accounts; nodes where the audience grows.
A live channel for the 24/7 programme; series per show; bouquets and packages per tier; lines with a connection limit and the billing period as duration; categories per genre.
A commerce connector or the Reseller API from the shop; webhooks on access changes; RTMP from the playout; partner accounts for affiliates.
Connection limits per subscription, signed and expiring playback links, affiliate accounts limited to their own lines, two-factor and audit log for the studio.
Management server at the management company, a node in each building, licensed feeds and an information channel as sources, the housing or billing system connected through the API.
Bouquets per kind of home; packages per kind of home with the lease period as duration; a line per apartment with a connection limit; an information channel in every package.
Reseller API from the housing or billing system; webhooks on expiring lines; a commerce connector for extra packages; RTMP for the information channel.
Connection limits per apartment, signed and expiring playback links, managers limited to their own homes, two-factor and audit log for management staff.
Management server in the museum, gallery screens on the local network, an archive library and a live channel from the lecture hall, a desk system connected through the API.
A bouquet for the galleries and one for members; packages per membership with its period as duration; activation codes sold at the desk; categories per exhibition and year.
Reseller API from the shop or membership system; a commerce connector for online memberships; webhooks on expiring lines; RTMP from the lecture hall.
Local-network operation, signed and expiring playback links, connection limits per membership, address binding of gallery screens, two-factor and audit log for staff.
Management server at the head office, a node per region, the store channel and training recordings as sources, franchisees as partner accounts, a franchise or HR system connected through the API.
A store channel bouquet; training bouquets per role; a package per kind of store and per role; one line per screen with a connection limit; categories per topic for the library.
Reseller API from the franchise-management or HR system; webhooks on expiring lines; RTMP for the store channel; a commerce connector to bill franchisees.
Connection limits per store, signed and expiring playback links, address binding of store screens, franchisees limited to their own lines, two-factor and audit log at the head office.
Management server in the data room, a streaming node per wing, licensed channel feeds and the hospital's own videos as sources, all on the hospital network.
Bouquets per ward line-up and one for hospital information; packages per ward type; a line per bed or ward television with a connection limit of one and a long expiry.
Reseller API for any system that creates or disables lines; webhooks on changes; Admin API keys for internal tooling; no native hospital-system integration.
No patient data in the panel, platform kept on the internal network, address-bound lines, signed and expiring playback links, two-factor and permission groups for staff, audit log, encrypted backups.
Management server on the main campus, a streaming node per campus and per hall of residence, campus feeds and lecture recordings as sources, the student-information system connected through the API.
Bouquets per faculty and for the campus line-up; packages with the semester as duration; lines per student with a device limit; series and categories for lecture archives.
Reseller API from the student-information system; faculties as partner accounts; webhooks on access changes; Admin API keys for internal tooling.
Platform on the campus network, signed and expiring playback links, device limits, two-factor and permission groups for faculties and staff, audit log, encrypted backups.
Management server in the institution's data centre, the chamber's live feed and recordings as sources, optional nodes for remote sites, the institution's systems connected through the API.
A public bouquet for sessions and information, bouquets per department for training; packages for residents and for staff; lines with a long expiry and a connection limit; a series per body for the archive.
Reseller API from the institution's website and systems; webhooks on access changes; Admin API keys with a read-only flag for reporting.
Platform on the institution's infrastructure behind a reverse proxy, public and internal material in separate bouquets, signed and expiring playback links, two-factor and permission groups, audit log, encrypted backups.
Management server in the operator's core site, a streaming node per point of presence, channel feeds and the VOD library as sources, billing connected through a connector or the API.
Bouquets per tier and add-on; packages per subscription with their duration and price in credits; lines per subscriber with a connection limit; dealers as partner accounts with credits.
Open-source connectors for billing and commerce systems; Reseller API and webhooks for anything else; Admin API keys for provisioning tools.
Signed and expiring playback links, connection limits per subscription, address, country and ISP binding, trusted proxies, two-factor and permission groups for staff and dealers, audit log, encrypted backups.
Education programme
Schools, colleges, universities and research institutes run the full Professional plan at no cost: a licence key valid for two years, issued to the institution, for campus TV, lecture libraries and teaching labs.
Education · free
For a growing service with its own resellers.
instead of $49 / month
The key is issued by hand after we check the institution; nothing is charged, no card is asked for.
Live channels, the campus channel and announcements on the screens of halls, libraries and common rooms, one bouquet per building.
Recorded lectures and course videos as a VOD catalogue with series, seasons and episodes, watched on any device a student already has.
A real IPTV / OTT platform for media, networking and IT courses: students run the panel, the nodes and the APIs hands-on.
One line per room or per student, activation codes for move-in day, expiry at the end of term, and no sharing between rooms.
Send the request from a mailbox on the institution's domain, with the name of the institution and the campus it is for.
A few lines on the use: campus TV, a lecture library, a lab — and roughly how many screens or students.
After a short check you get a Professional key for two years, issued to the institution, by e-mail.
Install the panel on your own server with the public installer, enter the key, and add your first channels and lines.
Hospitality
Live TV and a film library in every room, plus the services a guest expects from the remote: call the staff, ask for housekeeping, order from the menu, check out. Built with you on the Enterprise plan, branded for the property, managed from one panel.
Enterprise · hospitality
A dedicated team, an SLA and integration with your systems.
Priced for your deployment
Enterprise is quoted per property: the TV app with your guest services, the integration with your systems and a dedicated team, under an SLA.
The in-room TV app of the Enterprise plan carries the property's services beside the channels. Each one is scoped with you: what the guest sees, who receives it, and which system records it.
One button reaches the reception or the floor staff; the request carries the room number and lands on the desk or the staff's phones.
Ask for the room to be made up, for towels or amenities, or set "do not disturb" from the screen; housekeeping sees the queue by floor.
The guest reviews the bill on the TV and checks out from the room; the line closes and the folio goes to the front desk.
The menu of the restaurant and the minibar on screen, orders sent to the kitchen with the room number and charged to the folio.
A welcome screen with the guest's name and language, the hotel's facilities, opening hours, the local guide and the events of the day.
The running folio, messages from the reception and wake-up calls, all in the guest's language.
Rooms, buildings, the TVs or boxes in the rooms, the channels you hold rights to, and the systems the hotel runs (PMS, helpdesk).
Together we fix the list of guest services, the branding of the app and where each request goes — that is the Enterprise quote.
Our team delivers the branded TV app, the panel on your servers or ours, and the integration with the hotel's systems.
Pilot on one floor, then every room; a dedicated team and an SLA cover the operation afterwards.
Education keys and hotel deployments are handled by people, not by a form: one e-mail with the basics is enough to start.
Questions before you start, or help getting your first server online — reach us on the channel you prefer.
