Hyperswitch

What is Hyperswitch?

Hyperswitch is an open source payment orchestration platform that sits between your app and the payment processors. You integrate its single API once, and it routes each transaction across 100+ connectors — Stripe, Adyen, PayPal, Braintree, Worldpay, Checkout.com and more — so you’re not locked into one gateway. Built by Juspay and written in Rust, it’s Apache-2.0 licensed and self-hostable.

What is Hyperswitch best for?

Businesses that process meaningful payment volume across more than one processor and want control over routing, cost, and vendor relationships. It fits fintechs, SaaS platforms, marketplaces, and enterprises that need to add processors, route by success rate or cost, and keep card data in their own vault — rather than being tied to a single provider’s rails and pricing.

What can Hyperswitch do?

• Route payments across 100+ processors and acquirers through one unified API and SDK
• Improve authorization rates and cut costs with rule-based and success-rate-based intelligent routing
• Recover failed and churned payments with a smart retry (dunning) engine
• Vault cards, tokens, and wallet credentials in a PCI-compliant store, with bring-your-own-vault support
• Automate 2-way and 3-way reconciliation across processors
• Track processing fees and spot anomalies with cost observability
• Drop in prebuilt widgets and SDKs for web, Android, iOS, React Native, and Flutter, including Apple Pay, Google Pay, PayPal, and BNPL

Is Hyperswitch free?

Yes — Hyperswitch is free and open source under Apache-2.0, and you can self-host the full platform at no license cost; you only pay for the infrastructure it runs on and your processors’ transaction fees. Juspay also offers a managed, hosted version with compliance, SLAs, and support for teams that don’t want to run it themselves.

Where does Hyperswitch fall short?

• It orchestrates payments but is not itself a payment processor or merchant of record — you still need your own merchant accounts and processor contracts, and you inherit PCI scope when self-hosting the vault.
• It’s a heavier, more operationally involved system than a single-gateway SDK: the platform is a set of Rust microservices (app server, card vault, encryption service, routing control plane) meant for teams with real payment volume, so it’s overkill if you just need to accept cards on one processor.
• The open source project moves fast and targets engineering teams; features like advanced routing and revenue recovery assume you have the payments expertise to configure them well.

What does Hyperswitch replace?

Hyperswitch is a self-hostable alternative to hosted payment orchestration and gateway products like Stripe, Adyen, Braintree, and Spreedly. Instead of routing all volume and card data through one vendor’s cloud, you run the orchestration layer yourself and connect the processors you choose.

FAQ

Is Hyperswitch open source? Yes. The core platform is licensed under Apache-2.0 — a permissive OSI-approved license — and the full source is on GitHub. You can self-host, modify, and deploy it without a license fee.

Can I self-host Hyperswitch for free? Yes. You can run it locally with Docker or in production on Kubernetes via Helm charts on AWS, GCP, or Azure. The software is free; you pay only for your servers and your processors’ fees.

Is Hyperswitch a good Stripe alternative? For teams that use more than one processor, yes — it gives you routing, a vault, and reconciliation across providers instead of locking you to one. If you only need to accept cards on a single gateway with minimal setup, a hosted product like Stripe is simpler.

What do I need to run Hyperswitch? Docker or Podman for local testing, and Kubernetes for production deployment. You also need your own merchant accounts and API credentials for whichever payment processors you want to connect.