Deploy Openfront Dealership
Opensource DealerSocket alternative based on Next.js and Keystone.js
Just deployed
/var/lib/postgresql/data
openfront-dealership
Just deployed
Storage
Bucket
Just deployed
Deploy and Host Openfront Dealership with Railway
Openfront Dealership is a self-hostable digital showroom and dealership-operations application. Shoppers can explore vehicles, compare options, and submit sales, test-drive, trade-in, finance, or service requests. Teams coordinate inventory, CRM, deal desk, finance records, delivery, service, parts, and accounting.
About Hosting Openfront Dealership
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: 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 accounting, store settings, crm, deals, test drives, delivery, vehicles, finance, service, overview, analytics, trade ins through dedicated dashboard workspaces and permission-controlled data screens.
Storefront
Public routes include /inventory, vehicle details, /compare, /test-drive, /trade-in, /financing, /service, and customer accounts. Financing intake is a request workflow, not a promise of lender approval.
Vehicle Inventory & CRM
Track acquisitions, stock, recon work, merchandising versions, pricing, customer identity, lead assignments, interactions, and contact preferences.
Deal Desk & Finance
Prepare deal pencils, record approvals, financing applications, lender submissions and decisions, finance products, funding cases, and contract packages.
Delivery & Fixed Operations
Coordinate delivery cases and we-owe items, service appointments and repair orders, labor operations, parts inventory, purchasing, and accounting batches. External lender and accounting responses must be configured and recorded through their workflows.
Common Use Cases
- Vehicle Inventory & CRM
- Deal Desk & Finance
- Delivery & Fixed Operations
Dependencies for Openfront Dealership 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 Dealership 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 Dealership 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-dealership
openshiporg/openfront-dealershipStorage
Bucket