Deploy and Host Openfront Concerts with Railway

Openfront Concerts is a self-hostable ticketing, artist-deal and settlement application for an independent promoter that runs its own venues and promotes at partner venues. Fans browse upcoming events, hold general admission or reserved seats, and pay online. Promoter staff book artists, price events, run the box office and door, and settle each show.

About Hosting Openfront Concerts

This template provisions the application from its GitHub repository, PostgreSQL, and a private native Railway Bucket named Storage. The database starts empty; no demo records or reusable credentials are included. After deployment, open /dashboard/init to create the first admin, then run setup from the sidebar card.

DATABASE_URL references Postgres and the five S3_* variables reference the Storage bucket. Generated per deployment: SESSION_SECRET. NEXT_PUBLIC_APP_URL and SMTP_STORE_LINK use the service's public domain.

The app gets a Railway-generated public domain. No custom domains are included.

Admin Dashboard

Events (overview, billing, pricing, seating map, orders, expenses, settlement), Calendar and holds, Deals with a calculator preview, Box office, Door scan, Settlements, Venues and seating charts, Artists and tours, Orders, Promo codes, Customers, Payment providers and Settings.

Storefront

Upcoming events, an event page with general admission quantity or a seat grid, a hold with timer, card payment, confirmation with order and ticket codes, order lookup by email and order number, and ticket transfer.

Holds, Offers & Deals

Ranked date holds with challenge and confirm, offers (flat guarantee, versus, plus, door deal) whose accepted terms are frozen, artist deposits and event expenses.

Pricing, Seating & Tickets

Price levels with phases, published seating charts, production holds, 10-minute customer holds under a per-event lock, presale and promo codes, and ticket transfer that voids the old token.

Settlement

Merch and bar sales, a computed settlement worksheet with adjustments and sign-off, and artist payments. Refunds above a threshold need approval from a second user.

Common Use Cases

Selling general admission and reserved-seat tickets
Booking artists and tracking deals and holds
Settling shows with artists after the night

Dependencies for Openfront Concerts Hosting

The app needs a PostgreSQL database and S3-compatible object storage. Both are provisioned by this template.

Deployment Dependencies

Implementation Details

Next.js and Keystone 6 with a GraphQL API, Prisma, and PostgreSQL. Stripe and SMTP variables are optional and blank; add your own keys and a Stripe webhook pointing at /api/integrations/payment/pp_stripe_stripe/webhook to take card payments.

Why Deploy Openfront Concerts on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Openfront Concerts on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.