> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-developers/reference/hosted-apps.md). # Hosted Apps The Hosted Apps contract, covering the manifest, the runtime, the bundle rules and the limits {% hint style="info" %} **Private Preview:** Hosted Apps is available to selected accounts during its Private Preview. To request access, contact your CARTO representative. {% endhint %} **Hosted Apps** serves a static frontend under `/app//`, to the signed-in users of your organization that the app is shared with. The app reads the user's own access token from `./carto-info.json` and calls the CARTO APIs directly. These pages describe what CARTO reads when you deploy an app, what it serves at runtime, and the rules and limits it enforces. To get started, see [Hosting your first application](/carto-for-developers/quickstart/hosting-your-first-application.md) and the [Hosting your application in CARTO](/carto-for-developers/guides/build-a-hosted-application.md) guide. For how hosting fits with the rest of CARTO for Developers, see [Hosted Apps](/carto-for-developers/key-concepts/hosting-your-application.md) in Key concepts. For every command and flag, see the [`app` command reference](/carto-for-agents/cli/command-reference/app.md). | Page | Contents | | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | [App manifest (`carto.json`)](/carto-for-developers/reference/hosted-apps/app-manifest.md) | Every field of the manifest: connections, Named Sources and declared APIs. | | [Runtime and authentication](/carto-for-developers/reference/hosted-apps/runtime-and-authentication.md) | How an app is opened, the `carto-info.json` contract, sessions, sharing and versions. | | [Bundle requirements and limits](/carto-for-developers/reference/hosted-apps/bundle-requirements-and-limits.md) | What a valid bundle looks like, the enforced limits, and the response headers and CSP. | | [Limitations](/carto-for-developers/reference/hosted-apps/limitations.md) | What is and is not supported. | ## Requirements | Requirement | Detail | | ----------- | ------------------------------------------------------------------------------------------------------------ | | CARTO CLI | v0.12.0 or later. Apps are deployed with the CLI; see [Installation](/carto-for-agents/cli/installation.md). | | Account | Hosted Apps enabled for your account (Private Preview). | | Users | A CARTO user in the same organization. There is no anonymous access. | ## Glossary | Term | Meaning | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **slug** | The app's identifier in its URL, unique in your organization. It is the `` in `/app//`. | | **bundle** | The directory of built files that CARTO serves, with `index.html` at its root. | | **version** | One deploy of the bundle. Every deploy creates a version; deployed versions cannot be changed, and exactly one of them is active. | | **manifest** | `carto.json` at the root of the bundle. Read when you deploy, and never served. | | **`carto-info.json`** | The file CARTO serves to each user next to the app, with their access token and the API base URL. A reserved filename. | | **Named Source** | A parametrized SQL query stored in CARTO and run by name, so the SQL is not sent to the browser. A hosted app's are registered as `_`. | | **sharing** | Who can open the app: your organization, or specific groups and users. An app that is not shared is private to its owner. | | **owner** | The user who deployed the app. Only the owner can redeploy, share, roll back or delete it. | --- # 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.carto.com/carto-for-developers/reference/hosted-apps.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.