Private media delivery with expiring signed URLs

Public and restricted media use the same asset and revision model, with visibility controlling who can fetch the current bytes rather than how the file is organized.

The problem

Exposing raw storage URLs leaks infrastructure details and makes temporary access difficult to revoke or audit.

The SteadyLink model

Private assets reject public delivery while authorized applications can issue signed URLs with defined expirations and revoke them when access should end early.

How it works

Time-limited delivery

https://cdn.steadylink.io/a/private-report?token=expiring_grant

1
Mark the asset private
Set visibility on the bucket or individual file.
2
Create a signed grant
Choose an expiration through the dashboard or API.
3
Share temporary access
The recipient can fetch the file until the grant expires or is revoked.

What this changes

Read the documentation

Keep storage provider URLs private

Set an explicit access expiration

List and revoke active signed grants

Use public and private files in the same workspace

More of the platform

Stable asset URLs

Give each media asset one permanent delivery URL, then replace the underlying file and retain every revision without breaking apps, sites, emails, or embeds.

Learn more