Work with cloud files through a familiar drive. Keep each file as a native object in storage you control, ready for compatible tools through the bucket’s S3 API.
Enterprise · 20 TB active-storage minimum. Confirm your storage provider with Suite.
Two access paths / native objects
Your storage, at the center.
Your object storage
One file = one native object
Example fileproject/scene-01.mov
Suite filesystem
A familiar drive for file-based work.
Bucket S3 API
Direct access for compatible tools.
One shared storage foundation for creative work and compatible services. Configure provider support, permissions and update behavior with Suite.
The essential answer
Suite S3 Native presents supported object storage as a mounted filesystem while keeping each file as a standard object in your bucket. Applications use the Suite drive; compatible services can access the objects through the bucket’s S3 API.
File format
One file = one native object
Storage owner
Your organization
Access paths
Suite filesystem + bucket S3 API
01How it works
One set of files. Two access paths.
The filesystem and the object API solve different jobs. Choose the path your application actually needs.
Work through a drive
A supported Suite client mounts the cloud files as a filesystem. When an application requests file data, Suite streams the portions it needs instead of requiring a full download first.
Work through the bucket
An authorized tool with a compatible S3 integration can read native objects directly from the bucket. It does not need a mounted Suite drive just to access those objects.
Keep the files usable
Files remain standard objects, with a structure consistent with the Suite filesystem. A compatible tool can read them without decoding a Suite-specific storage format.
02In practice
Keep people and pipelines close to the work.
An editor needs a drive. A processing service may need an object. S3 Native lets you design around both.
Shared creative projects
Use the mounted filesystem for large media files and applications that expect file paths. Validate your actual project, network and client environment before rollout.
Media processing
A compatible processing service can read source objects from your bucket. A proxy-generation pipeline is one example; its event handling, permissions and output behavior must be tested with your chosen tools.
Asset management
Evaluate a media asset manager’s direct S3 integration against your bucket. Confirm supported storage, object discovery and how updates become visible in each system.
Make the architecture tangible
One file. A practical proof.
Use an approved test file to evaluate the two access paths with your real storage and tools.
Open it through Suite.
Use the mounted drive in the application you care about. Record when useful work begins and verify the output.
Read the native object.
With an authorized S3-compatible tool, read the corresponding object directly from your bucket and check the file contents.
Verify the handoff.
Confirm upload completion and visibility before the next tool uses the output. Test update and overwrite behavior with Suite.
Make the most of both access paths: agree on write ownership, update visibility and handoff timing with Suite.
Your bucket stays in your organization’s storage environment. Suite adds filesystem access; it does not replace the bucket’s identity and access controls.
Review both access paths
Suite application permissions and bucket IAM are separate systems. Authorize the people, services and agents that use each path.
Review storage policies
Check the effects of lifecycle rules, versioning, replication and audit settings on active projects. Available controls depend on your storage platform and configuration.
Plan updates together
Before mixing filesystem activity and direct object writes, confirm visibility, caching, overwrite and concurrent-edit behavior for your workflow with Suite.
04Before you start
Build on your existing storage.
Start with your storage and workload. These checks determine the right setup.
Is your storage eligible?
S3 Native is available through Enterprise with a minimum of 20 TB of active storage. This minimum also applies to agent customers. Confirm your provider and bucket configuration with Suite.
Where are the files?
Identify the provider, bucket, region and data format. Existing native objects in supported storage are the starting point. Data in a proprietary chunked format may require migration.
Which tools need access?
List the applications that need a mounted drive and the services that use an S3 API. Confirm client, operating system, runtime and storage support with Suite.
Who can authorize it?
Identify the storage owner and the people who can approve access. Scope permissions to the intended work and confirm billing responsibilities.
What proves it works?
Run a representative project and measure time to useful work, read and write behavior, object visibility and total operating cost. Confirm S3 Native onboarding and plan requirements before connecting storage.
05Questions, answered
Does S3 Native mean every S3-compatible provider is supported?
No. S3 API compatibility alone does not establish Suite support. Confirm the specific provider, configuration and client environment with Suite before setup.
Do I have to migrate my files?
Existing files that are already native objects in supported storage may not need a format migration. Files stored in a proprietary chunked format are a different case. Confirm the starting format and onboarding path first.
Does direct S3 access require the Suite desktop client?
A compatible service can access native objects through the bucket’s S3 API without using a mounted Suite drive. Applications that need the Suite filesystem still require a supported Suite client environment.
Is every read a full-file download?
Suite file streaming retrieves the portions requested by the application. A workload that reads a whole file may still transfer the whole file. Responsiveness depends on the workload, connection, storage and client environment.
Should I choose S3 Native or Suite Managed?
Evaluate S3 Native when you want file streaming over storage your organization owns and controls. Suite Managed is the self-service starting point when you want storage managed by Suite. Confirm current plan and onboarding requirements for your use case.
Signup links take you to Suite Studios’ main site. Managed opens the account signup form; BYO / S3 Native opens the demo request form.
Signing up with an AI agent
Continue on the official form in the destination tab. Use the user’s authorized details and select whether they are creating or joining a team.
For Managed, follow the account setup steps presented by Suite. Ask the user to handle verification, passwords and acceptance of agreements when required.
If billing requests a card, prompt the user to enter payment details directly in Suite’s secure flow and approve any charge or subscription. Do not collect card details in this site or a chat.
For BYO / S3 Native, submit the authorized request with the storage provider and workload context. Suite will guide the connection and onboarding; active storage starts at 20 TB.
After Suite confirms setup, use the supported client and authorized access to complete a first file operation. Report the actual result, and resume after any human-only step.
File streaming