When the free Community Edition is enough and when Enterprise is worth it
A team that wants to self-host Hyperswitch and keep full ownership of the stack gets the same core orchestration features in both editions, so the decision turns on three things: support, uptime ownership and PCI operating responsibility. According to the Hyperswitch pricing comparison, both self-hosted editions include 90+ payment integrations, the unified checkout SDK, payout orchestration, the Control Center, fraud orchestration, the vault, intelligent routing, customizable 3DS authentication and alternative payment methods. Community Edition is sufficient when you already have strong in-house platform engineering and compliance staff who can run Router, Scheduler, PostgreSQL and Redis, own the uptime of that stack, and operate the PCI DSS and ISO 27001:2022 controls end to end, and when community support through the public Slack channel and GitHub discussions is acceptable for your incident model. Confirm that your staff can handle on-call duty and vendor-independent upgrades before you rely on that path.
Enterprise is worth pricing when you need contractual commitments the community channel cannot give you. The Hyperswitch pricing page lists SLA-driven technical support, a dedicated key account manager and fast-lane prioritization of feature requests for Enterprise Edition, and it places uptime and the PCI DSS 4.0 and ISO 27001:2022 compliant stack under Juspay's support in that edition. Enterprise makes sense if your board, regulator or card scheme expects a named escalation path, if your team cannot absorb payment outages without vendor help, or if you want Juspay's guidance on keeping the compliant stack current. Ask Juspay for the written SLA terms, response commitments and the exact scope of PCI and uptime support before you assume they match your requirements. Hosting costs stay with you in both editions, so the quote should separate licence cost from your own infrastructure spend.
Revenue recovery, cost observability and reconciliation are paid add-ons in both the Community and Enterprise self-hosted editions, so choosing Enterprise does not include them. Price these modules separately in any quote and confirm which ones your roadmap needs, because they are not bundled into either tier.
Which Hyperswitch capabilities both editions include and which cost extra
This table sets the Hyperswitch Community Edition against the Enterprise Edition, row by row, using the vendor's published split on its pricing page. Read the first block to see what you get free in both self-hosted editions, the middle block for paid add-ons that sit outside the base price, and the last block for what changes in support and in who manages uptime and PCI DSS 4.0 and ISO 27001:2022 controls. The main takeaway is that the feature set is largely shared, so the decision turns mostly on support, operating responsibility and add-on needs, and add-on pricing is not published, so you must request it in writing.
| Capability | Community Edition | Enterprise Edition |
|---|---|---|
| 90+ payment integrations | Included, self-hosted | Included, self-hosted |
| Unified checkout SDK | Included, self-hosted | Included, self-hosted |
| Payout orchestration | Included, self-hosted | Included, self-hosted |
| Control Center and fraud orchestration | Included, self-hosted | Included, self-hosted |
| Vault, intelligent routing, customizable 3DS and alternative payment methods | Included, self-hosted | Included, self-hosted |
| Revenue recovery, cost observability and reconciliation | Paid add-on, price not published | Paid add-on, price not published |
| SLA-driven technical support and dedicated key account manager | Not included, community channels only | Included per vendor pricing page |
| Uptime and PCI DSS 4.0 and ISO 27001:2022 stack | Self-managed by your team | Supported by Juspay |
What the free Community Edition gives a self-hosting team
The Community Edition is the free self-hosted option for teams that run their own payments stack and manage compliance end to end. Its core is the Rust app server, which handles routing, retries and vaulting, and sits alongside the Router and Scheduler services. Router serves payment traffic, while Scheduler runs its Producer and Consumer roles against a queue. Both services depend on PostgreSQL with a master and replica setup, and Redis handles caching and the scheduler queue. The Control Center merchant dashboard and the client SDKs for web, Android, iOS, React Native and Flutter ship with the edition. Deployment runs through Helm charts on Kubernetes, with guides for Minikube, AWS, GCP and Azure, so the platform team owns the cluster, the database tier and the Redis tier from day one.
The pricing page lists the orchestration features that both self-hosted editions include, among them intelligent routing, the vault, customizable 3DS authentication and fraud orchestration. Revenue recovery, cost observability and reconciliation are paid add-ons in both editions, so a Community deployment does not include them by default. Support comes through the public Slack channel and GitHub discussions at no charge. That suits a team with strong Kubernetes, PostgreSQL and payments engineering skills that can diagnose issues from logs, configuration and community answers, and that accepts no contractual response time. A team that must show an SLA to its own regulators, or that expects to own uptime and PCI DSS 4.0 controls with vendor backing, should confirm with Juspay exactly what the Enterprise support model covers before it commits to the free path.
What Enterprise adds for typical regulated buyers
The Enterprise Edition does not change the orchestration code you run. It adds a contractual layer around the same self-hosted stack: support commitments, account ownership, roadmap influence, and Juspay's help with uptime and the PCI DSS and ISO 27001 posture. Each card below describes what that layer covers and what your team still owns.
SLA-driven technical support
Enterprise Edition adds SLA-driven technical support, where Community Edition relies on the public Slack channel and GitHub discussions. This matters when a bank, payment service provider or insurer must show its regulator or board a contractual support path with defined response expectations. Ask Juspay for the SLA document in writing, including severity levels, response targets, hours of coverage and what counts as a covered incident. Your team still owns the triage that decides whether an incident is a Hyperswitch fault or a connector or network fault.
Dedicated key account manager
Enterprise Edition includes a dedicated key account manager. This helps when several internal teams, such as payments operations, risk and treasury, need one named counterpart to route escalations and track open requests. Confirm in the contract whether the account manager is a commercial contact only or also coordinates technical escalations, and whether the role changes if your account moves between sales and support. Your team still owns the internal ownership map that tells the account manager who decides on priorities.
Fast-lane feature request prioritization
Enterprise Edition gives fast-lane prioritization of feature requests, while Community Edition requests go through the public community. This matters when a connector, routing rule or reporting gap blocks a launch or a regulatory deadline. Ask how a request is scored, whether prioritization carries any commitment on delivery dates, and whether the change lands in the upstream codebase or only in a patch for your deployment. Your team still owns the test plan and regression checks for any change you take into production.
Juspay help with uptime
On the pricing page, uptime is self-managed in Community Edition and supported by Juspay in Enterprise Edition. This matters when a merchant's checkout revenue depends on the orchestration layer staying available across Router, Scheduler, PostgreSQL and Redis. Ask what Juspay monitors, what they operate versus what they advise on, and how availability targets are measured and reported. Your team still owns the hosting, capacity planning, and the cloud or data center failover design, since hosting costs are not covered in either self-hosted edition.
Juspay support for PCI DSS and ISO posture
Enterprise Edition includes Juspay support for the PCI DSS 4.0 and ISO 27001:2022 compliant stack, where Community Edition leaves that work to you. This matters most when you run the native in-house vault, because the Hyperswitch docs state that the merchant is fully responsible for PCI DSS certification and data handling in that model. Ask Juspay exactly which controls and evidence they provide, which parts stay in your scope, and whether they support your assessor. Your team still owns the PCI DSS assessment itself, since only a qualified assessor or certification body can issue that outcome, not the vendor.
Expert guidance on the self-hosted stack
Enterprise Edition is aimed at businesses that keep full ownership of the stack but want Hyperswitch's expert guidance. This suits teams that will run Hyperswitch themselves yet lack in-house experience with Rust services, the card vault, or the Control Center's OpenID Connect-only single sign-on. Ask which guidance is included in the contract, such as architecture reviews, upgrade planning or configuration checks, and what is excluded. Your team still owns the operating runbooks, the change approvals, and the decision to accept or defer each upgrade.
Who carries PCI DSS responsibility in each edition
When you run the native Hyperswitch Vault inside your own infrastructure, your organization stores cardholder data in its own environment. The Hyperswitch documentation states that the merchant is fully responsible for PCI DSS certification and data handling in this self-hosted, in-house PCI model. That responsibility applies whichever edition you run, because the vault sits in your scope.
- Certification ownership: You own the PCI DSS assessment and the attestation that results from it, including the evidence that your environment meets each requirement.
- Hosting controls: Network segmentation, key handling, access control, logging and the hardening of the cluster, databases and Redis all fall to your team.
- Uptime and patching: The Community Edition page places uptime and the PCI DSS 4.0 compliant stack under self-managed operation, so your staff run the patch and recovery cycle.
- Enterprise effect: Enterprise support adds SLA-backed technical help and a key account manager, which can shorten troubleshooting. It does not change who is certified.
- Scope creep: Every system that touches card data, including Control Center access paths, joins your assessment.
Confirm with Juspay, in writing, exactly which PCI-related help the Enterprise agreement covers before you assume any of it reduces your assessor's workload.
In the self-hosted orchestration model with an external PCI vault provider, such as VGS or Tokenex, card data is held by that provider. Hyperswitch orchestrates payments and tokens while the external vault carries the cardholder data environment. Your PCI scope narrows, but it does not disappear, because your systems still handle tokens, payment flows and the integration between services.
- Shared responsibility: The vault provider's attestation covers the card storage environment, while your organization documents how your own systems connect to it.
- Contract review: Confirm the provider's current attestation, the responsibility matrix and the data flows you are relying on.
- Hyperswitch services: Orchestration, routing and the Control Center remain in your environment, so their hosting and access controls still count toward your scope.
- Edition difference: Both editions can use this model. Enterprise support may help with integration questions, but it does not replace the vault provider's attestation.
- Data flow mapping: Document every place a token or payment record moves, since your assessor will ask for it.
Ask the vault provider for its current attestation and responsibility matrix, and ask Juspay what its support covers in this architecture.
In the self-hosted orchestration model with the SaaS Hyperswitch Vault, you run the orchestration stack yourself while card storage happens in Juspay's hosted vault. This narrows the cardholder data work you carry, but the arrangement depends on the terms of the service, so you need the exact responsibility split in writing before you rely on it.
- Responsibility boundary: Obtain the written split between your organization and Juspay for card storage, key management and vault availability.
- Evidence: Request the current compliance documentation Juspay can provide for the hosted vault and confirm its scope and date.
- Your stack: Hosting, Router and Scheduler, PostgreSQL, Redis and Control Center remain your responsibility, along with their hardening.
- Enterprise value: Enterprise adds SLA-backed support and fast-lane prioritization, which can matter if your team needs vendor help during incidents involving the vault connection.
- Hosting costs: The pricing page states that hosting costs are not covered in either self-hosted edition, so budget for your own infrastructure in this model too.
Get the Juspay responsibility matrix and the scope of its vault attestation in writing, and confirm which edition's agreement includes the support terms you need.
How Control Center sign-in limits both editions
The main point for identity planning is that the Hyperswitch Control Center supports single sign-on through OpenID Connect only. SAML is not supported, there is no just-in-time or SCIM provisioning, and users must be invited into Hyperswitch before they can sign in. Roles are managed inside Hyperswitch rather than mapped from your identity provider's groups. These limits are documented in the Hyperswitch SSO guide for the Control Center, and they describe the dashboard that both the Community Edition and the Enterprise Edition ship with. Neither edition's pricing page lists an identity feature that removes them, so a paid tier should not be assumed to change this behavior.
For a team with an existing SAML-based identity provider, this has practical consequences. Someone must maintain a list of Control Center users and their roles outside the directory, and offboarding is a manual step: an account removed in your directory is not removed from Hyperswitch automatically. Access reviews for the merchant dashboard therefore have to be run against Hyperswitch itself, not against your identity governance tooling. Teams that need SCIM-driven lifecycle management or group-based role assignment should treat this as a gap to plan for, either with a manual control, a scheduled export and review, or a different access pattern for the dashboard.
Before you commit to an identity design, confirm current behavior for your edition with Juspay, ideally in writing. Ask whether SAML, SCIM or group-to-role mapping is on the roadmap, whether the OpenID Connect configuration is the same in the Community Edition and the Enterprise Edition, and how Juspay supports you if an OIDC issue blocks sign-in during an incident. The Hyperswitch SSO configuration guide is the starting point for your own test environment, and the result should be recorded as part of your access control evidence.
License, support and update terms for each edition
Community and Enterprise share an Apache 2.0 codebase, so the real difference is what Juspay commits to in writing. The cards below separate the license you inherit, the positioning of each edition, the support channels available today, and the terms you must confirm before you commit.
Apache 2.0 open source repository
The Hyperswitch repository is licensed under Apache 2.0 and is maintained by Juspay. Your right to run, modify and redistribute the code comes from that license, not from the edition you buy. Check that your internal changes, such as custom connectors or routing logic, stay within the license terms you accept, and have your legal team confirm how the Apache 2.0 grant interacts with any Enterprise agreement you sign.
Community Edition for self-managed stacks
The free Self-Host Community Edition is positioned for businesses that run their own payments stack and manage compliance end to end. Uptime, the PCI DSS 4.0 and ISO 27001:2022 compliant stack, and hosting costs sit with your team. Confirm whether your internal staffing can carry on-call response, security patching and PCI evidence collection before choosing this edition.
Enterprise Edition priced through sales
The Self-Host Enterprise Edition is priced through Juspay's sales team and is aimed at businesses that keep full ownership of the stack but want Hyperswitch's expert guidance. It is not a different codebase you must migrate to. Ask for a written quote that lists exactly which services, reviews and guidance are included, and what happens to pricing as your transaction volume or connector count grows.
Public Slack and GitHub support
Community Edition support runs through the public Slack channel and GitHub discussions at no charge. Responses come from the community and Juspay staff with no contractual response commitment. This is suitable for non-critical questions and development work. For production payment incidents, decide before go-live whether a public channel meets your escalation needs.
Contractual update and support terms
Enterprise Edition adds SLA-driven technical support, a dedicated key account manager and fast-lane prioritization of feature requests. The actual response times, severity definitions, upgrade support and patch windows are contract matters. Request the SLA document, the support hours, the escalation path and the supported release lines in writing, and confirm how long each release line receives security fixes before you sign.
What each edition costs and what drives the total
This table separates the cost components of a self-hosted Hyperswitch stack by edition, showing who is paid, what is one-time or recurring, and what drives each cost. Read it as a checklist for a quote: Community licensing is free, while Enterprise pricing is set through sales and depends on your written scope. The main takeaway is that the licence is rarely the largest line item, because hosting, staff time and integration work apply in both editions.
| Cost component | Community Edition | Enterprise Edition |
|---|---|---|
| Software licence | Free under Apache 2.0 with no published fee | Priced through sales; no price list is published, so ask for a written quote tied to your scope |
| Add-on modules (revenue recovery, cost observability, reconciliation) | Paid add-ons, priced separately from the free edition | Paid add-ons in the Enterprise edition as well; confirm which are included in your quote |
| Hosting and cloud infrastructure | Not covered; you pay your cloud, data center or Kubernetes costs directly | Not covered in either self-hosted edition; budget for it in your own infrastructure |
| Internal staff time for setup and upgrades | Recurring; your team owns upgrades, uptime and PCI DSS compliance | Recurring but reduced where Juspay supports uptime and compliance; confirm the exact scope in writing |
| Support | Free through the public Slack channel and GitHub discussions | SLA-driven technical support and a dedicated key account manager; ask for SLA terms in the quote |
| Integrator or implementation work | One-time: deployment, connector setup and vault design, often billed by a partner such as DeployOpen on a fixed scope | One-time work may overlap with vendor guidance; agree in writing who delivers which task |
| Compliance evidence for PCI DSS | Recurring internal effort; the merchant carries full responsibility for in-house vault models | Juspay support for compliance is listed on the pricing page; confirm what evidence is provided and what remains yours |
Moving from Community to Enterprise, or back
The sequence turns a self-hosted Community Edition stack into an Enterprise engagement with written scope, clear support ownership and a tested upgrade path, so no one discovers a responsibility gap after go-live. Each step ends with a document or check you can point to.
Confirm which add-on modules you need
Your payments and finance leads list the capabilities the stack must deliver, then map each one to a module. Hyperswitch's pricing page lists payment orchestration features, including the 90+ payment integrations, the unified checkout SDK, payout orchestration, the Control Center, fraud orchestration, the vault, intelligent routing, customizable 3DS authentication and alternative payment methods, as included in both self-hosted editions. Revenue recovery, cost observability and reconciliation are listed as paid add-ons in both editions, so these are the modules that change your cost. Done when you have a written list of required modules, each marked included or add-on, and you have confirmed the add-on prices with Juspay sales.
Request an Enterprise scope from Juspay sales
Your procurement or platform lead sends the required module list and your operating assumptions to Juspay sales. The Enterprise Edition is priced through sales, and the pricing page describes it as the option for businesses that keep full ownership of the stack but want Hyperswitch's expert guidance. Ask for a quote that separates the license, each add-on, support tiers and any services hours, and ask what recurs annually and what is one-time. Done when you hold a quote that matches your module list and names the support tier it includes.
Agree support and PCI responsibilities in writing
Legal, security and the platform owner review what Juspay will and will not own. The pricing page states that uptime and the PCI DSS 4.0 and ISO 27001:2022 compliant stack are self-managed in Community Edition and supported by Juspay in Enterprise Edition, and that hosting costs are not covered in either self-hosted edition. Also confirm the vault model: under the self-hosted, in-house PCI model, the Hyperswitch docs state the merchant is fully responsible for PCI DSS certification and data handling. Done when a responsibility matrix, signed off by security and compliance, lists each control area with its owner, and it is attached to the contract.
Plan the channel change and key account contacts
The platform owner moves day-to-day support from the public Slack channel and GitHub discussions, which the pricing page lists as free support for Community Edition, to the SLA-driven support channel and the dedicated key account manager listed for Enterprise Edition. Document who opens tickets, who approves severity levels, who is on call for payments incidents and how feature requests reach Juspay's prioritization path. Done when the escalation runbook names an owner for each role and the Juspay contacts are recorded in your incident tooling.
Test the change on a non-production environment
Your platform engineers deploy the Enterprise build and the add-on modules to a staging environment that mirrors production, including the PostgreSQL primary and replica, Redis, the Router and Scheduler services and the vault configuration. Run your connector test cases, reconciliation runs and a failover exercise against the staging stack. Record any configuration keys, database migrations or Helm chart changes that the move requires. Done when the test report shows all critical payment flows passing and the upgrade runbook has been rehearsed at least once.
Confirm the shared codebase and downgrade constraints
Engineering reviews whether the two editions share one codebase. The public Hyperswitch repository is licensed under Apache 2.0, and the pricing page presents both self-hosted editions as tiers of the same product, but the materials available to this review do not document the edition packaging in detail. Ask Juspay in writing whether Enterprise modules and configuration are compatible with a return to Community Edition, what data migrations a downgrade would require and whether any add-on features must be removed before reverting. Done when Juspay has confirmed the answers in writing and the rollback plan references that confirmation.
Schedule the production cutover with a rollback plan
The release owner schedules the production change after staging sign-off, with the rollback steps from the previous stage attached. Confirm the change window with the support contacts, freeze unrelated deployments and verify backups of PostgreSQL and the vault before cutover. Monitor transaction success rates and routing decisions for the agreed observation period after go-live. Done when the change record shows the rollback was rehearsed, the post-change checks passed and the responsibility matrix matches what was deployed.
Questions buyers ask before choosing an edition
Can a team run Hyperswitch on the Community Edition alone?
Yes, in principle. Juspay's pricing page places the free Self-Host Community Edition with businesses that self-host, run their own payments stack and manage compliance end to end. Both self-hosted editions include 90+ payment integrations, the unified checkout SDK, payout orchestration, the Control Center, fraud orchestration, the vault, intelligent routing, customizable 3DS authentication and alternative payment methods. The real question is whether your team has the platform, security and compliance capacity to own uptime and PCI DSS responsibilities without vendor-backed support. Confirm the support path you will rely on before go-live.
How much operating effort does self-hosting Hyperswitch take?
The effort sits in four areas. Hyperswitch documents Helm charts on Kubernetes, with guides for Minikube, AWS, GCP and Azure. The architecture uses two app services, Router and Scheduler, backed by PostgreSQL with a master and replica setup and by Redis for caching and the scheduler queue. Card data sits in the separate card vault, which the architecture docs describe as built for PCI DSS requirements, and in the in-house PCI model the merchant is fully responsible for PCI DSS certification and data handling. Hosting costs are not covered in either self-hosted edition. Ask Juspay for a sizing review and a list of the components your team must patch, monitor and back up.
What does the Enterprise Edition change for uptime and compliance?
On the pricing page, uptime and the PCI DSS 4.0 and ISO 27001:2022 compliant stack are self-managed in Community Edition and supported by Juspay in Enterprise Edition. Enterprise also adds SLA-driven technical support, a dedicated key account manager and fast-lane prioritization of feature requests. Juspay does not describe these as guarantees in the facts available here, so ask for the SLA terms, the scope of uptime support and the responsibility split for PCI DSS in writing. Your organization still keeps its own compliance obligations, and an independent assessor issues any attestation.
Do I need the paid add-ons such as reconciliation?
Only if your operating model needs them. Revenue recovery, cost observability and reconciliation are listed as paid add-ons in both the Community and Enterprise self-hosted editions, so choosing Enterprise does not include them. Hyperswitch's docs describe these modules, and your finance and operations teams should decide whether they replace an existing reconciliation process or add to it. Ask Juspay which add-ons apply to your edition, how each is priced and whether they run on your own infrastructure.
How long does a Juspay quote take to produce?
Juspay does not publish a turnaround time in the facts available here, so confirm it directly. The Enterprise Edition is priced through sales, and the quote follows from the scope you define: which connectors, modules, support levels and deployment model you need. Prepare your processor list, expected transaction profile, hosting plan and vault choice before the first call so the quote reflects your real requirements.
Can DeployOpen run either Hyperswitch edition for us?
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Hyperswitch, that work can cover deployment, configuration, integration and ongoing support in your environment. DeployOpen is not an official partner or reseller of Juspay unless a supplied fact says so, and it does not issue audit reports or certifications. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts, and ongoing support is available as a retainer. Juspay remains the source for Enterprise Edition terms.
What should we confirm with Juspay before choosing an edition?
Get written answers on five points. First, the SLA terms and what uptime support covers in Enterprise. Second, the PCI DSS responsibility split for your chosen vault model. Third, which connectors and modules are included in your edition, and which are paid add-ons. Fourth, the feature prioritization process and what fast-lane access means in practice. Fifth, the support path during an incident, including who responds and through which channel. Also confirm the Control Center sign-in model: the docs state SSO uses OpenID Connect only, with no SAML, JIT or SCIM provisioning, and roles are managed in Hyperswitch rather than mapped from your identity provider.
When a self-hosted team should bring in outside help
A self-hosted team should consider outside help when the work sits between the platform and its surroundings: connector integration, the vault model, identity wiring and compliance evidence. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades and documents self-hosted open-source platforms inside the client's own cloud accounts, data centers or air-gapped networks. That scope applies whichever edition you run. DeployOpen is not a Juspay partner, reseller or certified provider unless Juspay states otherwise, so confirm the relationship directly before you assume any vendor-side access or escalation path. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts, and ongoing support is available as a retainer.
Outside help complements either edition most clearly in three places. The first is the vault decision: the Hyperswitch docs describe three self-hosted vault models, and choosing between the native in-house PCI vault, an external PCI vault provider such as VGS or Tokenex, or the SaaS Hyperswitch Vault changes who carries PCI DSS responsibility. The second is the Control Center: SSO runs on OpenID Connect only, with no SAML, JIT or SCIM provisioning, and roles are managed in Hyperswitch, so plan the invitation and role process with your identity team early. The third is evidence. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. Ask your qualified assessor which artifacts they expect before you commission any preparation work.
How DeployOpen scopes and delivers Hyperswitch work
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For Hyperswitch, that means agreeing in writing which edition, modules and responsibilities the engagement covers before any work starts, so the choice between Community Edition and Enterprise Edition rests on a defined scope rather than assumptions.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope states which Hyperswitch edition, modules and payment connectors are included.
- Scope documents who owns uptime, PCI DSS evidence and hosting for each component.
- Ask for a quote that follows directly from that written scope, since no price list is published.
How we build
- Deployment onto your chosen cloud account, data center or air-gapped network, using the documented Kubernetes approach.
- Integration of the Control Center with your identity provider, confirming the OpenID Connect limits first.
- Configuration of the vault model you select, with the PCI DSS responsibilities mapped in writing.
- Security testing of the deployed stack and its APIs, reported against the agreed scope.
How we hand over
- Documentation of the architecture, configuration, runbooks and the responsibilities that stay with your team.
- Backup and restore procedures tested against the agreed scope before handover.
- Evidence and control records prepared for your compliance assessor, who issues any report or certification.
- A clear split between work delivered and work your team must run after handover.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped separately from the build.
- Retainer scope should state which Hyperswitch releases are covered and how upgrades are tested first.
- Ask whether support covers Juspay's Enterprise Edition services or only the DeployOpen-delivered stack.
- Confirm response expectations and escalation paths in the written retainer before signing.
