> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/faq/cloud-platforms.md).

# Cloud Platforms

Common questions about cloud support, data residency, and infrastructure architecture in Tessell.

| Platform                                       | Topics covered                                                                                                    |
| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [Azure](/tessell/faq/cloud-platforms/azure.md) | Infrastructure, certifications, Zero Data Loss, HA/DR, RBI compliance, Azure data service integrations, migration |
| [AWS](/tessell/faq/cloud-platforms/aws.md)     | Infrastructure, certifications, HA/DR, FSx for NetApp ONTAP                                                       |

***

### Q: Which public clouds does Tessell support?

**A:** Tessell is a **cloud-neutral** service. Database services can be hosted on:

* **AWS** (Amazon Web Services)
* **Azure** (Microsoft Azure)
* **GCP** (Google Cloud Platform)

All four relational engines (Oracle, PostgreSQL, MySQL, SQL Server) are available on all three clouds. Regional availability details are in [Supported Cloud Regions](/tessell/getting-started/supported_clouds.md).

***

### Q: Where are the actual database servers hosted — in Tessell's account or mine?

**A:** It depends on your deployment option (see [Deployment Options](/tessell/getting-started/deployment.md)):

| Deployment option                                                 | Where database VMs and storage live                                                                                                              |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Professional**, **Business**, **Virtual Private Tessell (VPT)** | Tessell's cloud account — Tessell owns and manages the underlying cloud resources                                                                |
| **VPT @ Customer**                                                | Your own cloud account — you own the subscription; Tessell's control plane connects in to manage provisioning, patching, backups, and monitoring |

VPT @ Customer is the preferred option for organisations with strict data residency or compliance requirements, because data never leaves your own cloud boundary.

***

### Q: Why does Tessell attach multiple disks to a database server?

**A:** Tessell uses separate disks for:

* **Data** — the primary database files
* **Logs** — transaction/redo logs (separate to prevent log I/O from competing with data I/O)
* **Backups** — local backup staging

This disk separation is a key reason Tessell can offer comparatively very high IOPS — each disk type is tuned independently, and I/O contention between data, log, and backup operations is eliminated.


---

# 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.tessell.com/tessell/faq/cloud-platforms.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.