DISCLAIMER: This page is for information only. It is not legal, financial or procurement advice and does not replace your own due diligence. Licenses, ownership, features and certifications can change: confirm what your decision rests on with the official sources.
🩺 Vitals
- 🟢 Last active: 2026-11-04
- 📦 Latest release: v1.129.0 (2026-11-02)
- 🐞 Open issues: 2360
- 🌟 Stars: 45.7k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent stable version the maintainers published as a release on the forge. Some healthy projects publish only tags, or publish their versions elsewhere.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: hyperswitch.io
- Source: github.com/juspay/hyperswitch
- License: Apache-2.0 (core; paid edition under its own terms)
- Deployment: Docker Container | Kubernetes (K8s)
- Jurisdiction: India 🇮🇳 (Juspay Technologies Private Limited)
- Compliance (SaaS): Hyperswitch Cloud security and compliance page
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: Very High (5/5) - Several service tiers, each sized on its own: the payment router and its workers, a card vault, PostgreSQL, Redis, Kafka and ClickHouse in the Helm default
- Maintenance: High (4/5) - Blue/green cluster upgrades with a database backup and a migration job at each release; unlocking the card vault after a restart needs several key custodians
- User Management: Moderate (3/5) - Team accounts with default and custom roles and TLS in its own server in the free build; OpenID Connect sign-in only through the admin API; no audit log, no SCIM
What the scores mean: Reading the Scores
1. The Executive Summary
What is it? Hyperswitch is a payments orchestration platform: one integration that routes each payment to one of many payment processors, Stripe, Adyen and Braintree among them, by rules the merchant sets, with a vault that stores cards and tokens on the merchant's own servers. It serves merchants and platforms that outgrow a single processor and want routing and stored cards under their own control. The paid edition adds revenue recovery for failed subscription payments, payment cost observability and reconciliation.
The Strategic Verdict:
- 🔴 For merchants without a platform team: Caution. It runs as several service tiers, each sized on its own, and card data on your servers brings your own environment under PCI DSS (Complexity, The Compliance Shift).
- 🟢 For merchants routing payments across several processors: Strong Buy. Routing and the card vault come in the free build with no license fee, so stored cards stay on your servers whichever processor you use (What is it?, Cost of Ownership).
2. Cost of Ownership
| Cost Component | Hyperswitch (Self-Hosted) |
|---|---|
| Pricing Model | No license fee for the core; paid edition for some features |
| Adoption | Manual migration (Stripe SDK and API calls replaced with Hyperswitch's) |
| Operations | Distributed cluster, grows with transaction volume; plus your team's time to run it (Maintenance, in the Profile) |
| Support | From the vendor: Hyperswitch Cloud, a managed service, and paid support for self-hosted installs (enterprise support); elsewhere, a paid service provider |
| Usage Meters | Paid to your payment provider (per transaction) |
| Exit | Payments as CSV (a data pipeline the operator builds); leaves out stored cards, which the vault returns one at a time through its API |
What each row covers: Total Cost of Ownership
3. Risk Assessment
- Jurisdiction: Juspay Technologies Private Limited, the project's vendor, is registered in India, under that country's law. The vendor runs Hyperswitch Cloud, a hosted service where your data can live; its hosts include a party domiciled in or controlled from the US. Data that party holds for Hyperswitch Cloud is within reach of the US CLOUD Act, wherever it is stored, if the party is based in the US or its US parent controls the data. US law can compel Scarf Systems, Inc. in the United States to hand over the usage data every install sends it.
- The Compliance Shift: Every install sends usage data to Scarf Systems, Inc. in the United States with no setting to switch it off, so the operator must account for that transfer in its own compliance work. Card data that passes through your servers brings your own environment under PCI DSS, and your payment brands and acquirer decide how it is validated. Self-hosting moves the security and compliance duties of running the software to the operator (the operator's compliance checklist). Any audit of Hyperswitch Cloud (such as SOC 2 or ISO 27001) covers the vendor's own systems, never your install.
- License Risk: Hyperswitch is under Apache-2.0, an OSI-approved permissive license (what it allows and requires). Apache-2.0 lets anyone, the vendor included, release modified versions under other terms, closed ones too. The optional Decision Engine, for cost-aware and approval-rate-aware routing, is a separate repository under AGPL-3.0.
4. Market Landscape
🏢 Proprietary Incumbents
- Stripe: Stripe is a platform for accepting payments online and in person.
Data held by: Stripe, LLC, United States 🇺🇸, subject to the US CLOUD Act for the data it holds, wherever it is stored.
Why teams leave: Routing to other processors is offered only on request, and its fee is a share of every payment.
Exit: Card data export to a PCI DSS Level 1 processor, on request; other data through the API, partial export (Link-saved credentials)
With Hyperswitch: Routing across processors, Stripe among them, comes in the free build with no license fee (What is it?, Cost of Ownership).
🤝 Open-Source Alternatives
—