Deploy and Host self hosted Hoppscotch (Open-Source API Client) on Railway

This template deploys Hoppscotch Community Edition 2026.9.0 as one AIO image on a single Railway domain with Postgres. Login methods are configured in the /admin wizard after first deploy, ideal for backend teams moving off Postman.

About Hosting Hoppscotch open-source software on Railway (self hosted Hoppscotch template)

This template runs the official Hoppscotch 2026.9.0 AIO image on one Railway domain with subpath access, backed by Railway Postgres. You finish setup by picking a sign-in method there, so no deploy-time input is needed.

Why Deploy Hoppscotch, the Postman alternative on Railway (Railway Free Trial)

Postman stores collections in its cloud and pushes team plans quickly.

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 Hoppscotch 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.

Railway vs Other Hosting Providers and VPS for Hoppscotch self hosting

Railway handles the container, domain, Postgres and migrations while these providers hand you more infrastructure to assemble yourself.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Managed container, Postgres and auto migrations; finish the /admin wizard only.	App Platform or Droplet: set up Caddy, database, env vars and migrations yourself.
AWS	One template gives you app, database, TLS, health checks and restart policy.	ECS/Fargate plus RDS need VPC, IAM, load balancer and manual migration commands.
Hetzner	No server maintenance, automatic restarts and encrypted secrets out of the box.	Cheap VPS: install Docker, Postgres, reverse proxy, TLS and run migrations by hand.

Common Use Cases for hosted Hoppscotch

Team API workspace: Create shared collections and environments so every dev uses the same base URLs, auth headers, and test scripts without emailing JSON files around.
CI collection runs: Export a collection and run it with the Hoppscotch CLI in GitHub Actions or any pipeline, failing builds when a contract test breaks.
Onboarding new engineers: Point teammates at the /admin invite flow, then they open the hosted URL and immediately see your internal endpoints instead of installing a desktop client.
Private API access: Use the desktop app or browser extension pointed at your hosted instance to reach VPC-only services, since the built-in proxy only handles public CORS requests.

Dependencies for Hoppscotch Docker hosted on Railway

The template depends on two services: the Hoppscotch 2026.9.0 AIO image and Postgres 18.6. Login methods are configured in the /admin wizard, not env vars. The only hard dependency is Postgres; the app container is stateless.

Deployment Dependencies for Managed Hoppscotch Service (API Development Platform)

The Hoppscotch service runs hoppscotch/hoppscotch:2026.9.0 with restart policy ALWAYS and a /ping health check. Postgres runs postgres-ssl, private only, with volume /var/lib/postgresql/data.

Implementation Details for Hoppscotch (Using the official Hoppscotch 2026.9.0 AIO image)

The AIO image bundles Caddy, the NestJS backend, and the web app. The start command runs prisma migrate deploy automatically on every deploy. VITE variables are injected at start, so changes need a redeploy, not a rebuild.

How does Hoppscotch compare against other API clients

These four comparisons focus on what changes when you move from a desktop or IDE tool to a self-hosted browser client on Railway. The trade-offs matter most for teams deciding where requests and collections live.

Hoppscotch vs Postman (Postman Alternative)

Self-hosted data: collections and environments live in your Postgres, not Postman's cloud; the MIT Community Edition is free.
One domain: the AIO image serves the web app, admin panel, and API from a single Railway URL, so you skip desktop sync accounts.
Where Postman wins: mock servers and published API docs are more mature, and its desktop app still has smoother offline work.

Hoppscotch vs Insomnia (Insomnia Alternative)

No cloud lock-in: team workspaces sit behind your own sign-in, not Kong's sync service, so you control access and data.
Protocol breadth: REST, GraphQL, WebSocket, SSE, Socket.IO, and MQTT all run in one browser UI.
Where Insomnia wins: desktop-first workflows feel smoother when you do not want to run a server at all.

Hoppscotch vs Bruno (Bruno Alternative)

Hosted collaboration: Bruno is offline and file-based; Hoppscotch gives shared requests and roles from a URL anyone can open.
No install needed: teammates open the Railway domain and start testing, which helps non-developer reviewers.
Where Bruno wins: git-friendly collection files are simpler for solo developers who keep everything in one repo.

Hoppscotch vs Thunder Client (Thunder Client Alternative)

Beyond VS Code: Hoppscotch is a standalone web app, so testers and QA folks do not need an IDE to hit your APIs.
Team features included: roles, shared collections, and admin controls come with the open-source server, not a paid tier.
Where Thunder Client wins: it lives inside VS Code, which is convenient when all API testing happens next to code.

How to use Hoppscotch (the OSS API client)?

Open https://your-domain/admin and complete the onboarding wizard. Pick GitHub, Google, Microsoft, or email magic link via SMTP. Save; the backend restarts itself.
Sign in on /admin first. That account becomes instance admin. Invite teammates from /admin Users; invites need SMTP.
Open the web app at your domain to create REST, GraphQL, WebSocket, SSE, or MQTT requests. Import collections from Postman, Insomnia, or OpenAPI files.
Use collections, environments, and pre-request scripts. For CI, install @hoppscotch/cli and run collections headlessly.
Point the Hoppscotch desktop app at your domain. APIs without CORS headers go through the proxy; private APIs need the browser extension or the desktop app.

How to self host Hoppscotch on other VPS Services (Hoppscotch self hosting guide)

Clone the Repository

git clone https://github.com/hoppscotch/hoppscotch.git
cd hoppscotch
cp .env.example .env

Install Dependencies

Docker and a reachable Postgres database are the only host dependencies. The AIO image bundles the app, admin, and backend.

Configure Environment Variables

Set DATABASE_URL, DATA_ENCRYPTION_KEY (32 chars), ENABLE_SUBPATH_BASED_ACCESS=true and the VITE URLs for your-domain: VITE_BASE_URL, VITE_ADMIN_URL, VITE_BACKEND_GQL_URL, VITE_BACKEND_WS_URL, VITE_BACKEND_API_URL. Use https://your-domain with /admin and /backend paths.

Start the Hoppscotch Application

docker run -d --env-file .env -p 80:80 hoppscotch/hoppscotch:2026.9.0
docker exec HOPSCOTCH_CONTAINER_ID pnpm exec prisma migrate deploy

Put HTTPS in front for OAuth callbacks.

Official Pricing of Hoppscotch (Hoppscotch pricing)

The Community Edition is free and MIT licensed, so self hosting costs nothing beyond your Railway infrastructure. Hoppscotch Cloud adds a free plan for individuals plus paid team and Enterprise plans, and a paid self-hosted Enterprise Edition adds SSO and audit features. Check hoppscotch.com for current numbers.

Hoppscotch cloud vs self hosted comparison (Pricing, features, costs, and more)

Self hosting the Community Edition keeps the MIT-licensed core on your own Railway project, with the AIO image and Postgres doing the work. Cloud plans add managed sync and support, but a small team can run this stack cheaply.

Monthly cost of self hosting Hoppscotch on Railway

Expect roughly $5-10/mo at light use for the Hoppscotch service and Railway Postgres. The container idles around 0.5 GB RAM, and Postgres stays small, so most teams stay near the low end of that range.

System Requirements for Hosting Hoppscotch on a VPS

A single vCPU with 1-2 GB RAM is enough for a small team. The AIO container idles around 0.5 GB RAM and Postgres adds little.

Frequently Asked Questions (FAQs)

Why is there no password login?

Hoppscotch uses GitHub, Google, Microsoft, or email magic links instead of local passwords. That avoids storing password hashes and keeps account recovery outside your database. Pick one or more methods in /admin.

Who becomes the instance admin?

The first account that signs in on /admin after the onboarding wizard becomes the admin. No env var sets it. Finish the wizard, then sign in yourself before inviting teammates.

Why does the desktop app throw CORS errors?

The desktop app sends its own app:// origin, which the backend checks against WHITELISTED_ORIGINS. If yours is missing, add app:// plus your domain with dots and dashes replaced by underscores to WHITELISTED_ORIGINS, then redeploy.

Where does my data live?

Collections, environments, teams, and settings live in the Railway Postgres database. The Hoppscotch container is stateless. DATA_ENCRYPTION_KEY encrypts stored secrets inside Postgres.

How do I upgrade Hoppscotch?

Change the image tag to a newer 2026.x AIO tag and redeploy. Back up Postgres first; the start command runs prisma migrate deploy automatically. Keep DATA_ENCRYPTION_KEY unchanged or old secrets become unreadable.

What is the Hoppscotch proxy for?

The proxy at proxy.hoppscotch.io forwards browser requests to APIs that don't send CORS headers. For private APIs, run your own proxy, use the browser extension, or use the desktop app so traffic stays inside your network.