Deploy Openfront Barbershop
Opensource Booksy alternative based on Next.js and Keystone.js
openfront-barbershop
Just deployed
Just deployed
/var/lib/postgresql/data
Storage
Bucket
Just deployed
Deploy and Host Openfront Barbershop with Railway
Openfront Barbershop is a self-hostable appointment, walk-in, and shop-management application. Customers can browse services and barbers, book visits, and join the queue. Staff manage chairs, schedules, customer records, checkout, packages, inventory, and commissions from the dashboard.
About Hosting Openfront Barbershop
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. Initialize the application using the repository's onboarding instructions after deployment.
DATABASE_URL references Postgres and the five S3_* variables reference the Storage bucket. Generated per deployment: SESSION_SECRET. Other references: SMTP_STORE_LINK. Defaults: NEXT_TELEMETRY_DISABLED=1, NODE_ENV=production, RAILPACK_NODE_VERSION=22.
Optional and blank until you configure the provider: SMTP_FROM, SMTP_HOST, SMTP_PORT.
The app gets a Railway-generated public domain. No custom domains are included.
Admin Dashboard
Manage customers, booking, store settings, pos, barbershop, queue, staff, services, reports through dedicated dashboard workspaces and permission-controlled data screens.
Storefront
Public pages include /services, /barbers, /book, /queue, /appointment, and /account. Online booking and queue entry connect to shop-scoped operator workflows.
Appointments & Walk-Ins
Check barber availability, create bookings, manage appointment changes, and seat walk-in queue entries. Staff can track service progress, waivers, waitlists, and no-shows.
Shop Checkout
Record services and retail sales, cash refunds, package use, tips, commissions, and reconciliation. The registered payment adapter is manual, for payment in person; it does not process online card payments.
Staff & Inventory
Maintain barber schedules, exceptions, shifts, chairs, practitioner credentials, products, suppliers, and inventory lots. Shop memberships determine the active operating context.
Common Use Cases
- Appointments & Walk-Ins
- Shop Checkout
- Staff & Inventory
Dependencies for Openfront Barbershop 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. Payments, email, and other external providers need their own operator configuration; this template does not activate them.
Why Deploy Openfront Barbershop 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 Barbershop 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
openfront-barbershop
openshiporg/openfront-barbershopStorage
Bucket