Deploy Hi.Events
Open-source event ticketing and management, an Eventbrite alternative
Redis
Just deployed
/data
Hi-Events
Just deployed
/app/backend/storage
Just deployed
/var/lib/postgresql/data
Deploy and Host Hi.Events on Railway
Hi.Events is an open-source event management and ticket selling platform, a self-hosted alternative to Eventbrite. Organizers create events with free, paid or donation tickets, recurring dates, promo codes, custom checkout questions and branded event pages, then check attendees in with QR codes. It is built with Laravel and React and licensed AGPL-3.0.
About Hosting Hi.Events
This template deploys Hi.Events v2.2.0 from the official all-in-one image (nginx, PHP-FPM, the server-rendered frontend, the queue worker and the scheduler in one service), pinned by digest and built from a public GitHub repo. It adds Railway Postgres and a password-protected Redis for the queue and cache. Uploaded images live on a volume, so they survive redeploys. The encryption key, the login-token secret and the frontend-to-API secret are generated for each deploy, every URL follows the service's Railway domain, and migrations run on each start. There is nothing to fill in. The first boot takes about a minute.
Common Use Cases
- Selling tickets for concerts, festivals, conferences and workshops without per-ticket platform fees
- Free registration with attendee lists, custom questions and QR code check-in for meetups and community events
- Recurring classes or tours with per-date capacity, plus an embeddable ticket widget for your own website
Dependencies for Hi.Events Hosting
- Postgres (Railway Postgres, included)
- Redis (Railway Redis, included)
Deployment Dependencies
- Hi.Events source and releases: https://github.com/HiEventsDev/Hi.Events/releases/tag/v2.2.0
- Official image: https://hub.docker.com/r/daveearley/hi.events-all-in-one
- Configuration reference: https://hi.events/docs/getting-started/deploying
- Template repo: https://github.com/aalfath/hi-events-railway-template
Implementation Details
After deploy, open the service URL and go to /auth/register. The first account you create owns the organizer account. Registration stays open for anyone until you set APP_DISABLE_REGISTRATION=true on the Hi-Events service, so do that once your team has signed up.
Optional settings go on the Hi-Events service as variables:
- Email (order confirmations, tickets, password resets):
MAIL_MAILER=smtp,MAIL_HOST,MAIL_PORT,MAIL_USERNAME,MAIL_PASSWORD,MAIL_ENCRYPTION,MAIL_FROM_ADDRESS. Until you set them, emails are only written to the log. - Paid tickets with Stripe:
STRIPE_PUBLIC_KEY,STRIPE_SECRET_KEY,STRIPE_WEBHOOK_SECRETandVITE_STRIPE_PUBLISHABLE_KEY, with the webhook athttps://YOUR-DOMAIN/api/public/webhooks/stripe. - Custom domain: add it in Railway, then set
APP_PUBLIC_URL=https://YOUR-DOMAINand redeploy.
Updates: the Hi-Events service builds from the template repo. When a new Hi.Events version is pinned there, Railway shows you an update notice and you choose when to apply it. Read the repo's CHANGELOG first and back up Postgres before a major version.
Why Deploy Hi.Events 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 Hi.Events 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.
Template Content
Redis
redis:8.2Hi-Events
aalfath/hi-events-railway-template