Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Choosing between an Instance and a Tenant

Decide whether a new requirement needs a separate DataOS Instance or a Tenant in an existing one.

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.


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 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 compute.

  • No: Choose a separate Instance.


Quick reference

Requirement
Recommended model

Proof of concept or focused data initiative

Tenant with 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 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.

Last updated

Was this helpful?