> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/learn/products-and-core-concepts/silk-product-fundamentals/silk-datapods-overview.md).

# Silk DataPods Overview

Learn what Silk DataPods do in your environment, how they relate to clusters and the other Silk products, and which choices and tools shape each DataPod.

## DataPods Introduction

Silk DataPods are where your application and database data lives. Hosts connect to a DataPod over iSCSI, read and write to its volumes, and rely on it for snapshots, clones, and replication.

The other Silk products are built around DataPods. Flex deploys and scales them, Echo creates database copies from their snapshots, and Clarity reports on how they're performing. Understanding DataPods gives you the foundation for working with the rest of Silk.

{% hint style="info" %}
**Looking for a summary of all four Silk products?**

See [Silk Product Overview](/learn/get-to-know-silk/silk-product-overview.md).
{% endhint %}

### How DataPods work with other Silk products

<table><thead><tr><th width="140.7406005859375">Product</th><th>Relationship to DataPods</th></tr></thead><tbody><tr><td><strong>Silk Flex</strong></td><td>Deploys DataPods, scales their resources, and manages the cloud infrastructure behind them.</td></tr><tr><td><strong>Silk Echo</strong></td><td>Uses DataPod snapshot and thin-cloning capabilities to create database copies. Each Echo operation runs within a single DataPod.</td></tr><tr><td><strong>Silk Clarity</strong></td><td>Monitors DataPod health, performance, capacity, and data protection across your environment.</td></tr></tbody></table>

## DataPods and clusters

Every DataPod runs inside a **cluster**. The cluster provides the shared networking and environment-wide settings its DataPods use, and each Flex instance manages one cluster.

A cluster can contain multiple DataPods. You might use separate DataPods to isolate workloads with different performance needs, environments, or owners.

The cluster's size limits how many Silk resources it can hold and can't be changed after creation, so plan it with your expected number of DataPods in mind.

To learn what a cluster defines and how it supports its DataPods, see [Clusters and DataPods](/learn/products-and-core-concepts/datapod-architecture/clusters-and-datapods.md).

## What's inside a DataPod

A DataPod separates performance from capacity into two layers:

{% columns %}
{% column %} <i class="fa-microchip">:microchip:</i>

**Performance layer**

**c.nodes** process I/O from connected hosts and apply data services. Add c.nodes when workloads need more throughput.
{% endcolumn %}

{% column %} <i class="fa-hard-drive">:hard-drive:</i>

**Capacity layer**

**m.nodes**, each made up of a group of **d.nodes**, store and protect persistent data. Add m.nodes when you need more physical capacity.
{% endcolumn %}
{% endcolumns %}

Since each layer scales on its own, you add only the resources a workload actually needs. Hosts keep connecting to the same DataPod as its underlying resources change.

To learn how the node types work together and how data flows through them, see [Clusters and DataPods](/learn/products-and-core-concepts/datapod-architecture/clusters-and-datapods.md#datapod-architecture).

## Choices you make when creating a DataPod

When you create a DataPod in Flex, a few decisions shape what it can do and how it can grow:

<table><thead><tr><th width="180">Decision</th><th>What it determines</th></tr></thead><tbody><tr><td><strong>Workload profile</strong></td><td>The available c.node configurations, logical capacity range, and read cache. Options are High Performance (the default), Accelerated Performance, and Limited Capacity. Availability varies by cloud provider.</td></tr><tr><td><strong>Storage type</strong></td><td>How the capacity layer is built. VM Local Disk is available on AWS, Azure, and Google Cloud. Managed Disk uses Azure Premium SSD v2 and is available only on Azure.</td></tr><tr><td><strong>Node types</strong></td><td>The VM types used for c.nodes and m.nodes. Flex shows the options compatible with your workload profile, storage type, and region.</td></tr><tr><td><strong>Capacity</strong></td><td>The DataPod's maximum allocated capacity and the physical capacity it starts with.</td></tr></tbody></table>

Together, the workload profile and storage type make up the DataPod's **deployment profile**.

{% hint style="warning" %}
**Some choices are permanent**

Some settings, including maximum allocated capacity, can't be changed after the DataPod is created. Review your configuration and expected growth with your Silk representative before deployment.
{% endhint %}

To compare profiles and node options, see [DataPod Deployment Profiles](/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md). To size a DataPod, see [Plan DataPod Capacity](/deploy/plan-your-deployment/plan-datapod-capacity.md).

## Manage a DataPod

You work with a DataPod through two interfaces, each at a different level.

{% columns %}
{% column %} <i class="fa-joystick">:joystick:</i>

**Silk Flex** manages the DataPod as a whole. Use it to create, scale, migrate, and decommission a DataPod, and to review its health, capacity, and performance.
{% endcolumn %}

{% column %} <i class="fa-desktop">:desktop:</i>

**The SDP Management Console** manages what's inside one DataPod. Use it to work with volumes, hosts, mappings, snapshots, replication, capacity policies, and users.
{% endcolumn %}
{% endcolumns %}

{% hint style="success" icon="lightbulb" %}
**Use Flex to change the DataPod. Use the SDP Management Console to work inside it.**
{% endhint %}

You can open a DataPod's SDP Management Console directly from Flex. For automation, DataPods also support the [Silk RESTful API](/api-reference/getting-started/silk-restful-api.md) and a command-line interface.

For a tour of the console and its user roles, see [SDP Management Console Overview](/learn/products-and-core-concepts/datapod-architecture/sdp-management-console-overview.md).

## Next steps

* [**Plan DataPod capacity**](/deploy/plan-your-deployment/plan-datapod-capacity.md) to estimate allocated and physical capacity before you create a DataPod.
* [**Connect hosts**](/deploy/connect-hosts/host-connectivity.md) to make DataPod volumes available to your applications and databases.
* [**Organize storage**](/learn/data-management-concepts/volumes-and-volume-groups.md) with volumes and volume groups.
* [**Protect your data**](/manage/protect-your-environment/replication-and-recovery.md) with recovery points and replication between DataPods.
* [**Monitor your environment**](/manage/monitor-and-automate-silk/monitor-your-silk-environment.md) to track DataPod health, performance, and capacity.
* [**Review platform limits**](/learn/references/silk-platform-configuration-limits.md) before you scale a DataPod.


---

# 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.silk.us/learn/products-and-core-concepts/silk-product-fundamentals/silk-datapods-overview.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.
