Tools/juspay/hyperswitch

hyperswitch

Open source, composable payments platform | PCI compliant | SaaS and Self-host options | Enables connectivity to multiple payment, payout, fraud, vault and tokenization providers | Uplifts authorization with intelligent routing and revenue recovery | Reduce payment processing costs with cost observability | Reduces payment ops with reconciliation

43.2kemergingRustApache License 2.0

The Lens

Hyperswitch sits between your app and payment processors like Stripe, Adyen, and PayPal, routing each transaction to whichever is cheapest or most likely to succeed. Juspay built it after processing billions of transactions and open sourced the core in Rust under Apache 2.0. One API, many processors, no rewrite when you add or drop one.

Self-hosting the Community Edition is real infrastructure: the router, Postgres, Redis, and a control center UI, plus the PCI scope questions that arrive the moment card data flows through systems you operate. This is a payments team tool, not a weekend deploy.

Single-processor startups don't need it; Stripe alone is simpler than Stripe behind a switch. It earns its keep when you juggle multiple processors for fees, geographic coverage, or failover. Solo and small teams: skip. Companies at real volume: smart routing and retry logic can recover a measurable slice of revenue. Enterprise Edition and Cloud exist when you'd rather pay Juspay to run it.

The catch: it orchestrates payments, it doesn't process them. You still need contracts with the underlying processors, and advanced features like revenue recovery and reconciliation are paid add-ons even on top of the open core.

Free vs Self-Hosted vs Paid

open core

Free Tier (Community Edition)

The core payments switch, Apache 2.0: unified API across processors (Stripe, Adyen, PayPal, and dozens more), smart routing rules, retries, a control center UI, and vaulting integration. Self-hosted with no transaction fees to Juspay.

Self-Hosted Setup

Heavier than most tools on this site: the Rust router, Postgres, Redis, and the control center, typically on Kubernetes for production. Add PCI DSS scope: once card data touches your deployment, compliance is your problem. Plan on a dedicated engineer for setup and ongoing ownership, not an afternoon.

Paid Tiers

  • Enterprise Edition (self-hosted): support SLAs, dedicated account management, expert guidance. Contact sales.
  • Hyperswitch Cloud: fully hosted with uptime guarantees and compliance handled. Contact sales.
  • Add-ons: revenue recovery, cost observability, and reconciliation are paid modules across tiers.

The Math

The savings case is routing: sending transactions to the cheapest viable processor and retrying intelligently. On low volume that's noise. At millions/month in payments, a fraction of a percent in fees or recovered failures pays for the infrastructure many times over.

Verdict

Free core, paid convenience and paid advanced modules. Only worth it once multiple processors are already your reality.

Open core payments routing, free to self-host. The value math only works at multi-processor volume, and the fancy modules cost extra.

Self-hosting ops:heavy

Get tools like this every Wednesday

One featured tool, three on the radar. No fluff.

Similar Tools

Score
67/100 · B
Adoption27/30
Maintenance10/25
Community5/20
License15/15
Analysis10/10

License: Apache License 2.0

Use freely. Patent grant included.

Commercial use: ✓ Yes

About

Owner
Juspay Technologies (Organization)
Stars
43,201
Forks
4,949

Explore Further

More tools in the directory