Self-Hosted Event Ticketing System

A ticketing SaaS takes a cut of every ticket sold and keeps the guest list on someone else's servers — a venue with merch and repeat dates wants to sell seats on its own VPS and its own license, with no turnover commission and no exporting the customer database through a support ticket. The Tickets format in NitroCart switches from the same admin panel as the catalog and the landing — one engine, one domain, one order database. Full product details are on the NitroCart homepage.

What this is and who needs it

Tickets is one of NitroCart's four storefront formats (alongside Catalog, Landing one, Landing multi): instead of product cards, the storefront shows events with a seat picker by sector, sub-sector and row, a session date, and a printable ticket with a QR or barcode issued right after payment. Switching between formats is one field in Site settings → Render setting, with no reinstall and no second VPS. This fits small venues and clubs with seated shows, conference organizers with tiered registration and dates, tour promoters who need to sell merch on the same domain right after the show, and theaters running multi-date subscriptions.

Criteria for choosing a ticketing system for a venue

1. Turnover commission. Does the platform take a percentage of every ticket sold on top of payment processing, or is there no turnover cut at all.
2. Ownership of the guest list. Can the customer list and purchase history be exported at any time without opening a support ticket.
3. Seat-level selection. Can a specific seat in a specific sector and row be sold, rather than only a generic ticket type with no seating tie-in.
4. Merch on the same stack. Can related merchandise be sold on the same domain and the same order database without a second platform.
5. Printable ticket. Is a PDF with a QR or barcode generated right after payment, without a third-party printing service.
6. Sales notifications. Does the organizer get a real-time alert for every sale.
7. Your own infrastructure. Does the ticketing system run on a VPS you rent, or only as a cloud SaaS on someone else's servers.

Comparison table: ticketing options for a small venue

Option	Per-ticket commission	Guest list ownership	Merch on the same engine	Your own infrastructure
Large ticketing aggregator	Usually 5–15% per ticket	No, the aggregator owns it	No, a separate platform	No, the aggregator's cloud
Off-the-shelf event SaaS	Flat subscription, sometimes plus a %	Partial, via export	Usually not	No
Custom-built solution	None	Yes, fully	Needs separate development	Yes, but dev and upkeep are on you
NitroCart Tickets	None, processing fees only	Yes, database on your VPS	Yes, switch via Render setting	Yes, your VPS

How this works in NitroCart

The Tickets format is enabled in Site settings → Render setting — once switched, the storefront shows events instead of a product catalog. Inside an event, a buyer picks a sector, sub-sector and row through a cascading select, sees a grid of free and taken seats, and checks out through the same flow as every other format, using the same payment URL set in Checkout settings. After payment, the buyer gets a printable ticket with a QR code or barcode they can print or show from their phone at the door. The organizer gets a notification for every sale in the same Telegram group already wired up for catalog orders — no separate setup for ticketing. Session dates and per-sector prices are set in the admin panel with no developer involved, and once a run of dates ends, Render setting flips back to Catalog with one field to sell merch on the same domain and the same order database.

The concrete piece: tickets and merch on one engine without a second platform

A common scenario for a small club: selling tickets to Friday's show and tour merch through the following week doesn't need two separate platforms, two payment-processing setups, and two admin panels for two teams. One VPS switches between the Tickets format (sectors, rows, dates, printable ticket) and the Catalog format (merch SKUs — shirts, vinyl, posters) through a single Render setting field in Site settings, staying on the same IP slot of the license. After the event, the format flips to Catalog, merch SKUs and a promo block go on the homepage, and ticket buyers get retargeted on the same domain without a hostname change and without reissuing the license — Cloudflare and SSL stay exactly as they were. Orders from both formats sit in one database on the VPS, so the same buyer's history (ticket first, merch later) shows up in one place, and Telegram sales alerts land in the same group regardless of which format is active — the organizer doesn't have to check two different channels.

When NitroCart is not a fit

If the requirement is a graphical interactive floor plan with a visual seating layout where a buyer clicks directly on a picture of the room, NitroCart doesn't have that — seat selection goes through sector → sub-sector → row selects and a grid of seats drawn as squares, with no rendered floor plan. It also doesn't fit a use case that needs automatic dynamic pricing that changes algorithmically in real time based on demand — per-sector prices are set statically in the admin panel until the next manual change, with no automation. An honest breakdown of the engine's limits is in when NitroCart is not a fit.

FAQ

Can a specific seat be sold instead of a generic ticket type? Yes, inventory is tracked at the individual seat level inside a sector and row — a purchased seat is immediately marked taken for other buyers.

Does merch sell on the same domain as tickets? Yes, one VPS switches the storefront format between Tickets and Catalog — the domain, SSL and license stay the same, only Render setting changes.

Does the seat grid work on mobile? Themes are responsive to mobile screens, but it's worth checking the seat grid on a real phone before sales open — a dense grid on a small screen needs scrolling.

Is there a commission on every ticket sold on top of payment processing? No, the NitroCart license doesn't take a turnover cut — the only fee is the standard payment processor's fee.

Can the guest list be exported for door check-in? Yes, the order and customer database lives on your VPS, and export is available from the admin panel at any time with no support ticket needed.

What happens to unsold seats once sales start? A seat stays available for purchase until payment goes through — the organizer sees in the admin panel at any moment how many seats are free per sector.

NitroCart pricing — Start 1 IP, Pro up to 5, Enterprise up to 15. Next: four formats: Catalog, Landing one, Landing multi, Tickets, non-obvious NitroCart use cases: pop-up, QR, webinar, season, sell tickets online, ticket system for a website.