> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/v1/dataos-operator/choosing-between-instance-and-tenant.md).

# Choosing between an Instance and a Tenant

When a new requirement comes in, the first decision is whether it should be served by a separate DataOS Instance or by a Tenant within an existing Instance.

This decision depends on isolation, governance, infrastructure control, workload behavior, and cost. In most cases, a Tenant is the right starting point. A separate Instance is more appropriate when strict separation or independent control is required.

***

## Decision flowchart

```mermaid
flowchart TD
    S[New Requirement] --> Q1{PoC or focused initiative?}
    Q1 -- Yes --> T1[Tenant: shared Dataplane + shared compute]
    Q1 -- No --> Q2{Strict infrastructure isolation?}
    Q2 -- Yes --> I1[Separate Instance]
    Q2 -- No --> Q3{Cross-org access needed?}
    Q3 -- Yes --> I2[Separate Instance]
    Q3 -- No --> Q4{Full infra control needed?}
    Q4 -- Yes --> I3[Separate Instance]
    Q4 -- No --> Q5{Cost efficiency priority?}
    Q5 -- No --> I4[Separate Instance]
    Q5 -- Yes --> Q6{Predictable workloads?}
    Q6 -- Yes --> T2[Tenant: shared Dataplane + shared compute]
    Q6 -- No --> I5[Separate Instance]

    style I1 fill:#FF5537,color:#fff,stroke:#733635,stroke-width:2px
    style I2 fill:#FF5537,color:#fff,stroke:#733635,stroke-width:2px
    style I3 fill:#FF5537,color:#fff,stroke:#733635,stroke-width:2px
    style I4 fill:#FF5537,color:#fff,stroke:#733635,stroke-width:2px
    style I5 fill:#FF5537,color:#fff,stroke:#733635,stroke-width:2px
    style T1 fill:#54DED1,color:#202F36,stroke:#009293,stroke-width:2px
    style T2 fill:#54DED1,color:#202F36,stroke:#009293,stroke-width:2px
```

***

## Evaluation criteria

Work through these questions in order. The first "yes" that points to a clear outcome is usually the right answer.

### 1. Business context

Is the requirement a proof of concept, pilot, or focused data initiative?

* **Yes:** Choose a **Tenant with shared Dataplane and shared compute**.
* **No:** Continue to the next question.

### 2. Security and compliance

Does the environment require strict infrastructure isolation?

* **Yes:** Choose a **separate Instance**.
* **No:** Continue.

### 3. Cross-organizational access

Will the environment include users from other departments, external vendors, or consultants?

* **Yes:** Choose a **separate Instance**.
* **No:** Continue.

### 4. Infrastructure control

Does the operating team need full control over upgrades, maintenance schedules, and platform operations?

* **Yes:** Choose a **separate Instance**.
* **No:** Continue.

### 5. Cost efficiency

Is shared infrastructure a higher priority than dedicated resources?

* **No:** Choose a **separate Instance**.
* **Yes:** Continue.

### 6. Workload predictability

Are workloads predictable and unlikely to affect neighboring Tenants?

* **Yes:** Choose a **Tenant with shared Dataplane and shared compute**.
* **No:** Choose a **separate Instance**.

***

## Quick reference

| Requirement                                   | Recommended model                               |
| --------------------------------------------- | ----------------------------------------------- |
| Proof of concept or focused data initiative   | Tenant with shared Dataplane and shared compute |
| Strict infrastructure isolation               | Separate Instance                               |
| Cross-department or external participants     | Separate Instance                               |
| Full upgrade and maintenance control          | Separate Instance                               |
| Cost efficiency through shared infrastructure | Tenant (evaluate further)                       |
| Predictable workloads, low neighbor impact    | Tenant with shared Dataplane and shared compute |

***

## Summary

* Use a **Tenant** when the requirement benefits from shared platform operations, lower cost, faster setup, and controlled reuse of existing infrastructure.
* Use a **separate Instance** when the requirement calls for strict isolation, independent infrastructure control, or broader boundary separation across organizations.

This is a governance and operating model decision, not only an infrastructure decision.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/operate/v1/dataos-operator/choosing-between-instance-and-tenant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.