HyperSwitch
A self-hostable payments switch that connects one integration to many processors, with routing, retries, a card vault and reconciliation.
What is HyperSwitch?
HyperSwitch from Juspay sits between your checkout and payment providers. Instead of coding against Stripe, Adyen, Braintree, Worldpay, Checkout.com and others one by one, you integrate once and route each transaction to the processor with the best predicted approval rate. Separate modules cover cost observability, retry-based revenue recovery, a PCI-compliant vault for cards and tokens, two- and three-way reconciliation, and drop-in widgets for wallets and buy-now-pay-later methods. A Control Center web app manages it, with 14 interface languages.
Good fit if
- You process payments through several providers and want to stop hard-wiring each one.
- You want to own card storage and routing logic instead of paying an orchestration vendor.
Look elsewhere if
- You only need one processor and a simple checkout; a direct integration is lighter.
- You want an API gateway for your own services rather than payment flows: Kong.
Before you adopt it
The code is under Apache-2.0, and contributors must sign a CLA. No paid parts were found in the repository, though Juspay also sells a hosted SaaS. Development is busy and spread over dozens of people. Expect a heavy deployment: the full Docker Compose profile starts many services, including PostgreSQL, Redis, Kafka, ClickHouse and Elasticsearch, and a minimal profile runs only the app server.
Drafted with AI from the project's README and repository data, then checked against that data on 31 October 2026. Report a correction
HyperSwitch health: is it still maintained?
84 of 100, actively developed
Read from GitHub on 3 November 2026. How the score works
HyperSwitch license: is it open source?
HyperSwitch uses Apache-2.0, an open-source license approved by the OSI. Contributors sign a contributor license agreement, which lets the owner relicense their work later.
- October 2022First published on GitHub.
- TodayApache-2.0. A contributor license agreement is required.
How to run HyperSwitch yourself
- Docker
- Dockerfile or compose file in the repository
- Compose file
- docker-compose.yml: 30 services (postgres, redis, kafka, clickhouse, elasticsearch)
- Setup effort
- 5 of 5, judged from the compose file
- Kubernetes
- No Helm chart in the repository
- Desktop and mobile
- No app builds in GitHub releases
- Interface languages
- 14 languages
Install instructions: hyperswitch.io or the README on GitHub.
Alternatives to HyperSwitch
- LangfuseOpen source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform. 89 health · MIT · 36.9k stars
- SentryDeveloper-first error tracking and performance monitoring 85 health · Functional Source License · 45.7k stars
- code-serverVS Code in the browser 85 health · MIT · 79.8k stars
- NovuThe open-source communication infrastructure for agents and products 81 health · MIT · 40.3k stars
- HasuraBlazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger… 80 health · Apache-2.0 · 32.1k stars
Questions about HyperSwitch
Is HyperSwitch open source?
Yes. HyperSwitch is published under Apache-2.0, an OSI-approved open-source license.
Is HyperSwitch still maintained?
Its health score is 84 of 100 (actively developed). It had 663 commits in the last 90 days, the latest on 3 November 2026, and its latest release came out on 2 November 2026.
How do I run HyperSwitch?
You can run it with Docker. The README on GitHub has the exact steps.
What are the alternatives to HyperSwitch?
Close alternatives in the Developer tools category include Langfuse, Sentry, code-server.