# What is bring your own storage?

> Bring your own storage (BYO storage, sometimes BYOB for bring your own bucket) means a vendor writes the artefacts it produces for you straight into.

Source: https://meetstream.ai/glossary/byo-storage

*By Sidhdharth Sivasubramanian, Co-founder and CEO, MeetStream*

Bring your own storage means a vendor writes the files it makes for you straight into a bucket you own.

It is also called BYO storage, or BYOB for bring your own bucket.

Retention, encryption, region and access then follow your rules.

- **Bot**: records
- **Processing**: artefacts
- **Your bucket**: S3, OSS, R2
- **Your policy**: retention, lock, region

*Artefacts are written to your bucket, never to ours, under your rules.*

## How it works

You save a storage config once, and every run after that follows it.

- **Save a config**: Provider, bucket, region
- **Add credentials**: And a prefix you choose
- **Run a bot**: Nothing else changes
- **Files land**: In a folder per bot

*Set it once, and each artefact lands under a folder named for the bot.*

The bot record keeps track of where each artefact went.

Old media stays reachable after a config change.

## Providers and artefacts

Three provider families, one active at a time.

- Amazon S3
- Alibaba Cloud OSS
- S3-compatible endpoints such as Cloudflare R2

On MeetStream the config covers every artefact a bot produces:

- Recordings and [per-participant streams](https://meetstream.ai/glossary/per-participant-audio)
- Transcripts and manifests
- Participant lists, chat logs and screenshots

## read_write vs write_only

Two access modes, and the choice is about who fetches the media.

- **read_write**: MeetStream can read it back Fetch endpoints keep working One-hour signed URLs to your objects The simpler path to start on
- **write_only**: MeetStream writes and deletes Nothing is ever read back You collect media with your own tools Regulated teams usually pick this

*The same bucket, with two levels of access granted back.*

The [storage integration page](https://meetstream.ai/integrations/s3-storage) has the setup steps.

It also carries the access policy and the object layout.

## Frequently asked questions

### Which providers are supported?

Amazon S3, Alibaba Cloud OSS, and S3-compatible endpoints through endpoint_url, such as Cloudflare R2.

### Does BYO storage cost extra?

You pay your storage provider for the bytes. MeetStream publishes no separate charge for the setup.

Once it is active, nothing is written to MeetStream storage.

### What happens to media written before I switched?

It stays where it was written. Each artefact records its own provider, bucket and prefix.

### Can I keep MeetStream from reading my media?

Yes, write_only mode.

## Keep exploring

- [Bring your own storage](https://meetstream.ai/integrations/s3-storage): Integration
- [Security](https://meetstream.ai/security): Company
- [Compliance recording](https://meetstream.ai/use-cases/compliance-recording): Use case
- [Webhook](https://meetstream.ai/glossary/webhook): Glossary
- [Meeting bot](https://meetstream.ai/glossary/meeting-bot): Glossary
- [Bot lifecycle](https://meetstream.ai/glossary/bot-lifecycle): Glossary

## Put the vocabulary to work

One API to join, record, stream and transcribe meetings across Zoom, Google Meet and Microsoft Teams.

---

Full site index for agents: https://meetstream.ai/llms.txt
API contract (OpenAPI 3.1): https://meetstream.ai/openapi.json
MCP discovery: https://meetstream.ai/.well-known/mcp