---
title: "Deploy Hyperswitch vs Stripe"
description: "Route Stripe and other processors through one open API"
category: "Other"
url: https://railway.com/deploy/deploy-hyperswitch-vs-stripe-payments
---

# Deploy Hyperswitch vs Stripe

Route Stripe and other processors through one open API

**[Deploy Hyperswitch vs Stripe on Railway](https://railway.com/template/deploy-hyperswitch-vs-stripe-payments)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/deploy-hyperswitch-vs-stripe-payments/manifest.json

- **Creator:** onepush
- **Category:** Other

## Template content

### control-center

- **Image:** juspaydotin/hyperswitch-control-center:v1.38.10@sha256:be7c128fb0e92a22d576c8ec15a8dffda047ceb5242ca1b4d48dc73d20498366
- **Health check:** /health
- **Public domain:** Yes

### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg

- **Image:** redis:8.2.10@sha256:47670742d7924adbcdb404d1288b6327815b23141969c0939b8e5d61f78c2634
- **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"`

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

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

### hyperswitch-router

- **Image:** ghcr.io/onepush-dev/hyperswitch-router:v1.128.0@sha256:71110fad0a471321fc2b1f3794f40f08235b441e64cae4c01dea4904b38fcae4
- **Health check:** /health
- **Public domain:** Yes

## Documentation

# Deploy and Host Hyperswitch vs Stripe (Open-Source Payments Switch) on Railway

This template deploys the Hyperswitch v1.128.0 router, Control Center, Postgres, and Redis on Railway. Hyperswitch is not a processor like Stripe; it routes Stripe and other processor calls through one open-source API.

## About Hosting Hyperswitch vs Stripe on Railway (self hosted Hyperswitch template)

This Railway template runs the open-source Hyperswitch router v1.128.0, the Control Center merchant dashboard, Postgres, and Redis as four connected services.

## Why Deploy Hyperswitch vs Stripe on Railway (Railway Free Trial)

Hyperswitch is free to self host, but you still pay Stripe's processing fees; the point is routing control and no single-processor lock-in. With Stripe alone, you are tied to its checkout and fees.

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 vs Stripe 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 vs Stripe self hosting

Railway deploys the four services as one stack; VPS providers give you a bare server you maintain yourself.

| Provider | What You Get with Railway | What You Get with the Other Provider |
|---|---|---|
| DigitalOcean | Managed deploy, health checks, env wiring | Droplet or App Platform; you set up Postgres, Redis, compose |
| AWS | Service orchestration, restarts, public endpoints | EC2 or EKS; IAM, security groups, manual migrations |
| Hetzner | One-click template, built-in Postgres 18 and Redis 8.2 | Cheap VPS; install Docker, clone repo, configure env vars |

Railway trades control for less operations work, good for test mode.

## Common Use Cases for hosted Hyperswitch vs Stripe

- **Multi-processor checkout:** Run Stripe as one connector, then add Adyen or a local acquirer for new markets without changing your checkout code. Hyperswitch routes each payment by rule, volume split, or priority.
- **Failover without manual swaps:** If Stripe declines or times out, smart retries push the payment to a second processor. You keep one API endpoint while Stripe stays just one route.
- **Vault you control:** Store card tokens in the Hyperswitch vault instead of Stripe's vault, so you can move those tokens to another processor later. Stripe never owns your only copy.
- **Fee negotiation use:** With live routing data across processors, you know exactly how much Stripe handles. That gives you real numbers when renegotiating rates or shifting volume.
- **Test-mode evaluation:** Connect Stripe sandbox keys in the Control Center, run test payments through the router, and compare behavior against other sandboxes before committing production traffic.

## Dependencies for Hyperswitch Docker hosted on Railway

The template bundles four Railway services: the Hyperswitch router, the Control Center dashboard, Postgres, and Redis.

### Deployment Dependencies for Managed Hyperswitch Service (Open-Source Payments Switch)

The managed service depends on Postgres 18 for merchant, routing, and payment data, Redis 8.2 for caching and queues, and two containers: hyperswitch-router (ghcr.io/onepush-dev/hyperswitch-router:v1.128.0) and control-center (juspaydotin/hyperswitch-control-center:v1.38.10).

### Implementation Details for Hyperswitch (Built on the Hyperswitch v1.128.0 router)

The router entrypoint maps Railway Postgres settings and runs database migrations before starting, so the first deploy may take a few minutes. ROUTER__SECRETS__ADMIN_API_KEY and other API keys are generated 32-character strings; JWT_SECRET is 48 characters; MASTER_ENC_KEY, HASH_KEY, and ENCRYPTION_KEY are 64-character hex values.

## How does Hyperswitch compare against other payment orchestration platforms

### Hyperswitch vs Stripe

- **Type:** Hyperswitch is an open-source switch in front of processors. Stripe is a proprietary processor that moves money.
- **Lock-in:** Hyperswitch routes to many processors through one API. Stripe keeps you on its acquirer economics.
- **Vault and PCI:** Hyperswitch gives a self-hosted vault you control. Stripe manages vault and PCI for you. Stripe wins on compliance.
- **Where Stripe wins:** If you only need Stripe, plain Stripe is simpler. Hyperswitch adds infrastructure and PCI scope.

### Hyperswitch vs Adyen

- **Type:** Adyen is an enterprise acquirer and proprietary platform. Hyperswitch is a switch that can route to Adyen.
- **Control:** Adyen offers direct acquiring and risk tooling. Hyperswitch gives routing rules and smart retries.
- **Where Adyen wins:** Adyen handles acquiring deeply. Hyperswitch does not acquire or settle money itself.

### Hyperswitch vs Spreedly

- **Type:** Spreedly is commercial orchestration and vault SaaS. Hyperswitch is self-hosted open source.
- **Cost and control:** Spreedly charges SaaS fees. Hyperswitch is free to self host.
- **Vault:** Both tokenize cards. Spreedly manages the vault. Hyperswitch's vault is yours to operate and back up.
- **Where Spreedly wins:** Managed service and compliance support, no infrastructure to run.

### Hyperswitch vs Primer

- **Type:** Primer is commercial orchestration with no-code workflows. Hyperswitch is code-first and open source.
- **Control:** Primer offers visual payment flows. Hyperswitch uses API config and routing rules in Control Center.
- **Where Primer wins:** Teams that want low-code logic and managed infrastructure. Hyperswitch suits teams that want code ownership.

## How to use Hyperswitch vs Stripe (the OSS Open-Source Payments Switch)?

1. Confirm the router responds: GET /health/ready on the router domain should list Postgres, Redis, and analytics as up before you create the first payment.
2. Open the control-center domain and sign up, then create a merchant and a profile.
3. Add Stripe as a connector with its test-mode keys. Hyperswitch treats Stripe like any other processor you plug in; no special Stripe-only code path exists.
4. Generate an API key in the dashboard and keep it plus the admin API key on your backend only.
5. Call POST /payments on the router domain with the api-key header and a Stripe test card. Stripe handles the first test payment.
6. Add a second processor later and set a volume split or priority rule. Your checkout code stays the same.

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

### Clone the Repository

Get the official source and switch to the v1.128.0 tag.

```
git clone https://github.com/juspay/hyperswitch
cd hyperswitch
git checkout v1.128.0
```

### Install Dependencies

Docker and Docker Compose are the only hard requirements. Hyperswitch builds in Rust, but the published images avoid a local Rust toolchain. Install Docker, then run the repo's setup helper.

```
./scripts/setup.sh
```

### Configure Environment Variables

The compose setup reads router settings from config/docker_compose.toml. Before going past local testing, replace the default admin API key, master encryption key and JWT secret in its secrets section, and point the dashboard and router URLs at your-domain.

### Start the Hyperswitch Application

Bring up the router, control center, Postgres, and Redis.

```
docker compose up -d
```

Open the control center at your-domain, create a merchant, connect a test processor like Stripe, and call the router API.

## Official Pricing of Hyperswitch (Hyperswitch pricing)

The open-source Hyperswitch switch is free to self host under Apache-2.0. You pay only for the infrastructure you run it on, such as Railway, Postgres, and Redis. Processors you connect, like Stripe or Adyen, still charge their own fees.

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

Self hosting gives you the same router and control center code without Juspay's hosted overhead. You keep processor contracts, data, and compliance, while Juspay's cloud removes the operational burden for a usage-based fee.

### Monthly cost of self hosting Hyperswitch on Railway

Expect about $15 to $30 per month for the router, control center, Postgres, and Redis at light use. Railway's $5 trial can cover an initial test-mode deployment, and processor fees are separate either way.

### System Requirements for Hosting Hyperswitch on a VPS

You run four services: the Hyperswitch router, control center, Postgres 18, and Redis 8.2.

## Frequently Asked Questions (FAQs)

### Is Hyperswitch a replacement for Stripe?

No. Hyperswitch is a switch in front of processors, so you still need Stripe or another processor to move money. You get one API and routing rules instead of a single processor's checkout.

### Do I need a Stripe account if I deploy this template?

Yes, for live payments. In test mode you can connect Stripe sandbox keys through the Control Center. Without any processor, the router has nothing to route to.

### Does self-hosting Hyperswitch remove PCI DSS scope?

No. Processing real card data puts you in scope for PCI DSS. This template is for evaluation and test mode; teams that handle compliance can manage it themselves.

### How do I add a second processor later?

Connect another processor like Adyen in the Control Center, then adjust routing rules. Your checkout code does not change because it still calls the same Hyperswitch API.

### What happens if Stripe has an outage?

You can configure smart retries to fail over to another connected processor. Without a second processor, the payment fails like it would on Stripe alone.

### Is the open-source version free to use?

Yes, the Apache-2.0 code is free to self host. Processors still charge their own fees, and Juspay also offers a hosted Hyperswitch cloud with usage-based pricing.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/deploy-hyperswitch-vs-stripe-payments