Deploy Hyperswitch

Open-source payments switch: API, Control Center dashboard and Web SDK

Deploy Hyperswitch

Just deployed

/data

/var/lib/postgresql/data

/local/bin/files

Just deployed

Deploy and Host Hyperswitch on Railway

Hyperswitch is an open-source payments switch by Juspay (Apache-2.0). One API connects your checkout to many payment processors, with routing, retries, refunds, payouts and fraud checks. The Control Center dashboard manages connectors, API keys and payments, and the Web SDK renders the checkout form in your page.

About Hosting Hyperswitch

This template deploys Hyperswitch v1.129.0 with the versions from its release compatibility matrix: the router (payments API), Control Center v1.39.0 and Web SDK v0.135.0. They run alongside Railway Postgres and Redis. Every service builds from a public GitHub repo that pins the official Juspay images by version and digest. On each start the router runs the release's own database migrations. All secrets and encryption keys are generated at deploy, so nothing needs to be filled in. Postgres, Redis and the router's file store sit on volumes. All three app services get a public domain and a health check.

Common Use Cases

  • Route payments across several processors (Stripe, Adyen, Checkout.com and others) behind one API
  • Evaluate or develop against a self-hosted payments orchestrator with the built-in PhonyPay test processor
  • Run a payments dashboard and checkout SDK for a sandbox or staging environment you control

Dependencies for Hyperswitch Hosting

  • PostgreSQL (Railway Postgres)
  • Redis (Railway Redis)

Deployment Dependencies

Implementation Details

After deploy:

  1. Open the control-center URL and sign up. The first account creates your organization and becomes its admin. Sign-up stays open, so anyone who can reach the URL can create their own separate organization. Keep the URL private if that matters to you.
  2. Under Connectors, add a processor. PhonyPay works without an outside account.
  3. Create an API key and call https://YOUR-ROUTER-DOMAIN/payments with the header api-key: YOUR-API-KEY.
  4. In your checkout page, load https://YOUR-WEB-SDK-DOMAIN/web/0.135.0/v1/HyperLoader.js.

Back up ROUTER__SECRETS__MASTER_ENC_KEY on the router service. It encrypts merchant data, and without it the database can't be read. The stack uses Hyperswitch's mock card locker, so it is meant for evaluation and sandbox processing. Storing real card data needs the separate Hyperswitch Card Vault and your own PCI DSS work.

Updates: when the template repo moves to a new Hyperswitch release, Railway shows "update available" on your project. Read the repo's CHANGELOG.md, back up Postgres, then apply the update. The router runs any new migrations on its next start.

Why Deploy Hyperswitch 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 Hyperswitch 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

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0