> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/data-testing/cloud-managed-data-contracts.md).
# Cloud-managed Data Contracts
Cloud-managed Data Contracts let you define and manage expectations for your data directly in the Soda Cloud UI.
This approach is perfect for data analysts, product owners, and business stakeholders who know what “good data” looks like but prefer intuitive tools over code. It’s also ideal for teams that want to move fast, collaborate visually, and integrate seamlessly with engineering workflows when needed.
With Soda Cloud, you can browse datasets, add quality rules, test and publish contracts, and set up scheduled or on-demand verification. All from your browser.
## Why Cloud-managed?
* **Faster time to value** – no setup required
* **Accessible to everyone** – empower domain experts, not just engineers
* **Built for collaboration** – share, comment, and propose changes in a shared UI
* **Easily operationalized** – schedule tests and trigger verifications programmatically
Cloud-managed contracts are a powerful way to bring your organization together around trusted data.
## Prerequisites
Before creating contracts in Soda Cloud, make sure:
* You have a **Soda Cloud account**
* You have access to an organization in Soda Cloud
* You have connected at least one **data source** via a Soda Runner [Via Soda Cloud](/onboard-data-sources-and-datasets/onboard-datasets-on-soda-cloud.md)
***
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/reference/documentation-access-and-licensing.md).
If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.soda.io/data-testing/cloud-managed-data-contracts.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.
