Storing a file is easy. What makes a repository trustworthy is everything that happens afterwards: whether a published version can change under your feet, whether a mistake can be undone, whether a deletion is really a deletion, and whether a file you promised to keep is really kept. Depotify answers each of those questions explicitly — the same way in every tool.
upload ──▶ published ──▶ trash ──▶ purged
│ ▲ │
│ └─restore──┘
├──▶ revisions (where you ask for them)
├──▶ scheduled deletion ──▶ trash / purged
├──▶ wipe ──▶ overwritten, then removed
└──▶ retention hold: nothing above happens until it ends
Published means published
A path, once written, is immutable: uploading different bytes to it is refused. A build that was tested is the build that ships, and a dependency you pinned yesterday is the one you get today. Identical content is stored once, however many paths and repositories refer to it.
Where changing content is the point — a nightly report, a "latest" artifact — a repository can keep revisions for the paths you choose:
- each new upload becomes the next revision, and every earlier one stays reachable;
- re-uploading what is already there changes nothing;
- an older revision can be made current again — as a new revision, so the history stays honest — without copying a byte;
- a revision can be locked against deletion, and a repository can keep only the newest N;
- paths declared as releases never take revisions, whatever else is configured.
Mistakes can be undone
- Take it back. An uploader without delete rights can still withdraw their own upload within a short window the repository sets — the "I pushed the wrong file" button.
- Trash. A deletion moves a file to the repository's trash: out of every listing, its content kept, restorable by the person who deleted it or anyone allowed to delete there. The trash empties itself after the number of days each repository sets.

- Purge. Removing something from the trash for good is a separate right from deleting it.
- Repositories, too. Deleting a whole repository that holds anything requires typing its name again, and is refused while it holds files under retention or is part of a virtual repository.
Delete later
A deletion — to the trash or permanent — can be scheduled for a date up to a year ahead: the file stays until then, and its listing shows the job. When the time comes, Depotify checks the rights again against the rules as they are then, and refuses if the file has changed in the meantime. Jobs can be cancelled and rescheduled, by their owner or by someone allowed to manage jobs; results stay in the job list.

Wipe: deletion that means it
For data that must not be recoverable — a leaked credential in a build artifact, a customer file, a licence that was withdrawn — Depotify can wipe:
- The file disappears from the listing at once.
- A wipe job waits for the repository's delay and its daily maintenance window — cancelling it in that time brings the file back.
- When it runs, it checks the rights again, takes the content out of the store and overwrites it the configured number of times with the configured pattern — random data, zeros, ones or a fixed byte — flushing each pass to disk, then truncates, renames and removes it. Progress is visible in the job.
Shared content is never wiped behind anyone's back. If the same bytes are also stored under other paths, the request is answered with every other path, and the person chooses: remove only this path and wipe the content when its last user is gone, or — with a stronger right — wipe it everywhere, after the other owners have been notified in the application and by e-mail.
Administrators can pause all new wipes, for an audit or an investigation; the pause survives a restart.
An honest limit: on SSDs and copy-on-write file systems an overwrite cannot guarantee the old blocks are gone, and backups and snapshots are not wiped. Depotify says so rather than promise what no software can.
Retention: a promise nobody can break early
Some files must be kept — for a regulator, a customer contract or a lawsuit. Depotify supports WORM (write once, read many) retention on any file revision:
| Mode | Who can end it early |
|---|---|
| Governance | only people with the hold right |
| Compliance | nobody — it can be extended, never shortened, softened or removed |
| Legal hold | until it is lifted; no end date |
A held file cannot be deleted, wiped, overwritten by a newer revision's clean-up or removed with its repository — every path to destroying it checks the hold and refuses with the reason. A lock, by contrast, is a convenience for the team; a hold is a promise to someone outside it, and the interface treats them differently.
Notices in your own time zone
Scheduled actions and shared-content wipes produce notices in the application and by e-mail. Times are shown in each reader's own time zone, from their account settings, then the site's, then the server's.
