Elur — You shared it. You still own it.

servers holding your files. There is no vault to breach — or to change hands with the company.

100%

of access events recorded on a public ledger neither party can edit.

act to revoke — every copy, every reader, every agent, everywhere.

∞

your archive's lifetime. Documented format, your key, no dependency on Elur existing.

The difference

Every provider promises they won't read your files. Promises have exceptions.

Data rooms hold your documents and ask you to trust their policy. Their AI indexes what you store. Their servers cache what your counterparties view. Their directories remember every deal you ever ran. Their contracts call your data "entrusted" — because it is. To them.

Elur can't read your files. Not won't — can't. There is no server in the middle. There is no middle.

How it works

Sharing becomes a lease, not a gift.

01 · SEALED

Encrypted on your device

Files are sealed with AES-256 before anything leaves your machine. Store the sealed copy anywhere — your drives, your servers, decentralized storage. Elur never holds it.

02 · GOVERNED

Enforced on a public ledger

The only key sits behind a policy on rails neither party controls. Every open is checked against your rules — expiry, open limits, named identities, view-only — and recorded where no one can edit it. Not even us.

03 · REVOCABLE

Taken back from anywhere

Revoke once and every future open dies — on their machine, in their AI, across the world. Reinstate just as easily: sealed, never lost. No requests, no phone calls, no permission needed.

The Elur application: an ink-navy rail with rooms — Open, Encrypt, Agent access, People, Activity — beside a cream document workspace.

Every room of the data room — except the one where they keep your files.

For the agent era

Everyone is teaching AI agents to remember. We taught them to forget.

Their agents already read everything you send — every term sheet, every contract, forever, with no record and no way back. Elur makes agent knowledge a lease: any agent connects through an open standard, opens documents through your gate, and loses everything the moment you say so.

Grant

Give a counterparty's agent a badge — one act, no files sent, no account needed on their side.

Watch

Every open it makes is signed on the ledger. You know what it read, and when — provably.

Revoke

Kill the badge and every door closes at once. Its next request: ACCESS DENIED.

Side by side

How we compare.

	Elur	Legacy data rooms	Encrypted cloud storage
Encrypted on your device, before anything leaves it	✓	✗	✓
The provider cannot read your files — can't, not won't	✓	✗	✓
Audit trail and per-document permissions	✓	✓	✓
Recipients open documents with no account and no vendor	✓	✗	✗
An access ledger neither party — nor the provider — can edit	✓	✗	✗
AI agents as named identities you can revoke from anywhere	✓	✗	✗
Can recover your documents if you lose your keys	✗*	✓	✓

Short on purpose. The last row is the price of the second — a provider that can't read your files is a provider that can't recover them.
*You can. Your recovery phrase restores everything, on any machine — it just never passes through us.

What we can't do

A security product should tell you its limits before you find them.

We can't erase what was already read.

Revocation kills every future open, everywhere. It cannot reach a memory, a photograph of a screen, or a copy made while access was live. What it changes is the default: keeping your data stops being automatic and becomes a deliberate, recorded act.

We can't see your deals — or sell them.

There is no Elur database of your documents, your counterparties, or your readers. Names you give identities live on your device alone; the ledger holds pseudonyms. Nothing to breach, nothing to sell.

We can't lock you in — or lock you out.

Your vault opens with your key, offline, forever — and the format is documented, so your archive outlives us. If you stop paying, you lose our conveniences, never your property. Billing that can't take hostages.