> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/workflows/vault/deployment-models.md).

# Vault Deployment Models

Choose the right Vault deployment model based on your hosting preference and PCI compliance posture

Juspay Hyperswitch supports multiple vault deployment models to match your PCI profile and infrastructure preferences. The table below summarizes each option; click a row to read the full integration guide.

**Deployment Model: Standalone Vaulting Service**

<table><thead><tr><th width="200">Vault Options</th><th width="200">PCI Ownership / Scope</th><th>Example Use Case</th></tr></thead><tbody><tr><td><a href="/integration-guide/workflows/vault/deployment-models/vault-standalone-saas-vault-pci.md">SaaS Hyperswitch Vault</a></td><td>Merchant PCI Environment</td><td>Financial institutions requiring full data sovereignty and PCI control with raw payment method responses</td></tr><tr><td><a href="/integration-guide/workflows/vault/deployment-models/vault-standalone-saas-vault-non-pci.md">SaaS Hyperswitch Vault</a></td><td>Non PCI Scope</td><td>Merchants wanting to avoid PCI scope while maintaining existing PSP relationships via Proxy API</td></tr><tr><td><a href="/integration-guide/workflows/vault/deployment-models/connect-external-vaults-to-hyperswitch-orchestration.md">Third-Party Vault</a></td><td>Merchant PCI Environment</td><td>Merchants already using third-party vault providers like VGS, TokenEx, or similar services</td></tr></tbody></table>

**Deployment Model: Self-Hosted Payments Orchestrator with Vaulting Service**

| Vault Options                                                                                                                                 | PCI Ownership / Scope | Example Use Case                                                                  |
| --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | --------------------------------------------------------------------------------- |
| [Self-Hosted Hyperswitch Vault](/integration-guide/workflows/vault/deployment-models/self-hosted-and-in-house-pci.md)                         | PCI Environment       | Large enterprises requiring full control over both orchestration and payment data |
| [SaaS Hyperswitch Vault](/integration-guide/workflows/vault/deployment-models/self-hosted-orchestration-with-saas-vault.md)                   | Non-PCI               | Mid-size merchants needing orchestration flexibility without PCI burden           |
| [Third-Party Vault](/integration-guide/workflows/vault/deployment-models/self-hosted-orchestration-with-external-or-third-party-pci-vault.md) | Non-PCI               | Businesses with existing vault investments (VGS, TokenEx) adding orchestration    |

**Deployment Model: SaaS Payments Orchestrator with Vaulting Service**

| Vault Options                                                                                                          | PCI Ownership / Scope                | Example Use Case                                                         |
| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------------------ |
| [SaaS Hyperswitch Vault](/integration-guide/workflows/vault/deployment-models/saas-orchestration-with-juspay-vault.md) | Managed by Hyperswitch               | Growing businesses seeking fully managed payment infrastructure          |
| [Third-Party Vault](/integration-guide/workflows/vault/deployment-models/saas-orchestration-with-third-party-vault.md) | Shared / External PCI Responsibility | SaaS companies with compliance requirements for specific vault providers |

<div align="center"><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-70cb35777c6a3d1e1f6f72b4fa66ac525c62e7a7%2Fvault-external-vaults.png?alt=media" alt=""></div>

All deployment models share the same `payment_method_id` token standard and are compatible with the [Vault-Then-Pay](/integration-guide/payment-suite/payment-method-card.md) payment flow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integration-guide/workflows/vault/deployment-models.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.