> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/cloud.md).

# Cloud

Use Jet Admin's hosted services while managing your app configuration, users, and connected resources.

## Prepare the app

1. Identify the database or API used by each environment.
2. Configure the required connections and appropriately scoped credentials.
3. Set up user membership, authentication, and permissions.
4. Test representative reads, writes, and denied actions.
5. [Publish](/jet-bridge-deployment/publish-your-app.md) and [verify](/jet-bridge-deployment/publish-your-app/verify-a-release.md) the intended app version.

## Review data handling

Distinguish source data storage from request processing, logs, exports, uploaded files, and AI inputs. Connecting an external database does not by itself establish that no data is processed by other services.

Review the configured resource and feature behavior for your app. See [Security and data handling](/access-and-sharing/data-privacy-and-security.md) for the questions to resolve, including Jet Tables and recovery scope.

## Operational checks

Confirm that the intended users can reach the app and that the required resources are reachable through the configured connection path. Assign an owner for credential rotation, membership review, and resource recovery.

For connection failures, use [Diagnose resource and deployment errors](/jet-bridge-deployment/logs-and-troubleshooting/resource-and-deployment-errors.md). If you need to operate a bridge or the application services yourself, compare [deployment options](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises.md).


---

# 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.jetadmin.io/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/cloud.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.