> 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/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/readme/what-companies-use-pandium-for.md).

# What Companies Use Pandium For

* Launch highly configurable, reusable, and dynamic native integrations.
* Automate release management. [Release management](https://docs.pandium.com/quick-start/key-terminology#release) options and versioning within the platform make it easy to update your integrations and track changes.
* Set customer-specific deployment without having to build the infrastructure to enable and manage this. 
* Give customers the ability to build custom user experiences with the [Pandium API](https://docs.pandium.com/reference/pandium-api).
* Deploy integrations to specific customers or empower clients to discover and install integrations via an embedded In-App Marketplace UI in your app. 
* Showcase your ecosystem of integrations and partners to customers, partners, and prospects via our In-App Marketplace and Public Gallery products. 
* Give customers more visibility into their integrations and enable them to install apps, manage configurations, define sync schedules, and view logs via a customizable marketplace experience.
* Manage relationships with technology partners. Invite partners to submit integrations, marketing materials, and documentation for their tile within your marketplace.


---

# 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/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/readme/what-companies-use-pandium-for.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.