> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/vault/readme.md). # Product Overview The VGS Secure Data Suite provides a unified framework for collecting, storing, and exchanging sensitive information safely across your applications and infrastructure. At its core, the VGS Vault securely holds sensitive data and replaces it with VGS Aliases. Aliases are non-sensitive representations that preserve format and functionality while eliminating storage risk to the organization. Data can be transmitted securely through multiple ingress and egress channels and protocols, including the [**HTTPS Proxies**](/vault/http-proxy.md), [**Batch File Transmission Tools**,](/vault/batch-file-transmission.md) and the [**TCP Proxy**](/vault/iso-proxy.md). The platform also allows organizations to perform complex modifications and cryptographic operations to sensitive data in transit using [**VGS Compute**](/vault/developer-tools/larky.md)**.** Together, these tools enable an organization to operate on sensitive data such as payment credentials, social security numbers, passport numbers, passwords, and any other information that the organization deems sensitive. --- # 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.verygoodsecurity.com/vault/readme.md?ask=&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.