# Venuo

> Public event pages, tiered tickets and QR check-in at the door — an Eventbrite alternative you run yourself, taking no percentage of ticket sales.

Source page: https://saascode.ai/products/venuo
Machine-readable record: https://saascode.ai/products/venuo.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $229 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Venuo is self-serve event ticketing for organizers who run events regularly: create an event with a public page, sell tickets by type, and check attendees in at the door by scanning a QR code in a browser.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/venuo — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://venuo.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Door staff** (`member`) — `user@demo.com` / `demo123`
  Check-in only: scans tickets at the door.
- **Event organizer** (`org_admin`) — `org-admin@demo.com` / `demo123`
  Runs events: ticket types, discounts, attendees.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every organisation and cross-org sales.

Or open a role directly: https://saascode.ai/demo/venuo?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, member, org_admin, super_admin
- **tables: 63** — distinct CREATE TABLE statements across every applied migration
- **migrations: 103** — .sql files in supabase/migrations
- **page modules: 77** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 139,588** — lines of code (comments and blank lines excluded) across 1014 TypeScript files (127,879) and 108 SQL files (11,709); node_modules and .next excluded
- **api route files: 216** — files named route.ts under src/app/api
- **http operations: 285** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 63 tables, 108 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-07-29

## Complete capability inventory

11 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Door check-in & reporting

- **Door check-in (scan, counts)** — Check-in runs in a browser on a phone. There is no app to install and no scanner hardware to hire — door staff open a link and point the camera at the ticket.
- **Attendee management (resend/void/refund)** — The attendee list enumerates tickets rather than orders, so it shows people rather than purchases. Organizers can resend a ticket, void one, or refund from the same place.
- **Sales reports** — Sales by event and by ticket type, covering what sold, when, and for how much.
- **Live check-in dashboard** — On the mid tier and above, the organizer watches arrivals in real time: how many are in, how many are still expected, broken down by ticket type.
- **Offline door mode** — The attendee manifest is held on the device, scans queue locally, and the queue syncs when connectivity returns. Records created offline are marked as such.

### Events, tickets & checkout

- **Events with public page** — An organizer creates an event and gets a public page for it — the thing that goes in an email, a story or a poster's QR code. Recurring and multi-date events are available on the top tier as event occurrences under one event.
- **Single ticket type + sale window** *(seller-authored)* — One ticket type with its own price, quota and sale window — enough to run a straightforward event on every tier, and the thing early-bird pricing is built from once more types are available.
- **Anonymous checkout + QR email** — A buyer purchases without creating an account. Name, email, pay, done.
- **Multiple ticket types** — A ticket type carries its own price, its quota and its sale window, so early-bird pricing and a capped VIP tier are configuration rather than separate events.
- **Discount codes** *(seller-authored)* — Codes that reduce the price at checkout, which is how an organizer runs a promoter allocation, a member rate or an early push without creating a separate ticket type and reconciling the two afterwards.
- **Recurring & multi-date events** *(seller-authored)* — One event that runs on several dates, or repeats on a schedule, without being recreated each time. A weekly night modelled as fifty separate events is fifty places for the details to drift apart.

## What each system gives the operator

*stated.*

- **Door check-in & reporting** — The door keeps moving even when the venue has no signal.
- **Events, tickets & checkout** — A buyer goes from a link to a ticket without creating an account.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Scanning keeps working in a basement venue with no bars.

Door software fails in exactly the place it is used: a room full of people, on a network that was fine at setup and is saturated by the time the queue forms. When scanning stops, the fallback is a printed list and a pen, the queue stops moving, and the people outside form an opinion about the event before they are inside it. Organizers who have lived through it once buy hardware and staff to avoid a second time, which is money spent on a problem that should not exist.

### Someone buying four tickets brings four people who each get in on their own.

Money and admission are different things, and ticketing that conflates them breaks at the door. A group buys together and arrives separately; the person who paid is running late; one of the four cannot come and the ticket should go to somebody else. With one code per order, all of that becomes a conversation with door staff while a queue builds behind it — and the organizer finds out afterwards, from the complaints, that half the friction of the night was at the entrance.

### Sales settle with the organizer directly, and you take none of it.

Ticketing platforms that hold funds inherit the hardest parts of the business: payouts, refunds after a cancelled show, disputes between an organizer and their own attendees, and in some jurisdictions a licensing question about holding other people's money at all. It is the reason the incumbents charge what they charge, and it is the part a small operator cannot staff. Taking custody looks like the business model right up to the first cancelled event.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security, applied by the shipped migration scripts.
- **A payment provider for the subscription** (required) — The organizer's own Venuo subscription.
- **A payment account per organizer** (required to sell) — Each organizer connects their own account, stored encrypted per organization. Ticket money goes to them directly; the platform never holds it.
- **Email provider** (required) — Ticket delivery. Without it a purchase completes and no QR code arrives, so this one is not optional in practice.
- **HTTPS and a camera-capable device** (at the door) — Browser camera access requires a secure origin. Any modern phone works; no dedicated scanner is needed.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 139,588 lines across the application and its database, 63 tables defined by 103 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Venuo demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 3 of them: Door staff, Event organizer, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 77 page modules and 285 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, A payment provider for the subscription, A payment account per organizer, Email provider, HTTPS and a camera-capable device. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 103 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $229?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Event Ticketing Software Compared: Who Actually Bears the Platform's Cut?](https://saascode.ai/inside/event-ticketing-software-compared-who-actually-bears-the.md)
- [Venuo vs Ticket Tailor, Eventbrite, and the Other Ways to Own a Ticketing Platform](https://saascode.ai/inside/venuo-vs-ticket-tailor-eventbrite-and-the-other-ways-to-own.md)
- [Venuo: event ticketing you run yourself, from public pages to QR check-in](https://saascode.ai/inside/road-to-venuo.md)

## Links

- Catalog page: https://saascode.ai/products/venuo
- Product record: https://saascode.ai/inside/products/venuo
- Live demo: https://venuo.saascode.ai
- Every product: https://saascode.ai/llms.txt