> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/anatomy-of-an-integration.md).

# Anatomy of an Integration

A more technical look into the structure of Pandium and a deeper dive into the workings of how integrations are hosted and run on our platform.

![We handle all the devops while you focus on the App](https://4017407078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MfJn-9R_dn6dvcGNcdk%2Fuploads%2FJalCZmPBSkwKheG0J149%2FPlatform%20Diagram%20DRAFT%20\(1\).png?alt=media\&token=40d60d4f-07f5-4343-bec8-6aac385016da)

On Pandium, integrations are constructed as a simple Posix compliant [command line interface](https://en.wikipedia.org/wiki/Command-line_interface) application (CLI). The CLI should read tenant configuration and connector secrets from [environment variables](/getting-started/anatomy-of-an-integration/environment-variables.md). Any logs you wish to display to your end users should be written to [`stderr`](/getting-started/anatomy-of-an-integration/environment-variables/stderr.md).

One can pass information to the next run by writing a json encoded string to [`stdout`](/getting-started/anatomy-of-an-integration/environment-variables/stdout.md). On the next run it will be injected in as an environment variable named`PAN_CTX_LAST_RUN_STDOUT` or `PAN_CTX_LAST_SUCESSFUL_RUN_STDOUT.`


---

# 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.pandium.com/getting-started/anatomy-of-an-integration.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.