A page describing an event with a Stripe Checkout button and a generated ticket is genuinely simple — one of the more approachable builds in this library.
Build it
Effort: an eveningRunning cost: $0/mo to start
Why CanICodeThis says Build it
An event page with date, location, and description is standard content rendering
Stripe Checkout for ticket purchase, generating a unique ticket code on success, is a well-documented pattern
A simple check-in page scanning or entering the ticket code is straightforward
The parts that'll cause problems
Multiple ticket tiers with different prices and limited quantities need real inventory-style tracking to avoid overselling
QR-code scanning for fast check-in at the door needs a camera-based scanning library
Refunds and transfers between attendees add real, separate workflow
How I'd build this
frontend
Astro or Next.js
database
Turso (SQLite)
payments
Stripe Checkout
hosting
Cloudflare Pages
MVP scope
An event page with details
Stripe Checkout for ticket purchase
A unique ticket code generated per purchase
A simple check-in page to mark a code used
Postpone to v2
Multiple ticket tiers with quantity limits
QR-code scanning for check-in
Refunds and ticket transfers
What it actually costs to build
AI agent — with a subscription (Claude Pro/Max, Cursor, etc.)
$0 marginal
AI agent — pay-per-use API, no subscription
$16–$27 one-time
Hosting, once it's running
$0/mo (free tier)
Domain name, if you want your own
~$12/yr
The build prompt
Build me an event ticket sales page: event details, Stripe Checkout for purchase, a unique ticket code generated and emailed on success, and a simple admin page to mark a code as checked in. Skip multiple tiers and QR scanning for v1 — one ticket type and manual code entry covers a real small-event need.