Openfront Salon is a self-hostable booking and salon-operations application. Clients can explore services and stylists, book appointments, and manage their visits. Salon teams use the dashboard for scheduling, client history, checkout, retail inventory, memberships, packages, and commissions.
Documentation: docs.openship.org/docs/openfront/salon
| Storefront | salon.openship.org |
| Dashboard | salon.openship.org/dashboard |
Every Openfront is open source and self-hostable. Try any of them on its live demo.
| Product | For | Repository | Demo | Docs |
|---|---|---|---|---|
| Openfront E-commerce | Online store: catalog, checkout, orders, fulfillment | openfront | e-commerce.openship.org | Docs |
| Openfront Restaurant | Online ordering, POS and kitchen display | openfront-restaurant | restaurant.openship.org | Docs |
| Openfront Grocery | Grocery ordering, lots, expiry and pickup | openfront-grocery | grocery.openship.org | Docs |
| Openfront Gym | Memberships, classes, check-in and billing | openfront-gym | gym.openship.org | Docs |
| Openfront Hotel | Reservations, front desk, housekeeping, folios | openfront-hotel | hotel.openship.org | Docs |
| Openfront Rental | Short-term rental bookings and calendars | openfront-rental | rental.openship.org | Docs |
| Openfront Salon (this repository) | Appointments, stylists and services | openfront-salon | salon.openship.org | Docs |
| Openfront Barbershop | Bookings, walk-ins and barbers | openfront-barbershop | barbershop.openship.org | Docs |
| Openfront Coffee Shop | Café ordering and counter POS | openfront-coffeeshop | coffee-shop.openship.org | Docs |
| Openfront Real Estate | Listings, showings and transactions | openfront-realestate | real-estate.openship.org | Docs |
| Openfront Dealership | Inventory, test drives, deals and service | openfront-dealership | dealership.openship.org | Docs |
| Openfront Vape | Age-gated retail with compliance controls | openfront-vape | vape.openship.org | Docs |
| Openfront Convenience | Convenience store POS and inventory | openfront-convenience | convenience.openship.org | Docs |
| Openfront Collectibles | Graded items, consignment and provenance | openfront-collectibles | collectibles.openship.org | Docs |
| Openfront Cannabis | Dispensary menu, packages and recalls | openfront-cannabis | cannabis.openship.org | Docs |
| Openfront Pharmacy | Prescriptions, inventory lots and pickup | openfront-pharmacy | pharmacy.openship.org | Docs |
| Openfront Med Spa | Treatments, consents and memberships | openfront-medspa | medspa.openship.org | Docs |
| Openfront Construction | Projects, bids, change orders and crews | openfront-construction | construction.openship.org | Docs |
| Openfront Law Firm | Matters, intake, time and billing | openfront-law-firm | law-firm.openship.org | Docs |
| Openfront Scheduling | Booking pages for appointment businesses | openfront-scheduling | scheduling.openship.org | Docs |
| Openfront Social | Creator community and posts | openfront-social | social.openship.org | Docs |
| Openfront Rideshare | Rides, drivers and dispatch | openfront-rideshare | rideshare.openship.org | Docs |
| Openfront Airline | Flights, booking and passenger operations | openfront-airline | airline.openship.org | Docs |
| Openfront Hospital | Appointments, patients and care teams | openfront-hospital | hospital.openship.org | Docs |
| Openfront Sportsbook | Markets, bets and results | openfront-sportsbook | sportsbook.openship.org | Docs |
| Openfront Financial | Accounts, portfolios and advisory | openfront-financial | financial.openship.org | Docs |
| Openfront Analytics | Privacy-friendly website analytics | analytics | analytics.openship.org | Docs |
| Openship | Order routing from sales channels to fulfillment | openship | os.openship.org | Docs |
| Marketplace | Shop across Openfront stores | marketplace | marketplace.openship.org | Docs |
Manage commissions, clients, appointments, catalog, resources, store settings, schedules, checkout, engagement, integrations, inventory, benefits through dedicated dashboard workspaces and permission-controlled data screens.
Clients can browse /services and /stylists, book at /book, and view appointments and accounts. Gift-card, gallery, team, and review pages round out the public site.
Coordinate stylist schedules, resources, appointment segments, deposits, and waitlists. Appointment transitions and schedule revisions are handled by dedicated workflow commands.
Complete appointment checkout, record retail sales, redeem packages, and manage memberships, points, referrals, and gift cards. Reversal, gratuity, and commission records preserve financial history.
Maintain client notes, color formulas, and consultation submissions. Consultation review uses a separate care-record permission rather than assuming every salon manager can read it.
- Frontend: Next.js 16 with App Router and React 19.
- Backend: KeystoneJS 6 with a GraphQL API.
- Database: PostgreSQL with Prisma ORM.
- Styling: Tailwind CSS 4 and shared shadcn/ui components.
- Authentication: Password-based user accounts and session-based access with role capabilities.
openfront-salon/
├── app/ # Public pages, dashboard routes, and HTTP endpoints
├── features/
│ ├── keystone/ # Backend models, access rules, and GraphQL workflows
│ ├── platform/ # Operator workspaces and onboarding
│ ├── storefront/ # Public application components and screens
│ └── dashboard/ # Authentication and shared dashboard shell
└── components/ # Shared UI components
The model registry and Prisma schema cover:
- Services, variants, stylists, schedules, resources, and appointment segments.
- Clients, notes, color formulas, consultation templates, submissions, and reviews.
- Appointment lines, deposits, payment sessions, checkout transactions, and reversals.
- Products, inventory movements, packages, memberships, loyalty, gift cards, and commissions.
- Node.js 22, compatible with the package requirements and Next.js 16.
- A PostgreSQL database you can migrate.
- npm.
-
Clone and install dependencies:
git clone https://github.com/openshiporg/openfront-salon.git cd openfront-salon npm install -
Configure environment variables:
cp .env.example .env
Review the example configuration and replace its placeholders. Keep only the local settings you need; do not copy production-mode or infrastructure examples unchanged.
DATABASE_URL=postgresql://user:password@host/database SESSION_SECRET=replace-with-a-new-private-random-secret
Generate the session secret with
openssl rand -hex 32; use the generated value, not the placeholder. Never commit.env.Review runtime configuration for additional application settings before building or deploying. Configure enabled integrations separately; the two values above are not a complete production configuration.
-
Start development server:
npm run dev
The development script prepares the backend schema, applies checked-in migrations, and starts Next.js.
-
Access the application: Open the URL
npm run devprints, then use these paths:- Public application:
/ - Admin dashboard:
/dashboard - GraphQL API:
/api/graphql
- Public application:
-
Create your first admin user: Visit
/dashboard/initon an empty database to create the initial administrator, then sign in to the dashboard. -
Run application onboarding: Use dashboard onboarding to configure the salon, services, stylists, schedules, resources, and storefront settings. Review payment-provider settings separately.
npm run dev- Prepare the backend schema, apply migrations, and start Next.js development.npm run build- Build the backend and Next.js for production; does not apply migrations.npm start- Start the production Next.js server.npm run migrate:gen- Prepare the schema and generate/apply development migrations.npm run migrate- Apply checked-in Prisma migrations.npm run lint- Run the repository's ESLint script.
Use a disposable development database for migration generation. Review the script before running it against any existing data.
Manual and Stripe adapters are registered in the payment loader. Configure provider records before taking payments; manual records do not represent a processor capture.
See the Openfront Salon documentation for the application guide. The backend models, registered business workflows, access rules, and application routes document the implementation in this repository.
canAccessDashboard- Access dashboard.canManageAppointments- Manage appointments.canManageCatalog- Manage catalog.canManageClients- Manage clients.canManageCareRecords- Manage care records.canManagePayments- Manage payments.canIssueRefunds- Issue refunds.
- Session-based authentication for signed-in users.
- Backend list access and workflow authorization, rather than dashboard visibility alone.
- Client and appointment read rules distinguish staff capabilities from records owned by the signed-in client. Care-record access and onboarding require explicit permissions.
Review the access implementation and individual workflow checks before extending permissions.
- Commissions:
/dashboard/platform/commissions. - Clients:
/dashboard/platform/clients. - Appointments:
/dashboard/platform/appointments. - Catalog:
/dashboard/platform/catalog. - Resources:
/dashboard/platform/resources. - Store Settings:
/dashboard/platform/store-settings. - Schedules:
/dashboard/platform/schedules. - Checkout:
/dashboard/platform/checkout. - Engagement:
/dashboard/platform/engagement. - Integrations:
/dashboard/platform/integrations. - Inventory:
/dashboard/platform/inventory. - Benefits:
/dashboard/platform/benefits.
Clients can browse /services and /stylists, book at /book, and view appointments and accounts. Gift-card, gallery, team, and review pages round out the public site.
Coordinate stylist schedules, resources, appointment segments, deposits, and waitlists. Appointment transitions and schedule revisions are handled by dedicated workflow commands.
The Vercel button imports this application's own repository. Provision PostgreSQL and configure the application's complete runtime requirements, storage, mail, and enabled providers before building. Importing the source does not configure these services.
Build the application and apply checked-in migrations as a release step before starting the server. Back up existing data before migration.
npm run build
npm run migrate
npm startThe included Railway configuration defines this app's build and startup lifecycle. Provision services and secrets separately.
Keep the shared PostgreSQL database, session secrets, and configured object storage consistent across application processes. Review background delivery and integration requirements before choosing a serverless runtime; a source import does not supply persistent workers.
Use the development commands above when preparing changes. Keep model changes and their migrations together, and describe workflow and permission changes in pull requests.
No top-level license file or package license declaration is included in this repository.
- Documentation: Openfront Salon guide.
- Issues: Report bugs and feature requests.
- Product: Learn more about Openfront Salon.
Built with Next.js and KeystoneJS.