Why a venue should own its ticket office
Commission, customer data and the day a platform changes its terms — the three reasons venues move to software they own.
Every venue eventually does the same arithmetic: how much of each ticket goes to the platform that sold it, and what happens to the customer relationship after the money is split.
Commission compounds
A ticketing platform typically takes a percentage of the face value, sometimes from the buyer, sometimes from the venue, often from both. On a 2 000 ₽ ticket, five percent is 100 ₽. Multiply by a season and the number stops being abstract.
Software you install once has no per-ticket line in the ledger. The server costs the same whether you sell a hundred tickets or ten thousand.
The customer list is the asset
When a platform sells your tickets, it learns who your audience is, what they buy and when they return. You get a settlement report.
When your own site sells them, the database with those buyers is on your server. That is what makes a mailing list, a season pass and a returning-audience strategy possible without asking permission.
Terms change without your vote
Platforms change fees, payout schedules and moderation rules. Sometimes reasonably, sometimes not. The venue that rents its checkout discovers the change in a newsletter.
Owning the code means the checkout behaves the same next season, whatever happens to a vendor. It also means someone on your side can read it — which is why the source ships unobfuscated.
What owning it does not mean
It does not mean building it. The reason venues hesitate is the assumption that "own" equals "develop": a year of work, a team, a roadmap.
The realistic middle ground is a finished product with a one-time license: the code is yours, the features already exist, and installation takes an afternoon. That is the model this product is sold under — and the reason the demo is online and public rather than a sales call.
The hidden cost of the middle ground
Honesty demands the other side: owning software means owning operations. Backups, updates, a server, someone who knows what to do when the site is down at 19:40 on a sold-out evening.
That work is real. It is also finite and documentable, unlike a commission that scales with your success. A venue with a 2 GB VPS and a weekly backup habit is in a better position than one waiting for a platform's support queue on a show night.