Hyperswitch vs Rafiki
Hyperswitch and Rafiki are both payment orchestration software. Hyperswitch is open source under Apache-2.0, with 46k GitHub stars. Rafiki is open source under Apache-2.0, with 360 GitHub stars.
Which to pick
- Pick Hyperswitch when
- You process enough payments to benefit from routing across several processors and have engineers to run it.
- Pick Rafiki when
- You operate a digital wallet or account service and want to join the Interledger network.
Side by side
A payments orchestration platform that connects one API to many processors, payout, fraud and vault providers, with routing, retries and reconciliation.
Software for wallet providers and banks to offer Interledger payments and Open Payments APIs to their account holders.
Self-hosting a PCI-scoped payment system is a serious operational and compliance burden.
Interledger adoption is still small, and current releases are marked beta.
Production-ready
Usable
Self-hosted server and cloud service
Self-hosted server
Rust, PostgreSQL and Redis
TypeScript, Node.js and PostgreSQL
Open source, Apache-2.0 (permissive) (both)
You can build it into a product you sell, as long as you keep its copyright notice. (both)
46k GitHub stars
360 GitHub stars
Established: started 4 years ago, latest release v1.129.0.
Established: started 5 years ago, latest release v2.4.2-beta.
Other comparisons
More payment orchestration platforms
Both sides were judged on 2026-11-03 from each project's README and GitHub data. License, age and popularity lines are worked out directly.