Depotify is a self-hosted repository manager for source code, system and language packages, container images, infrastructure modules and plain files — 21 repository types that work the same way: one rule language, one kind of access token, one audit trail, and one way to delete, restore and securely wipe. Each tool is a module: run all 21 on one server, or each where it belongs — git on one machine, Mercurial on another, the package registries on a third. Your hardware, your network, your rules.
Could Bob upload a hotfix into the release folder? The simulator asks the same rule engine the server uses and answers with the decision, the rule that made it and the note its author left for whoever is refused — here: application releases are published by the release pipeline only.
A deletion in two weeks, a secure wipe in tonight's maintenance window: every job is listed with who asked for it, can be cancelled or moved, and checks the rights again when its time comes.
A token for the build server publishes RPMs and nothing else; one for a laptop only installs Python packages. Scopes are chosen from a tree, a token expires, and a revoke takes effect on the next request.
Cache PyPI, npm, crates.io, Docker Hub or a distribution mirror. Every option of a remote repository says what it allows and what it refuses — and a repository never fetches from itself.