---
title: "Tenant states"
description: "Multi-tenant collections enable you to efficiently manage isolated subsets of data using the same schema and configuration. Weaviate supports the following tenant states:"
url: https://docs.weaviate.io/weaviate/starter-guides/managing-resources/tenant-states
---

# Tenant states

Multi-tenant collections enable you to efficiently manage isolated subsets of data using the same schema and configuration. Weaviate supports the following tenant states:

| Tenant state | CRUD & Queries | Vector Index | Inverted Index | Object Data | Time to Activate | Tenant description |
| - | - | - | - | - | - | - |
| Active (default) | **Yes** | Hot/Warm | Warm | Warm | None | Available for use |
| Inactive | **No** | Warm | Warm | Warm | Fast | Not available for use, stored locally |
| Offloaded | **No** | Cold | Cold | Cold | Slow | Not available for use, stored on the cloud |

A tenant status management strategy can help you to balance cost and performance. Here's why. An active tenant with an HNSW index uses *hot* resources, which are the most expensive. At the other end of the spectrum, an offloaded tenant uses *cold* resources, which are the least expensive.

> [!NOTE]
>
> **Tenant state propagation**
>
> A tenant state change may take some time to propagate across a cluster, especially a multi-node cluster.
>
>
>
> For example, data may not be immediately available after reactivating an offloaded tenant. Similarly, data may not be immediately unavailable after offloading a tenant. This is because the [tenant states are eventually consistent](https://docs.weaviate.io/weaviate/concepts/replication-architecture/consistency#tenant-states-and-data-objects), and the change must be propagated to all nodes in the cluster.

### Tenant states and resource usage

*Hot* tenants can be deactivated to *warm* storage to reduce memory usage, and any tenant can be offloaded to *cold* storage to reduce memory and disk usage. Conversely, any tenant can be reactivated when needed.

Therefore, consider a strategy of deactivating tenants that are not frequently accessed, and offloading tenants that are rarely accessed.

For example, imagine an e-commerce platform with separate tenants for each vendor. During a holiday sale, the tenant for a popular electronics vendor might be kept active for quick access, while tenants for seasonal vendors (e.g., Christmas decorations in July) could be offloaded to cold storage to save resources.

Understanding how tenant states interact with different index types is crucial for developing an effective resource management strategy. Let's explore this relationship in more detail.

### Tenant states and index types

Tenant states management strategies are tied to index types. This is because the index type determines the resources used by a tenant. For example, a tenant with an HNSW index type uses *hot* resources, while a tenant with a flat index type uses *warm* resources.

If a multi-tenant collection is configured with a dynamic index type, some tenants may be stored in *warm* storage (flat index) and others in *hot* storage (HNSW index). As a result, effectively managing tenants with HNSW indexes may have the most significant impact on resource usage.

We suggest following the following guidelines for selecting a tenant state:

```mermaid
flowchart LR
    %% Define nodes and connections
    subgraph tenantData ["Tenant Data Availability"]
        direction LR
        needNow{"Does the tenant data<br> need to be<br> available now?"}
        howQuick{"When it is needed,<br> how quickly does it<br> need to be available?"}

        needNow -->|Yes| active["Active"]
        needNow -->|No| howQuick
        howQuick -->|Quickly| inactive["Inactive"]
        howQuick -->|"Latency is acceptable"| offloaded["Offloaded"]
    end

    %% Style nodes
    style needNow fill:#ffffff,stroke:#B9C8DF,color:#130C49
    style howQuick fill:#ffffff,stroke:#B9C8DF,color:#130C49

    %% Terminal nodes
    style active fill:#ffffff,stroke:#61BD73,color:#130C49
    style inactive fill:#ffffff,stroke:#61BD73,color:#130C49
    style offloaded fill:#ffffff,stroke:#61BD73,color:#130C49

    %% Style subgraph
    style tenantData fill:#ffffff,stroke:#61BD73,stroke-width:2px,color:#130C49
```

If you are unsure which tenants can be made inactive or offloaded, consider a strategy of deactivating tenants that have not been accessed for a certain period of time. And offloading tenants that have not been accessed for a longer period of time.

## Hands-on

Here are some resources to implement hands-on tenant offloading in Weaviate.

### Configure tenant offloading

In order to use tenant offloading, you need to configure an offload module.\
(See [How-to: Configure tenant offloading](https://docs.weaviate.io/deploy/configuration/tenant-offloading))

### Update a tenant state

A tenant state can be switched between `active`, `inactive`, and `offloaded` at any time.\
(See [How-to: Manage tenant states](https://docs.weaviate.io/weaviate/manage-collections/tenant-states) for instructions and code examples.)

### Auto-activate tenants

You can configure a collection to automatically activate (inactive and offloaded) tenants when they are accessed.\
This can provide a balance between resource usage and performance.\
(See [How-to: Auto-activate tenants](https://docs.weaviate.io/weaviate/manage-collections/tenant-states#automatically-activate-tenants) for instructions and code examples.)
