> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/data-privacy/byos.md).

# Bring Your Own Storage

Learn how Currents can be integrated to your own S3-compatible object storage.

{% hint style="success" %}
**Availability**

The Bring Your Own Storage (BYOS) feature is available as part of the **Enterprise plan.** It provides a simple and secure way to integrate our solution with your existing storage infrastructure, ensuring full data ownership.\
\
Contact our support team if you're interested in enabling this feature for your organization.
{% endhint %}

### Overview

Our Bring Your Own Storage (BYOS) model allows customers to use their own S3-compatible object storage with our solution.\
Instead of uploading data to storage managed by us, all files remain within the customer’s storage environment.

We integrate directly with your storage and handle the setup on our side.

Examples of S3-compatible storage providers:

* GCS(Google GCP)
* S3 (AWS)
* R2 (Cloudflare)
* Wasabi
* Backblaze B22

### How It Works

To enable BYOS, we require the following from you:

* An S3-compatible storage endpoint
* A dedicated bucket for the solution
* Access credentials (with the minimum required permissions)

Once these are provided, our team will configure the solution to securely read and write data directly to your storage.

### Full Data Ownership

You retain complete ownership and control of your data:

* Data is stored exclusively in your infrastructure
* You control retention, lifecycle policies, and access
* No duplication of data into third-party storage

### Security & Access

* Access is limited strictly to the provided bucket
* Permissions follow the principle of least privilege
* Credentials can be rotated or revoked at any time


---

# 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.currents.dev/resources/data-privacy/byos.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.