> 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/developer-tools/larky.md).

# VGS Compute

VGS Compute enables organizations to securely process, transform, and validate sensitive payloads in transit using Pythonic syntax.

VGS Compute has been used extensively by enterprise customers to perform custom cryptographic operations, payload transformations, and policy enforcement in real time.

VGS Compute combines programmability with isolation and security, enabling organizations to adapt to any internal or external integration requirement without compromising security, compliance, or code ownership.

Powered by the VGS-maintained [starlarky runtime](https://github.com/verygoodsecurity/starlarky), VGS Compute allows you to inject programmable logic directly into your data flows, executing customer-written code on data as it passes through the VGS Secure Data proxies without ever exposing the underlying sensitive values.


---

# 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/developer-tools/larky.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.
