ADR-001: Hyperswitch self-host vs Juspay-hosted
ADR-001: Hyperswitch self-host vs Juspay-hosted
Status
Accepted (2026-05-28)
Context
Hyperswitch ships open-source under Apache-2.0; Juspay also offers a managed/hosted tier with the same code plus operational support. mvs-pay must choose where to run.
Decision
Self-host the open-source code on EKS. We never use Juspay’s managed tier or paid features.
Consequences
- Full control over routing config, GSM rules, decision-engine deployment.
- Smart Retries enablement is self-serve (no Juspay support handshake).
- Operational burden: we own the upgrade cadence, DR, scaling.
- PCI scope: card-vault is in our environment; we own the AOC.
Alternatives considered
- Juspay-hosted: drops most operational burden onto Juspay. Rejected because it would shift the trust boundary off our infrastructure and limit features (e.g., Smart Retries enablement requires their support).