Rive Blog
New Enterprise feature gives control over Rive file storage
BYOB (Bring Your Own Bucket) lets you store your Rive files at rest in your own AWS S3 bucket, including encryption, region selections, and access policies.
Some enterprise teams need more control over where their data lives. BYOB (Bring Your Own Bucket) is our answer.
This is a new Enterprise feature that lets you store your Rive files at rest in your own AWS S3 buckets, instead of Rive’s infrastructure. You still get the full Rive experience, but you also choose the region. You set the access policies. You can encrypt it with your own keys. And you can revoke access at any time.
This is important for organizations with strict security, compliance, or data residency requirements, like government contractors or companies operating under mandates to store data within a specific country or infrastructure.
What’s stored, and where?
Files created in the Rive Editor, including user-generated and auto-generated revisions, uploaded assets such as images and audio, and cloud renderer output, will live in your S3 bucket instead of ours. This ensures your source files remain fully under your control. You can monitor access via your own AWS logs, perform your own backups, and cut off access instantly if needed by revoking a single role in your AWS account.
What’s still processed by Rive?
Because Rive is a collaborative design platform, active editing still happens on Rive’s infrastructure. That includes syncing changes across users, resolving version conflicts, and generating runtime-optimized .riv files. All of this happens in memory during an active session. We never store that data on disk.
Assets, such as images and fonts, are temporarily stored on disk while we process them (e.g., resizing, compressing), but are deleted immediately afterward.
What are the benefits?
Complete control over your file storage. Store .riv and .rev files in your own S3 bucket, not Rive’s.
Regional compliance support. Choose which AWS region your data lives in. This is helpful for teams with GDPR or country-specific mandates.
Key management. Encrypt files with your own keys.
Revocable access. Instantly revoke Rive’s access to your bucket, no support request required.
Audit visibility. Use your own access logs to see when/where files were accessed.
Live multiplayer editing. Revision history lives on your storage.
BYOB is not offline mode
BYOB is not about removing Rive from the loop. Your data at rest lives in your infrastructure, but Rive’s cloud-based tools still handle collaboration, rendering, and file syncing. It’s the best of both worlds: enterprise-grade control without giving up the full power of Rive.
For most security and compliance teams, control over data at rest is the key requirement. And that’s what BYOB delivers.
How it works
You provide an S3 bucket and configure access.
Rive stores your files directly in that bucket.
You manage access, logging, and region selection.
Rive continues to handle in-memory processing during editing sessions.
Let’s get your bucket connected
Some enterprise teams need more control over where their data lives. BYOB (Bring Your Own Bucket) is our answer.
This is a new Enterprise feature that lets you store your Rive files at rest in your own AWS S3 buckets, instead of Rive’s infrastructure. You still get the full Rive experience, but you also choose the region. You set the access policies. You can encrypt it with your own keys. And you can revoke access at any time.
This is important for organizations with strict security, compliance, or data residency requirements, like government contractors or companies operating under mandates to store data within a specific country or infrastructure.
What’s stored, and where?
Files created in the Rive Editor, including user-generated and auto-generated revisions, uploaded assets such as images and audio, and cloud renderer output, will live in your S3 bucket instead of ours. This ensures your source files remain fully under your control. You can monitor access via your own AWS logs, perform your own backups, and cut off access instantly if needed by revoking a single role in your AWS account.
What’s still processed by Rive?
Because Rive is a collaborative design platform, active editing still happens on Rive’s infrastructure. That includes syncing changes across users, resolving version conflicts, and generating runtime-optimized .riv files. All of this happens in memory during an active session. We never store that data on disk.
Assets, such as images and fonts, are temporarily stored on disk while we process them (e.g., resizing, compressing), but are deleted immediately afterward.
What are the benefits?
Complete control over your file storage. Store .riv and .rev files in your own S3 bucket, not Rive’s.
Regional compliance support. Choose which AWS region your data lives in. This is helpful for teams with GDPR or country-specific mandates.
Key management. Encrypt files with your own keys.
Revocable access. Instantly revoke Rive’s access to your bucket, no support request required.
Audit visibility. Use your own access logs to see when/where files were accessed.
Live multiplayer editing. Revision history lives on your storage.
BYOB is not offline mode
BYOB is not about removing Rive from the loop. Your data at rest lives in your infrastructure, but Rive’s cloud-based tools still handle collaboration, rendering, and file syncing. It’s the best of both worlds: enterprise-grade control without giving up the full power of Rive.
For most security and compliance teams, control over data at rest is the key requirement. And that’s what BYOB delivers.
How it works
You provide an S3 bucket and configure access.
Rive stores your files directly in that bucket.
You manage access, logging, and region selection.
Rive continues to handle in-memory processing during editing sessions.
Let’s get your bucket connected
Some enterprise teams need more control over where their data lives. BYOB (Bring Your Own Bucket) is our answer.
This is a new Enterprise feature that lets you store your Rive files at rest in your own AWS S3 buckets, instead of Rive’s infrastructure. You still get the full Rive experience, but you also choose the region. You set the access policies. You can encrypt it with your own keys. And you can revoke access at any time.
This is important for organizations with strict security, compliance, or data residency requirements, like government contractors or companies operating under mandates to store data within a specific country or infrastructure.
What’s stored, and where?
Files created in the Rive Editor, including user-generated and auto-generated revisions, uploaded assets such as images and audio, and cloud renderer output, will live in your S3 bucket instead of ours. This ensures your source files remain fully under your control. You can monitor access via your own AWS logs, perform your own backups, and cut off access instantly if needed by revoking a single role in your AWS account.
What’s still processed by Rive?
Because Rive is a collaborative design platform, active editing still happens on Rive’s infrastructure. That includes syncing changes across users, resolving version conflicts, and generating runtime-optimized .riv files. All of this happens in memory during an active session. We never store that data on disk.
Assets, such as images and fonts, are temporarily stored on disk while we process them (e.g., resizing, compressing), but are deleted immediately afterward.
What are the benefits?
Complete control over your file storage. Store .riv and .rev files in your own S3 bucket, not Rive’s.
Regional compliance support. Choose which AWS region your data lives in. This is helpful for teams with GDPR or country-specific mandates.
Key management. Encrypt files with your own keys.
Revocable access. Instantly revoke Rive’s access to your bucket, no support request required.
Audit visibility. Use your own access logs to see when/where files were accessed.
Live multiplayer editing. Revision history lives on your storage.
BYOB is not offline mode
BYOB is not about removing Rive from the loop. Your data at rest lives in your infrastructure, but Rive’s cloud-based tools still handle collaboration, rendering, and file syncing. It’s the best of both worlds: enterprise-grade control without giving up the full power of Rive.
For most security and compliance teams, control over data at rest is the key requirement. And that’s what BYOB delivers.
How it works
You provide an S3 bucket and configure access.
Rive stores your files directly in that bucket.
You manage access, logging, and region selection.
Rive continues to handle in-memory processing during editing sessions.
Let’s get your bucket connected
Join our newsletter
Get all the latest Rive news delivered to your inbox.