Triton Cloud Object Storage
Create Buckets next to your Triton Cloud Instances and use familiar S3 clients.
Get cloud early access →S3-compatible storage on the same Triton Cloud platform as your Instances. Instance-to-Bucket traffic stays on the private path and does not bill as egress.
Put backups, assets, datasets, and build artifacts in Buckets your Instances can reach privately. The path does not need to leave the VPC or become a separate internet transfer line item.
Scheduled database dumps and Instance backups.
Assets, downloads, datasets, and generated output.
CI output and release archives available across Instances.
The common object path is only the start. Manta implements the storage controls teams use to protect data and automate its lifecycle.
Protect current data and make updates only when the object state you expect is still true.
Apply retention in GOVERNANCE or COMPLIANCE mode and place legal holds that cannot be bypassed.
Expire current and noncurrent versions by age, and clean up abandoned multipart uploads.
Encryption requests are explicitly rejected today rather than accepted while storing plaintext. The compatibility reference names every supported, partial, rejected, and missing operation.
Read the operation matrix →Manta is the open-source storage system. Object Storage is the managed surface on Triton Cloud. The same system is part of Triton Private Cloud when you need to run the platform on infrastructure you control.
Create Buckets next to your Triton Cloud Instances and use familiar S3 clients.
Get cloud early access →The same open-source system is the Manta data-services direction for Triton Private Cloud, currently in development.
Review your environment →A flat monthly base covers storage and requests, followed by a per-GB storage overage. Private traffic between your Instances and Buckets does not bill as egress.
Block Storage and Filesystem are planned, not available today. Manta data services for Triton Private Cloud are in development.
View the roadmap →