> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/readme/secoda-as-an-admin/deployment-options.md).

# Deployment options

Check out the deployment options for setting up Secoda.

Secoda offers three main deployment options depending on your organization's needs.

## **Multi-Tenant Cloud**

You can select from the following regions for hosting our multi-tenant Cloud version of the app:

1. US (us-east-1)
2. EU (eu-central-1)
3. APAC (ap-southeast-1)

With our multi-tenant setup (and most software SaaS), organization's application data is stored on a shared database. All application data is stored within a private VPC and is separated at the software-level using row-level security, global checks, and automated tests to ensure data is securely separated.

## **Single-Tenant Cloud**

A single-tenant Cloud set up is an isolated version of the app in it's own VPC in the region of your choice. The following holds true for this option:

* All of your organization's application data exists in it's own database that is not shared with any other Secoda customers.
* The Secoda team manages all application upgrades and infrastructure changes.
* You can select your own custom URL, i.e, <https://test.secoda.co>.

This provides stronger security guarantees, dedicated resources, and can offer lower latency by configuration in a nearby AWS region.

## [**Self-Hosted**](/enterprise/self-hosted-secoda.md) (On-Premise)

There are three options for self-hosting Secoda:

1. [AWS ECS](https://github.com/secoda/terraform-aws-secoda) (recommended)
2. [Docker Compose](https://github.com/secoda/docker-compose)
3. [Kubernetes](https://github.com/secoda/helm)

{% hint style="info" %}
The self-hosted options require DevOps support from the customer and Secoda which can result in higher costs.
{% 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.secoda.co/readme/secoda-as-an-admin/deployment-options.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.