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

# Deploy Openfront Hospital

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

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

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/openfront-hospital/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-hospital

- **Source:** https://github.com/openshiporg/openfront-hospital
- **Start command:** `next start`
- **Health check:** /api/health
- **Public domain:** Yes

## Buckets

- **Storage**

## Documentation

# Deploy and Host Openfront Hospital with Railway

Openfront Hospital is a self-hostable care-booking and hospital-operations application. Visitors can explore care services and providers, request appointments, and complete intake. Staff coordinate registration, scheduling, patient records, encounters, inpatient capacity, clinical fulfillment, claims, communication, and reporting.

## About Hosting Openfront Hospital

This template provisions the application from [its GitHub repository](https://github.com/openshiporg/openfront-hospital), 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`.

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

### Admin Dashboard
Manage patients, inpatient, registration, appointments, operational fabric, store settings, clinical operations, schedules, intake, clinical fulfillment, encounters, care queue through dedicated dashboard workspaces and permission-controlled data screens.

### Storefront
Public routes include `/care`, `/providers`, `/book`, appointment-type booking pages, and `/intake`. Intake access and appointment requests are separate from staff access to clinical records.

### Registration & Care Coordination
Maintain patient identity and coverage, registration, appointment types, provider schedules, care queues, intake, consent, and secure patient communication.

### Clinical & Inpatient Operations
Coordinate encounters, admissions, beds and reservations, care plans, medical orders, prescriptions, laboratory records, procedures, specimens, and episode closure workflows.

### Billing & Data Governance
Track claims and claim versions, patient payments and refunds, inventory, integration delivery, portability, retention, record holds, and clinical audit events. Software workflows do not establish clinical, privacy, or regulatory certification.

## Common Use Cases

- Registration & Care Coordination
- Clinical & Inpatient Operations
- Billing & Data Governance

## Dependencies for Openfront Hospital Hosting

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

### Deployment Dependencies

- [openfront-hospital on GitHub](https://github.com/openshiporg/openfront-hospital)
- [Full README and onboarding instructions](https://github.com/openshiporg/openfront-hospital#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 Hospital 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 Hospital 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-hospital