Managed Hyperswitch Hosting — production-ready from $16 a month
Open-source payments switch that routes transactions across multiple payment processors. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Hyperswitch, no lock-in.
Hyperswitch on ManageStacks is an open-source payments switch written in Rust that connects your checkout to multiple payment processors through one API, deployed to your own AWS, Azure, or GCP region with flat per-app pricing from $16 a month ($30 on the Standard production plan). It suits merchants and fintech teams wanting processor flexibility without a single-gateway lock-in.
What does Hyperswitch do, and why do teams deploy it?
Hyperswitch is a payments orchestration layer developed by Juspay and written primarily in Rust. Rather than integrating each payment processor separately, an application calls one unified API, and Hyperswitch routes the transaction to a connected processor. Routing rules let merchants choose processors by criteria such as payment method, amount, or availability, and retries can fall back to another connector when one fails. It also provides a control center for managing connectors, viewing payments, and handling refunds. Because it processes sensitive payment flows, running it in your own cloud account keeps infrastructure and logs under your control.
- Unified payments API across many payment processors
- Rule-based routing between connected processors
- Fallback retries through an alternate connector on failure
- Control center for payments, refunds, and connectors
- Support for cards and local payment methods
- Webhook events for payment status updates
Open-source payments switch that routes transactions across multiple payment processors
Hyperswitch as a self-hosted alternative to Stripe, Adyen and Spreedly
Instead of paying per-seat fees to a SaaS vendor, teams self-host Hyperswitch to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed Hyperswitch hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting Hyperswitch the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Hyperswitch at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Hyperswitch run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Hyperswitch in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Hyperswitch on ManageStacks
What is Hyperswitch on ManageStacks?
Hyperswitch is an open-source payments switch that lets one integration talk to several payment processors. ManageStacks deploys it in your own cloud account so the orchestration layer runs on infrastructure you control.
How does Hyperswitch compare to Stripe?
Stripe is a proprietary payment processor with its own gateway and pricing. Hyperswitch is an orchestration layer that sits in front of processors, which can include Stripe itself. It adds routing and fallback choices instead of replacing the processors.
Can Hyperswitch route payments to different processors?
Yes. You configure connectors for the processors you hold accounts with and define routing rules to choose between them. If a payment attempt fails, you can retry through another connector according to your configuration.
Do I still need accounts with payment processors?
Yes. Hyperswitch does not process money by itself; you bring your own processor accounts and credentials. Those credentials are stored in your own deployment, and contracts and fees remain between you and each processor.
How should I think about security for a payments app?
Payment infrastructure carries compliance obligations that depend on your setup. Running Hyperswitch in your own cloud gives you control over networking and access, but you should review your own compliance requirements with your processors and advisers.
Other erp & business tools on ManageStacks
WooCommerce
Customizable open-source eCommerce plugin that turns WordPress into an online store
Magento
Open-source eCommerce software for building a custom online store from the ground up
ERPNext
Full-featured open-source ERP system
Odoo
Suite of business management applications
Run Hyperswitch without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $16/mo.