RVLTION Download

Clipboard intelligence that never leaves your machine

Most clipboard managers remember items.
RVLTION remembers what they were part of.

RVLTION records what you copy, on your device, and notices when a run of copies turns out to be about one thing. You can keep that connection, and find your way back to it later.

Download RVLTION Windows today. Build it yourself, there is no public release.

The timeline

Everything you copied, in the shape it happened.

Not a list. A timeline, with the gaps left in. Select a fragment and RVLTION tells you where it came from. Travel back and everything outside that moment recedes.

A working reconstruction, not a screenshot. Try selecting a row. Demonstration data

The idea

A clipboard history remembers the thing. It forgets the reason.

You can scroll back through everything you copied and still not find what you were doing. The fragments are all there. What is missing is what tied them together.

What did I copy?

  • link
  • link
  • price
  • note
  • note
  • link

A list of things, in the order they happened.

What was I doing?

  • Keychron Q1 Shopping6 items, 17 minutes
  • A product page from amazon.com
  • A foam mod guide from reddit.com
  • Switch compatibility notes
  • One price

One thing you were doing, with the parts still attached.

Discover, then reveal

It waits until there is actually something to say.

Copying ten things in a minute is a burst, not research. RVLTION only raises a connection when the items are about something: a repeated product, a repeated source, a repeated word. When nothing ties them together it stays quiet.

Walk it forward. The evidence shown is the same wording the application produces, and there is no confidence score anywhere in it. Demonstration data

And where it stops

Knowing what does not belong is the harder half.

Anything can group things that were copied close together. What decides whether this is useful is the four answers underneath: joining fragments that share a subject and no words, keeping two neighbouring threads apart, leaving your own writing alone, and admitting when a fragment could go either way rather than guessing.

Four real cases. Each one is checked by a test in the source, so this page cannot claim behaviour the engine does not have. Demonstration data

Keep, and it becomes a Revelation

A kept connection keeps its reasons.

Keep a connection and it persists, remembering why it existed in the first place. What RVLTION found and what you added later stay distinguishable. Removing something from a Revelation does not delete the item, because context and history are different kinds of ownership.

Press Keep this. Notice that a Revelation is not a folder, it is preserved context. Demonstration data

Reconnect

It suggests. You decide.

Weeks later you copy something that looks like it belongs to a Revelation you kept. RVLTION says so, and stops there. It never adds anything on its own, and something you have declined does not come back to ask again.

Try Ignore. Those items stop being evidence for that context permanently. Demonstration data

Find

For when you half remember it.

You usually remember something about the thing: a product name, the site it came from, roughly when. FIND matches on those signals against your local history and tells you why each result is there.

Find in RVLTION

Local, not saved

Try reddit keyboard. The sourdough thread is also from reddit.com and is still not returned, because a domain says where something came from, not what it is about. Demonstration data

Local

Not in the cloud. On your device.

This is not a policy or a setting. There is no HTTP client in the build, and the application's content security policy does not permit an outbound connection.

Local processing

Connections are detected on your machine by deterministic rules: repeated words, repeated sources, timing. There is no model and nothing to train.

No external AI

Your clipboard is never sent to an AI service. RVLTION does not call OpenAI, Anthropic, Google, or any hosted model. It detects and blocks keys for those services so they never reach your history.

Nothing uploaded

No account, no sync, no telemetry, no analytics, no update check that contacts a server. The core product does not need a network connection.

Secrets excluded

Suspected secrets are caught before anything is written to disk. Twelve published token shapes, an entropy check, twenty one protected applications, and the clipboard privacy flags password managers set.

Stated plainly Your history is an ordinary SQLite file in your user profile. RVLTION keeps secrets out of it. It does not encrypt it, and does not claim to. Anyone who can read your user profile can read that file, exactly as with any other local application data. Read the privacy boundary

The loop

Five steps, and only two of them are ours.

  1. DiscoverRVLTION records what you copy, locally.
  2. RevealWhen copies turn out to be about one thing, it says so.
  3. KeepYou decide the context is worth preserving.
  4. RevelationIt persists, with the reasons it was found.
  5. ReconnectLater activity that fits is offered for review.

Keep and review are yours. RVLTION does not add anything on its own.

Platforms

Windows and Linux.

Clipboard access lives in one small layer, so a new platform means writing that layer rather than rebuilding the product. Windows and Linux both run: installed, capturing, with installers built for each. macOS is written and has never been compiled, so it is the one platform where calling it supported would be a lie.

See what is available