---
updatedAt: 2026-08-13T15:17:49.000Z
agentTools:
  projectIndex: https://documentation.picsellia.com/llms.txt
---

# Storages and Datalakes

The *Storages and Datalakes* tab, available in the *Integrations* category of your *Organization Settings*, is where you manage the Cloud Storage integrations connected to your *Organization*, and the `Datalake` that read and write `Data` through them.

<Image src="https://files.readme.io/15a3a54ba0952ec3d324364eb0e63c357753c9d527f05339e511394909f0dbf1-image.png" align="center" caption="Storages and Datalake tab" border={true} />

## 1. Cloud Storage Integrations

This section lists every client bucket that has been integrated with your *Organization*, on top of the Picsellia Object Storage created by default for your *Organization*. For each integration, you'll find its name (matching your bucket name on your Cloud Provider) and, if applicable, a *Default* badge.

<Image src="https://files.readme.io/8598a78867f17b2908f42741ab74be11238eb879c4934a6f1ea425116f76db0b-image.png" align="center" caption="List of Cloud Storage Integrations" border={true} />

<Callout icon="📘" theme="info">
  ### Default Cloud Storage for non-image files

  All the files that are not images or videos from a `Datalake` (such as `Experiment` or `ModelVersion` files) are always sent to your _Default_ Cloud Storage.
</Callout>

## 2. Datalake

This section lists every `Datalake` existing in your *Organization*. For each `Datalake`, you'll find the amount of `Data` it contains and which Cloud Storage integration it stores its `Data` in.

<Callout icon="📘" theme="info">
  ### 1 Cloud Storage Integration, several Datalakes

  An _Organization_ can have several `Datalake`, each one connected to a different or the same Cloud Storage integration.
</Callout>

## 3. Connect your own Cloud Storage

By default, a new *Organization* only has one Cloud Storage integration and one `Datalake`, both backed by the Picsellia Object Storage. If your images and videos already live in your own Cloud Storage bucket, Picsellia lets you connect it directly to your *Organization* instead of migrating your `Data` elsewhere: your images and videos always remain stored on your side, and Picsellia only reads and writes to it.

The exhaustive procedure to connect your own bucket, for AWS, Azure or GCP, along with the philosophy behind this mechanism, is detailed [here](https://documentation.picsellia.com/docs/tutorial-connect-storage).

<Callout icon="👍" theme="okay">
  ### Want to integrate your compute infrastructure as well?

  Looking to run your `Trainings` and `Processings` on your own compute infrastructure instead? Head over to [Compute Connectors](https://documentation.picsellia.com/docs/compute-connectors).
</Callout>