Hotline0937 763 762 VIEN Book a consultation
Home · Packages

Four ways to deploy the KHC platform

The four tiers are separated by event scale, peak concurrency and the level of operational commitment, not by a feature count. The same core platform underneath; what changes is the operations layer, the defence layer and the service level attached.

Compare the four

Side by side

BASIC

Single event

One event, fast deployment

For a single event running over one or a few days, with a simple seating layout and moderate traffic. The whole event lifecycle, from on-sale through gate check-in to reporting, runs on one system, so the post-event numbers reconcile without manual cross-checking between channels.
Applies to
A one-day or few-day event with moderate traffic
Core components
Ticketing webapp, dynamic QR tickets, gate check-in with offline readiness, sales reporting
Operations
KHC hands over the process; the organiser runs the event day
Optional add-ons
On-site point of sale, ticket delivery by SMS and email, on-site technician
Fee mechanism
A fixed fee per event, a share of ticket revenue, or a combination of the two
Best forAn organiser running a single show or a short tournament without standing up a system of their own.
PRO

Season and event series

Multiple on-sales, repeatable operations, data exploitation

For sports clubs and organisers with many fixtures or many on-sale waves in a cycle. The difference is not a feature count but accumulation: purchase behaviour, attendance frequency and engagement build up across waves and become the basis for audience segmentation and demand forecasting for the next on-sale.
Applies to
A season, an event series, multiple on-sale waves in one cycle
Core components
Everything in the Single event tier
Operations layer
Per-fixture and per-wave management, advanced vouchers and bundles, multi-level permissions, operations audit log, real-time reporting
Data layer
Accumulated audience profiles, behavioural segmentation, a basis for forecasting demand on the next on-sale
Optional add-ons
Membership programme, merchandise and food-and-beverage commerce, scheduled data export over an API
Fee mechanism
A platform fee per month or per season, a per-fixture operations fee where applicable, or a combination with a revenue share
Best forFootball, basketball and volleyball clubs and series organisers who want their audience turned into usable data.
ENTERPRISE

Large scale with an operational commitment

High concurrency, hardened defence, a committed service level

For events with high peak concurrency at on-sale and at gate opening: large concerts, major tournaments, events exposed to ticket scalping. The defence layer covers rate limiting, blocklists and behavioural risk scoring to identify organised scalping, together with load rehearsal before the on-sale and a written service-level commitment.
Applies to
High peak concurrency at on-sale and gate opening, with a committed service level
Core components
Everything in the Season and event series tier
Defence layer
Rate limiting, blocklists, behavioural risk scoring to identify organised scalping
Pre-event preparation
Load testing, on-sale and gate-opening rehearsals, incident playbooks agreed in advance
Service level
A written commitment on availability, response time and restore time across four severity levels, with incident reporting
Optional add-ons
Interactive seat selection, on-site support team and a dedicated hotline, integration with the organisation's identity and management systems
Best forEvents where a failure in the first fifteen minutes of an on-sale cannot be recovered.
CUSTOM

Purpose-built model

A revenue model of its own, built after a survey

For cases the three tiers above do not describe: an organisation that owns a large community but does not run events, manufacturers and distributors seeking access to an existing community, a federation needing one shared model across member organisations. KHC surveys the current state, builds a revenue model for that case, and only then defines scope and cost structure.
Applies to
Cases that do not fit the three tiers, or a model shared across several organisations
Method
Survey the current state, build a revenue model, define scope, and only then discuss cost
Scope may include
A fanzone for a creator audience, a sales channel from manufacturers and distributors into a community, a shared system for a federation, integration with existing systems
Data ownership
Community data belongs to the community owner, agreed in writing before deployment
Fee mechanism
Determined after the survey; there is no published price frame
Best forCreators with large followings, manufacturers, distributors and federations that need a model built for them.

KHC does not publish prices for the four tiers. Audience size, number of events in a cycle, peak concurrency and current ticketing practice differ from one organisation to the next, so KHC runs a survey first and only then sets a figure for that organisation. Leave your details and KHC will book the survey and send a quote with a scope document.

Which package

Five questions that settle it

One event or a whole cycle

A single event stops at the first tier. Many fixtures or many on-sale waves in one cycle need the operations and data layers of the second.

What is peak concurrency

This number decides whether the defence layer and load testing are needed, and it is the real boundary between the second and third tiers.

Is there a seat map, and is seat selection required

An interactive map brings temporary holds and conflict resolution with it; it is not an interface option.

Are membership, merchandise and food and beverage required

This is what turns an audience into repeat revenue, and it only means something once data accumulates across waves.

Who carries the event day

If a failure during gate opening cannot be recovered, the service level has to be committed in writing, not agreed verbally.

Ask for a quote and a scope document

Leave your details and the KHC business development team will get back to you in working hours.

Hotline 0937 763 762