---
title: "Deploy Openfront Rental"
description: "Opensource Guesty alternative based on Next.js and Keystone.js"
category: "Starters"
url: https://railway.com/deploy/openfront-rental
---

# Deploy Openfront Rental

Opensource Guesty alternative based on Next.js and Keystone.js

**[Deploy Openfront Rental on Railway](https://railway.com/template/openfront-rental)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/openfront-rental/manifest.json

- **Creator:** Openship
- **Category:** Starters

## Template content

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

### openfront-rental

- **Source:** https://github.com/openshiporg/openfront-rental
- **Start command:** `npm run migrate && next start`
- **Public domain:** Yes

## Buckets

- **Storage**

## Documentation

# Deploy and Host Openfront Rental with Railway

Openfront Rental is a self-hostable platform for professional short-term accommodation managers. Guests can search stays, request quotes, reserve accommodation, sign agreements, and review private trip information. Hosts use the dashboard for properties, listings, calendars, pricing, reservations, guest messages, property tasks, payments, and owner statements.

## About Hosting Openfront Rental

This template provisions the application from [its GitHub repository](https://github.com/openshiporg/openfront-rental), 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: `NEXT_PUBLIC_APP_URL`. Defaults: `NODE_ENV=production`, `PUBLIC_SIGNUPS_ALLOWED=false`, `STRIPE_ENABLED=false`.

Optional and blank until you configure the provider: `SMTP_FROM`, `SMTP_HOST`, `SMTP_PASSWORD`, `SMTP_PORT`, `SMTP_USER`, `STRIPE_PUBLISHABLE_KEY`, `STRIPE_SECRET_KEY`, `STRIPE_WEBHOOK_SECRET`.

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

### Admin Dashboard
Manage properties, accommodation units, listings, calendar blocks, pricing, reservations, guests, and agreements. Host workspaces also cover messages, property tasks, reviews, channels, payment records, payouts, owner statements, and reports.

### Storefront
Guests can search published stays, view listing details, browse collections, compare properties, and request a quote for dates and guest counts. Quote checkout leads to reservations; private trip, agreement, and message links support the guest journey.

### Reservations, Pricing & Agreements
Rates, seasonal rates, fees, taxes, cancellation policies, and house rules define stay terms. Quotes and reservation lines preserve accepted stay details. Host commands support reservation transitions, amendments, unit reassignment, cancellation requests, and agreement signing.

### Host Operations & Owner Accounting
Properties, units, calendar blocks, and property tasks support accommodation operations. Hosts can manage inbox conversations and review moderation. Owner assignments, statements, statement lines, payout records, security deposits, and damage claims keep financial and ownership records linked to stays; these records are not an external payout or deposit-custody service.

### Payments & Calendar Exchange
Manual payments are recorded by authorized hosts. The Stripe card adapter is explicitly test-mode only and rejects live-mode payments. Refund review and provider-attempt reconciliation are separate host workflows. Direct and iCalendar adapters support calendar exchange; no native OTA adapter is registered.

## Common Use Cases

- Reservations, Pricing & Agreements
- Host Operations & Owner Accounting
- Payments & Calendar Exchange

## Dependencies for Openfront Rental Hosting

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

### Deployment Dependencies

- [openfront-rental on GitHub](https://github.com/openshiporg/openfront-rental)
- [Full README and onboarding instructions](https://github.com/openshiporg/openfront-rental#readme)
- [Railway Buckets](https://docs.railway.com/guides/storage-buckets)

### 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 Rental 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 Rental 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.


## Similar templates

- [Openfront Gym](https://railway.com/deploy/openfront-gym) — Opensource Mindbody alternative based on Next.js and Keystone.js
- [open-excalidraw](https://railway.com/deploy/open-excalidraw) — Self-hostable collaborative drawing built on Excalidraw
- [Next.js + Prisma + PostgreSQL Starter](https://railway.com/deploy/nextjs-prisma-postgres) — Deploy a Next.js app with Prisma ORM and PostgreSQL in one click.

Open this page in a browser: https://railway.com/deploy/openfront-rental