1. Home
  2. Platform & Integrations
  3. Open Source - Chobble Tickets

Fully open source

Every line of code is public and every feature is included, licensed under AGPLv3 with no proprietary extensions.

No open-core tricks

Some "open source" ticketing platforms only open-source the basics, then charge for the features you actually need. Chobble Tickets doesn't do that - the hosted version and the self-hosted version are exactly the same code.

The entire codebase is on GitHub under the AGPLv3 licence. You can read it, fork it, modify it, and run it yourself.

Built by a community interest company

Chobble is a community interest company (CIC), not a VC-funded startup. There's no pressure to extract value from users or lock people into a platform - the software exists to be useful.

Three ways to deploy

1. Managed hosting

Sign up and we handle everything - infrastructure, updates, backups, and support - for £50/year (50% off for charities, community groups, artists, and musicians). No per-ticket fees, unlimited events, unlimited tickets.

2. GitHub-controlled deployments

For extra security, fork the repository on GitHub. We manage the infrastructure, but you control exactly when code updates are deployed through GitHub Actions. No update can reach your instance without your explicit approval.

3. Fully self-hosted (free)

Deploy on any Deno-compatible environment with one-click deploy buttons for DigitalOcean, Heroku, Koyeb, and Render (plus Fly.io, Docker, and Bunny Edge Scripting). You own and control everything. Follow the README to get started, or browse the technical documentation for implementation details.

Unlike other self-hosted ticketing platforms that require you to set up and maintain a traditional server, Chobble Tickets compiles to a single JavaScript file that runs on Bunny.net edge scripts with a Bunny.net edge database. There's no server to manage, no scaling to worry about, and no database replication to configure — it's all handled by the Bunny platform. This makes self-hosting Chobble Tickets closer to deploying a static site than running a web application.

References