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.
How it works
You save a storage config once, and every run after that follows it.
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
- 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.
The storage integration page 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.
Put the vocabulary to work
One API to join, record, stream and transcribe meetings across Zoom, Google Meet and Microsoft Teams.