S3-compatible object storage

S3-compatible object storage

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

S3 without migration friction

S3 compatibility in every storage zone

Keep familiar S3 tooling and object workflows while gaining regional storage and direct integration with ACDN delivery.

01

S3 compatible

Connect AWS CLI, Laravel S3 disks, Flysystem, rclone, s3cmd, and other S3-compatible clients to the ACDN endpoint.

02

AWS Signature Version 4

Use SigV4 header authentication and presigned URLs for secure object access and uploads.

03

Isolated buckets and regions

Give each workload its own bucket name, credentials, and explicit storage region.

04

Complete object workflow

List, upload, read, inspect, and delete objects through standard S3 operations, including byte-range downloads.

05

Simple HTTP API included

Use the direct AccessKey API alongside S3 when a lightweight GET, PUT, HEAD, or DELETE integration is enough.

06

CDN-ready source

Use a storage zone as the origin for a pull zone and place cached edge delivery in front of stored objects.

On-demand HLS packaging

Turn one stored MP4 into an HLS playback URL

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.

01

Package on demand

Publish without generating every HLS segment ahead of time. Packaging starts when the playback path is requested.

02

Keep one source object

The original MP4 remains unchanged, and generated HLS files are not written back to the storage zone.

03

Deliver through the edge

Serve manifests and segments from the hostname of a pull zone linked directly to the storage zone.

On-demand playback path HLS
Stored source object video/library/launch.mp4
Package as HLS on request
HLS manifest 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.

A direct path to delivery

Build the object flow around your application

Start with a zone and object paths, automate access through the storage endpoint, and add CDN delivery where public reach is needed.

  1. 01

    Create and organize a zone

    Choose a stable zone name and region, then plan directory prefixes around your product or media structure.

  2. 02

    Connect your application

    Point your existing S3 client at the ACDN endpoint and configure the bucket, region, access key ID, and secret.

  3. 03

    Add edge delivery

    Create a pull zone backed by storage, then validate public URLs, cache behavior, and invalidation for changing files.

Keep content organized

Storage for the files your products depend on

Media libraries

Organize images, audio, and video under predictable paths before serving them through a pull zone.

Static application assets

Keep JavaScript, CSS, archives, and downloadable files in a dedicated delivery source.

Backups and archives

Separate retained files from public delivery content with purpose-specific storage zones.

S3-native applications

Use existing S3 libraries and tools without rewriting the application storage layer.

Straightforward storage pricing

One rate for data stored in a zone

Storage is priced by the amount of data kept in your storage zone each month.

View all pricing
Ready for your files

Point your S3 client at ACDN

Keep your existing S3 workflow, store objects in an isolated zone, and connect them to ACDN delivery when you need public reach.