S3 compatible
Connect AWS CLI, Laravel S3 disks, Flysystem, rclone, s3cmd, and other S3-compatible clients to the ACDN endpoint.
Each storage zone is a S3-compatible, isolated object namespace with its own bucket name, region, and credentials. Use familiar S3 workflows, then connect the same zone directly to ACDN delivery.
Works with AWS CLI, Laravel and Flysystem, rclone, s3cmd, and other S3-compatible clients. Compatibility boundaries
Keep familiar S3 tooling and object workflows while gaining regional storage and direct integration with ACDN delivery.
Connect AWS CLI, Laravel S3 disks, Flysystem, rclone, s3cmd, and other S3-compatible clients to the ACDN endpoint.
Use SigV4 header authentication and presigned URLs for secure object access and uploads.
Give each workload its own bucket name, credentials, and explicit storage region.
List, upload, read, inspect, and delete objects through standard S3 operations, including byte-range downloads.
Use the direct AccessKey API alongside S3 when a lightweight GET, PUT, HEAD, or DELETE integration is enough.
Use a storage zone as the origin for a pull zone and place cached edge delivery in front of stored objects.
Upload a compatible MP4 once. ACDN creates the HLS manifest and media segments as viewers request them through a linked pull zone—without a preprocessing pipeline or stored HLS copies.
Publish without generating every HLS segment ahead of time. Packaging starts when the playback path is requested.
The original MP4 remains unchanged, and generated HLS files are not written back to the storage zone.
Serve manifests and segments from the hostname of a pull zone linked directly to the storage zone.
video/library/launch.mp4
https://cdn.example.com/hls/video/library/launch.mp4/master.m3u8
Compatible MP4 input is required. HLS packaging does not transcode unsupported audio or video codecs.
Start with a zone and object paths, automate access through the storage endpoint, and add CDN delivery where public reach is needed.
Choose a stable zone name and region, then plan directory prefixes around your product or media structure.
Point your existing S3 client at the ACDN endpoint and configure the bucket, region, access key ID, and secret.
Create a pull zone backed by storage, then validate public URLs, cache behavior, and invalidation for changing files.
Organize images, audio, and video under predictable paths before serving them through a pull zone.
Keep JavaScript, CSS, archives, and downloadable files in a dedicated delivery source.
Separate retained files from public delivery content with purpose-specific storage zones.
Use existing S3 libraries and tools without rewriting the application storage layer.
Storage is priced by the amount of data kept in your storage zone each month.
View all pricingA flat price for S3-compatible data storage inside a storage zone.
Keep your existing S3 workflow, store objects in an isolated zone, and connect them to ACDN delivery when you need public reach.