← Platform

File revision history without URL churn

Every replacement stays reversible because SteadyLink attaches immutable revisions to the asset instead of overwriting its history.

The problem

Overwriting a stored file erases useful context, while creating a separate file preserves history at the cost of a new URL and more migration work.

The SteadyLink model

Each replacement becomes a retained revision with its own size, type, checksum, scan state, timestamp, label, and note, while one revision remains current for stable delivery.

How it works

Asset history
campaign-hero.webp  ·  v42 current  ·  41 revisions retained
  1. 1

    Upload a replacement

    The new file enters the same scanning and metadata pipeline as the original.

  2. 2

    Review the revision

    Add a label or note and compare its metadata with older versions.

  3. 3

    Choose what is current

    Promote any retained revision while the asset URL stays in place.

What this changes

Read the documentation
Inspect every retained replacement
Label releases and record team notes
Promote an older revision without republishing links
Pin a specific revision when bytes must remain immutable

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

Image transformations

Request image width, height, quality, WebP, AVIF, JPG, or PNG output from the edge while preserving the original asset revision.

Learn more

Private and signed media

Keep files private by default and create time-limited signed URLs when a browser, customer, or external service needs temporary access.

Learn more