HyperSwitch

Payment switch to make payments fast, reliable and affordable. Connect with multiple payment processors and route traffic effortlessly, all with a single API integration.

Thriving · 91
91/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 35/40
Releases 25/25
Community 19/20
Momentum 12/15

Commit activity more than 88% of tracked projects; popularity more than 96%. How this is calculated.

Commits, last 11 months

2025-12: 187 commits 2026-01: 184 commits 2026-02: 158 commits 2026-03: 152 commits 2026-04: 161 commits 2026-05: 179 commits 2026-06: 202 commits 2026-07: 232 commits 2026-08: 186 commits 2026-09: 231 commits 2026-10: 242 commits
2025-12 2114 total 2026-10
Stars46k
Latest releasev1.129.0 · 2 Nov 2026
Repo updated20 Nov 2026
LicenceApache-2.0
Built withDocker, Rust

Is HyperSwitch actively maintained?

HyperSwitch is under active development: 2114 commits landed over the last 11 months, averaging roughly 220 commits a month in the most recent quarter.

The most recent tagged release, v1.129.0, shipped within the last month — a current, installable version exists today.

Note that HyperSwitch depends on a third-party service to work fully. It is self-hosted, but not self-contained: if that external service changes its terms or disappears, your instance is affected.

Of the 42 projects we track in Money, Budgeting & Management, HyperSwitch ranks #3 by health score — in the top quarter of its category.

What HyperSwitch actually does

HyperSwitch is a self-hosted payment routing engine designed to connect your application with multiple payment processors through a single API interface. It acts as an intermediary to manage payment traffic and provider distribution. The system is built with Rust and packaged via Docker.

Best fit: Engineering teams processing high volumes of transactions who want to avoid vendor lock-in and programmatically route payments across various processors.

Worth knowing: Operating a self-hosted payment switch introduces significant compliance requirements, such as PCI-DSS adherence, and creates a critical failure point for financial operations.

Deployment notes

Deployment typically involves running containerised images through Docker, requiring persistent storage for state management and an external database backend.


HyperSwitch as a replacement for


Alternatives to HyperSwitch

Projects in the same categories, ordered by health score.