Get RVLTION
Find where the things you copied came from.
RVLTION runs on your machine and keeps its history there. There is no account to create and nothing to configure before it starts working.
Windows
Built and tested
RVLTION is built, run and used daily on Windows 10 and 11. Capture is event driven: Windows tells RVLTION when the clipboard changes, so nothing runs between copies. It installs per user, needs no administrator, and stores its history in your own profile.
There is no public download yet, and the build is unsigned. Until there is a certificate, the only way to run RVLTION is to build it yourself from source.
macOS
Written, never built
The macOS clipboard backend is written and in the repository. It reads the pasteboard on a short interval, because macOS offers a change counter and no change notification, which is why every clipboard tool on the platform polls.
It has never been compiled or run. This project is developed on Windows, which cannot produce or test a macOS binary, so nothing about macOS has been verified. It would also be unsigned, and an unsigned application is not trusted by Gatekeeper.
Linux
Built and tested
The Linux clipboard backend is written and covers X11 and Wayland sessions separately, because they are genuinely different problems rather than one platform.
Wayland deserves a plain statement rather than a footnote. It is designed to stop a background application reading the clipboard. RVLTION uses the wlr data control protocol, which Sway, Hyprland, river and most wlroots based compositors implement. GNOME and KDE Plasma do not implement it today, so on those sessions capture cannot work at all. RVLTION would report itself unavailable and say why, rather than running and recording nothing. The X11 path is the one that has been exercised; the Wayland path is written and has not been run on a compositor that implements the protocol.
It runs. On Ubuntu 24.04 the backend test suite passes 534 tests, and three artifacts are produced and have each been launched on an X11 session: a release ELF binary, a Debian package, and an AppImage. Each one opened its database, applied its migrations, started capture on the X11 backend, and recorded copied text, URLs and file paths with the same classification Windows gives them. The Debian package installs through apt and registers a desktop entry.
Once it is installed
Three things, and then you forget about it.
- Leave it running RVLTION records what you copy. There is nothing to switch on.
- Carry on working When a run of copies turns out to be about one thing, RVLTION says so.
- Keep what matters A kept connection becomes a Revelation and stays, with the reasons it was found.
System requirements
Modest.
- Operating system
- Windows 10 or later, 64 bit
- Runtime
- WebView2, already present on Windows 11 and on current Windows 10
- Disk
- About 20 MB installed, plus your history, which is a single SQLite file
- Memory
- Under 100 MB while running
- Network
- Not required. RVLTION makes no outbound connections
- Account
- None
Building from source on Windows needs Rust 1.85 or later with the MSVC toolchain, Node 20 or later, and Visual Studio Build Tools with the C++ workload. Build instructions
macOS has requirements on paper only, since no binary has been produced: macOS 12 or later and the Xcode command line tools to build. Linux requirements are real and have been exercised. Building needs the WebKitGTK 4.1, GTK 3 and libayatana development headers. Running needs libwebkit2gtk-4.1-0 and libgtk-3-0, which the Debian package declares as dependencies, or the AppImage, which carries them. On Wayland you also need a compositor implementing the wlr data control protocol. Platform detail