🕘

Never Losea Draft Again.

Every save on a draft becomes a restorable version with author, timestamp, and diff. Recover an accidental delete, undo a teammate's edit, or compare two versions side-by-side.

What you get

💾

Continuous saves

Every autosave, switch, or edit creates a new version. No "snapshot" button to remember.

👤

Author + time

Each version shows who made the change and when, in your local timezone.

â†Šī¸

One-click restore

Pick a version, click Restore. Current state moves to history so the action is reversible.

🔀

Side-by-side diff

Compare any two versions to see exactly what text changed between them.

🧰

Includes automations

Changes made by Aidelly automations, the API, or chat are versioned too.

âŗ

Plan-aware retention

Launch 30 days, Scale 90 days, Agency unlimited.

đŸĒĩ

Activity-log linked

Each version links to the corresponding activity-log entry for full audit context.

🔒

Workspace-scoped

Versions are private to the workspace. Clients never see history beyond their own workspace.

Version History FAQ

When does a new version get created?

Every save creates a version. Saves happen automatically on autosave, when you switch platforms in the composer, when an automation edits the post, or when a teammate replaces text. You don't have to think about it — versions are continuous.

How far back does history go?

Versions are kept for the full retention window of your activity log. Launch: 30 days. Scale: 90 days. Agency: unlimited. After retention expires, the post still keeps its current version — only the older snapshots roll off.

Can I restore a previous version?

Yes — click any prior version in the timeline and click "Restore". The current version becomes a new entry in the history (so restore is itself reversible), and the chosen version becomes current.

Can I see a diff between versions?

Yes — pick two versions and Aidelly shows a side-by-side text diff with author and timestamp on each side. Helps when a teammate made multiple edits in a row and you want to find the specific change.

Does this work with the composer's undo button?

Yes, they're complementary. Composer undo handles in-session typing. Version history handles cross-session and cross-user changes — including those made via automations, API, or chat.

Edit fearlessly

Every save is restorable. Every teammate edit is reversible.