Event ticketing without per-ticket fees. Open source. Encrypted.
Sign up here See a live demo View on GitHubMost ticketing platforms take a cut of every sale by inserting themselves in the transaction. Chobble Tickets is a flat £50/year, and I'm not involved in your sales at all. Payments go through your own Stripe or Square account, so the money goes straight to you. This could save you thousands of pounds every year if you run a lot of events.
The entire platform is open source under the AGPL licence. You can read every line of code, self-host it for free, or pay for managed hosting and let me handle the infrastructure. If you want to customise it, I'll do that at my normal rates, or you can employ some other nerd, because it's open source.
Every ticket gets a unique QR code. Your staff just scan it with their phone using the built-in scanner. It's really easy. Check-in only, with no accidental check-outs from double-scans.
Two people can't grab the last ticket at the same time. Places are reserved for 5 minutes while someone pays, then released if they abandon.
Paste in your Stripe key and the webhook configures itself. Square's also supported. Free events don't need any payment setup at all.
All personal info is encrypted at rest. Even if the database were compromised, attendee data stays protected. The system encrypts data at every level.
Standard events for one-off occasions. Daily events let attendees pick a date from a calendar, with per-date capacity and holiday blackout dates.
Combine events into one URL so attendees fill in their details once, pay once, and get all their tickets together. There's a link builder so you don't have to construct the URLs by hand.
Bundle related events under a single page. Share one link and attendees see everything that's available.
Download attendee lists as CSV whenever you like. Set up webhooks to fire on every registration, handy for email notifications, Slack, or spreadsheets.
Got a team? Invite managers to the admin panel. Owners get full control, managers can see events and the calendar. Activity logs track everything.
Refund individual attendees, bulk refund an entire event, or let the system handle it automatically if the event fills up while someone's paying.
Already got a website? Embed the booking form with the provided embed script or iframe code. No website? Use the built-in public site instead.
Don't need a separate website? Enable the public site for a homepage, events listing, and contact page on your domain. Light and dark themes included.
Format your event descriptions with Markdown, including headings, bold, links, and lists. It just renders nicely, no HTML needed.
Upload a header image in settings to brand your site, and add images to individual event booking pages.
There's loads more too: configurable contact fields, registration deadlines, max tickets per purchase, event date and location fields, duplicate events in one click, manually adding attendees for walk-ins and comps, terms & conditions, custom thank-you redirects, a calendar view across all events, per-event activity logs, session management, failed payment tracking, and a built-in admin guide.
For the full feature list and pricing details, see the Chobble Tickets service page.
The simplest option. Sign up and I'll set up your own Chobble Tickets instance, handle all the infrastructure, and keep it running and maintained. You just create events and sell tickets.
I'll be in touch within a couple of days to get you going. Mention if you're a community group, charity, artist or musician for the 50% discount.
This is more work than the fully-managed option, but it provides an extra layer of protection: even if someone compromised my accounts, they couldn't push a tainted update to your system to access your data. You review and deploy every change yourself.
Sign up here and mention you'd like to handle your own deployments.
Click the button below to generate a secure encryption key. This key encrypts all personal data in your database.
1 Go to github.com/chobbledotcom/tickets/fork
2 Click "Create fork"
(You'll need a GitHub account, and it's free to create one)
In your forked repository, add the deployment secrets so GitHub Actions can deploy to Bunny:
1 Go to Settings (tab at the top)
2 Click Secrets and variables in the left sidebar
3 Click Actions
4 For each secret below, click "New repository secret"
DB_URL,
DB_TOKEN, DB_ENCRYPTION_KEY, and
ALLOWED_DOMAIN) are configured as Bunny native secrets
in the Bunny dashboard, and Chobble will have set these up for you
already. Only BUNNY_SCRIPT_ID,
BUNNY_ACCESS_KEY, and DB_ENCRYPTION_KEY
need to go in GitHub.
1 Go to the Actions tab
2 Click "I understand my workflows, go ahead and enable them"
3 Click Deploy in the left sidebar
4 Click "Run workflow" button on the right
5 Click the green "Run workflow" button
1 Visit your domain and go to /setup/
2 Choose an admin username and password (minimum 8 characters)
3 Choose your currency (defaults to GBP)
4 Accept the data controller agreement, which confirms you're responsible for your attendees' data
5 Go to Settings to configure Stripe or Square
6 Create your first event and share the booking link
/admin/guide with answers to common questions about events,
payments, check-in, and more.
Chobble Tickets is fully open source and you can self-host it for free. The whole platform runs on Bunny.net using their edge scripting and Turso (libsql) for the database.
Follow the setup instructions in the README on GitHub to get your instance running.
You'll need a database encryption key. This encrypts all personal data
in your database, including names, emails, phone numbers, addresses, and
more. Click below to generate one, then add it to your environment
variables as DB_ENCRYPTION_KEY.
/setup/ to
set your admin credentials and currency. Payment providers are
configured at /admin/settings.