> For the complete documentation index, see [llms.txt](https://developer.vario-software.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.vario-software.de/documentation/apps/introduction.md).

# Introduction

A **VARIO Cloud App** is an external web application that you build and host yourself. It is integrated into VARIO-Cloud in three ways:

* **UI integration**: VARIO Cloud embeds your App inside an iframe at defined integration points (for example, as a navigation entry or dialog). To the end user, the App appears as part of the ERP UI.
* **Data integration via REST API**: Your App talks to the VARIO Cloud backend using the public REST API (secured with OAuth2) to read and update ERP data.
* **Webhooks**: You can send and receive Events triggered by the Cloud App or via Webhooks

The App does **not** run inside VARIO Cloud itself. Instead, it is a self-hosted service that connects to VARIO Cloud through iframe-based UI integration and the REST API.

### App types: private vs public

VARIO Cloud supports **private Apps** and **public Apps**. Every App starts out private — public is a status an existing App is promoted to, not a separate kind of project.

#### Private Apps

Private Apps are built for a single customer or organization.

* Any customer on the **Enterprise plan** can develop and add private Apps.
* Private Apps are not listed in the App Store.

#### Public Apps (App-Store)

Public Apps are available to all customers via the [**VARIO App-Store**](https://app-store.vario-software.de/).

You do not need our approval to get started. First, build and run your App as a private App, keeping the [App Store Guidelines](https://developer.vario-software.de/app-store-guidelines/) in mind. When it is ready for a wider audience, follow these steps:

1. **Contact us** with your finished private App.
2. **Sign the App-Store contract** and [become an official App-Developer](https://www.vario-software.de/partner/app-partner/)**.**
3. **Review process** — we review the App, and on success it is published as a public App in the App Store.

{% hint style="info" %}
Because the path always starts private, nothing about the development work changes when you plan to publish later. Build it the normal way — see [Create an App](/documentation/apps/create-an-app.md) and the [Quickstart](/documentation/apps/quickstart.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.vario-software.de/documentation/apps/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.