Deploy and Host self hosted Hyperswitch Control Center (Open-Source Payments Orchestration) on Railway

This template runs the Hyperswitch Control Center dashboard on port 9000 next to the router API. The two point at each other, so sign-up, login, and every setting go through the router. For engineers evaluating Hyperswitch.

About Hosting Hyperswitch Control Center open-source software on Railway (self hosted Hyperswitch template)

This template runs the Hyperswitch Control Center as a public dashboard on port 9000, next to the hyperswitch-router API on 8080. All merchant, connector, API key, payment, and routing data stays in Postgres.

Why Deploy Hyperswitch Control Center, the Spreedly alternative on Railway (Railway Free Trial)

Spreedly rents a hosted vault and dashboard that scales with volume. Hyperswitch is the open-source route: you keep processor keys and routing rules in your own Postgres and only pay Railway for containers. The $5 trial is enough to sign up and add Stripe test keys.

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 Hyperswitch Control Center 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 Hyperswitch Control Center self hosting

Railway gives you the router, Control Center, Postgres and Redis as connected services with generated secrets, while a raw VPS leaves you wiring each piece yourself.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Managed Postgres, Redis, and connected services	Manual Docker, Postgres, Redis, and env wiring
AWS	One project with attached database and Redis	ECS, RDS, ElastiCache, and IAM across consoles
Hetzner	Automatic rebuilds and health checks	Cheap capacity but you manage OS and backups

Common Use Cases for hosted Hyperswitch Control Center

Add a second processor: Use the dashboard's connectors screen to paste sandbox keys from Stripe or Adyen and enable them without a code deploy.
Compare processors with volume split: Set a routing rule that sends 50% of test payments to each connector, then watch the payments list to see approval rates.
Issue separate API keys: Create staging and production keys from the dashboard, so your backend uses different credentials without sharing a single token.
Review failed payments and retries: Open the payments screen to filter declines, check the smart retry status, and see which connector actually succeeded.
Give finance a view: Let non-engineers check payment totals and refunds in the dashboard without backend access.

Dependencies for Hyperswitch Control Center Docker hosted on Railway

This template runs hyperswitch-router on 8080, Control Center on 9000, Postgres 18, and Redis 8.2. The dashboard has no database; every sign-up, login, connector key, routing rule, and API key lives in the router's Postgres, so both web services must be healthy.

Deployment Dependencies for Managed Hyperswitch Control Center Service (Payments Orchestration)

The apps are wired by env vars: ROUTER__USER__BASE_URL points the router at the Control Center domain, and the dashboard's default__endpoints__api_url points at the router domain. Postgres and Redis are hard dependencies for the router only.

Implementation Details for Hyperswitch Control Center (Using Hyperswitch official docker image)

The router image's entrypoint maps Railway's Postgres settings and runs migrations before starting on 8080. /health returns "health is good"; /health/ready reports database, Redis, and analytics status. The router mounts a volume at /local/bin/files.

How does Hyperswitch Control Center compare against other payment orchestration platforms

Hyperswitch vs Spreedly

Cost: Hyperswitch is free to self host; Spreedly charges per transaction on top of processors.
Ownership: Control Center is open source and runs on your Railway project; Spreedly hosts its dashboard for you.
Vault: Hyperswitch's vault keeps card tokens in your own stack, so PCI scope is yours; Spreedly owns vault compliance.
Code: You can modify Hyperswitch; Spreedly is closed source.

Hyperswitch vs Primer

Workflows: Primer has visual no-code builders; Hyperswitch routing is config driven and needs an engineer.
Hosting: Control Center is self hosted; Primer is a managed SaaS you cannot control.
Lock-in: Hyperswitch uses a unified API you own; Primer sits between you and processors.
Cost: Hyperswitch is free to run; Primer adds a platform fee.

Hyperswitch vs Stripe Dashboard

Processor choice: Hyperswitch routes across 50 plus processors; Stripe Dashboard manages only Stripe.
Deployment: Control Center is open source and self hosted; Stripe's dashboard is proprietary.
Compliance: Stripe handles PCI with hosted fields; Hyperswitch live mode puts card data in your scope.

Hyperswitch vs Adyen Customer Area

Audience: Hyperswitch suits payment engineers; Adyen targets enterprise finance and risk teams.
Ops: You deploy Control Center yourself; Adyen is managed with SLAs.
Flexibility: Hyperswitch routes across Adyen and others; Adyen dashboard manages only Adyen.
Cost: Hyperswitch is free to self host; Adyen charges negotiated enterprise fees.

How to use Hyperswitch Control Center (the OSS payment orchestrator)?

Open the control-center domain on port 9000 and sign up the first user.
Create a merchant and a business profile from the dashboard.
Add Stripe as a connector using its sandbox keys, then mark it test mode.
Run a test payment from the dashboard to confirm the connector works.
Create an API key for your backend.
From your backend, call POST /payments on the router domain with the api-key header.
Add a second connector, then create a volume-split routing rule to compare processors.
Review payments, refunds, disputes and analytics in the dashboard.

Every setting in the dashboard goes through the router API, so keep both services healthy while you test.

How to self host Hyperswitch Control Center on other VPS Services (Hyperswitch self hosting guide)

Clone the Repository

Clone the official Hyperswitch stack, which includes both the router and the Control Center dashboard.

git clone https://github.com/juspay/hyperswitch
cd hyperswitch

Install Dependencies

Install Docker and Docker Compose on your VPS. The repo includes a setup script that prepares configuration.

./scripts/setup.sh

Configure Environment Variables

The compose setup reads the repo's config files. Replace the sample secrets (master encryption key, JWT secret, hash key) with your own, point the router's user base URL at your Control Center domain and the dashboard's API URL at your router domain.

Start the Hyperswitch Control Center Application

Start both services with Docker Compose, then open the Control Center on port 9000 to sign up.

docker compose up -d

Railway handles all of this for you by provisioning Postgres, Redis, secrets, and public domains in one template deploy.

Official Pricing of Hyperswitch Control Center (Hyperswitch pricing)

Hyperswitch Control Center is open source under Apache-2.0 and free to self host. Juspay also sells a hosted Hyperswitch cloud with usage-based pricing, but no public numbers. Processors still charge their own fees per transaction.

Hyperswitch Control Center cloud vs self hosted comparison (Pricing, features, costs, and more)

Self hosting the Control Center is free; you only pay for the infrastructure it runs on and any processor fees from test or live payments. Juspay also offers a hosted cloud with usage based pricing, but self hosting keeps all merchant and connector data in your own Postgres.

Monthly cost of self hosting Hyperswitch Control Center on Railway

On Railway, the router, dashboard, Postgres, and Redis services typically run about $15 to $30 per month at light use. Processors still charge their own per transaction fees regardless of where Hyperswitch runs.

System Requirements for Hosting Hyperswitch Control Center on a VPS

The stack is light enough for a small VPS: the Rust router and the dashboard web app need modest CPU, while Postgres and Redis add memory. Plan for at least 2 GB RAM and 10 GB disk for test traffic; scale up only when you move to live payments. No special GPU or enterprise hardware is required.

Frequently Asked Questions (FAQs)

Why does login fail if the router is down?

The dashboard is only a frontend for the router API; it holds no local data. If the router or Postgres is down, sign-up, login and settings all fail.

Can I hide the dashboard from the internet?

Yes. Remove the public domain from control-center and reach it privately, or put it behind your own auth. Keep ROUTER__USER__BASE_URL updated.

Who can sign up?

Anyone who can reach the dashboard can create the first user and merchant profile. After setup, restrict the public domain so strangers cannot sign up.

Where are connector keys stored?

Connector credentials entered in the dashboard go to the router and are stored encrypted in Postgres using MASTER_ENC_KEY. Back up that key.

Is the dashboard open source?

Yes. It is Apache-2.0 at github.com/juspay/hyperswitch-control-center. You can inspect or patch it.

Does it work in live mode?

Yes, but live card processing puts you in PCI DSS scope. The template is test-mode by default; for live, handle compliance and use production keys.