A backup is a type, not a promise
Every destructive call takes a token that only a successful backup produces. "Never delete without a backup" is checked by the compiler, not by discipline.
Windows 10 and 11 · 64-bit · v1.5.1 · 21 services built in
Take your right-click menu back
See every entry, where it lives in the registry and which program put it there. Hide it, sort it, delete it, or build your own — and every change is backed up before it happens.
No installer. No runtime library. No background service.
Windows 11
Windows 10
Built in Rust
Services
The Categories tab. Click to see it full size.
- Free and open source
- MIT licence
- Windows 11 ready1
- Works without administrator rights2
- Four switches instead of a row of verbs
- Automatic backups before every change
- Updates itself, signature checked first
- A favourites list you place from
- Dark and light mode
- German and English, switched at runtime
- Add entries by drag and drop
- Search across names, paths and commands
- Finds entries whose program is gone
- Built-in services from any OpenAPI address
- Built-in help, with working command lines
- Built in Rust: one file, no runtime library
1 The entries of the Windows 11 menu are listed, hidden and created. Their order up there belongs to Explorer, and the commands it builds in itself carry no registration to reach.
2 Your own entries always go to HKCU. Changing an entry that lives under HKLM needs elevation, and it is asked for that one step only.
Why this one
Six things that are mechanism rather than marketing.
The whole file-type chain
For one extension the scan walks all seven levels Windows walks — user choice, ProgID, perceived type, SystemFileAssociations. The two levels most editors overlook are where image tools register.
Two hundred tools from one address
Paste the docs URL of any service that describes itself through OpenAPI. Every endpoint that takes a file becomes a menu entry, grouped the way the service groups itself.
The new Windows 11 menu, too
Packaged entries are read from their manifests and hidden through the per-user blocked list. Your own entries reach the upper menu through a handler the executable carries inside itself.
Signed updates
The program checks a signature made with a key that does not live in the repository, then the published checksum. A release without both is never offered.
One file, no installer
A single Rust executable. No runtime library, no background service, no registry key of its own until you create one.
Every change is backed up first
Not as a matter of policy. The delete function cannot be called without proof that a backup exists, and the proof is a value only a successful export hands out.
How the backups work