Stable file identities

A SteadyLink file has one identity. Replacements add revisions, and the workspace chooses which clean revision its stable URL serves.

Current and revision-specific delivery

The URL /a/{asset_id} follows the current revision. Use ?v=42 when a consumer must stay on one retained revision.

Stable URL

cdn.steadylink.io/a/asset_uuid

Revision-specific URL

cdn.steadylink.io/a/asset_uuid?v=42

Replacement, promotion, and rollback

Replacing a file creates a new immutable revision and makes it current after finalization and scanning. Promoting an older clean revision changes the current pointer without copying bytes or changing the stable URL.

The stable URL has a five-minute cache lifetime. Revision-specific responses are immutable and cacheable for one year. A promoted revision may take up to the stable cache lifetime to appear everywhere.

Need another path?

Open dashboard Read engineering notes