Open files others sent you — they unlock on this Mac, only while the sender still allows access.
A .elur file arrives through any channel — email, Drive, USB. It travels safely anywhere: the seal, not the channel, is the security.
No account, no sign-up, nothing uploaded. It unlocks on this Mac, for your eyes.
It reads only while the sender allows — they shared it, they still own it.
Every deal you govern, summed from your own records and the public ledger — documents live and sealed, who can open them, opens this week, and what expires next. Nothing here is stored by us; it's read fresh each time you open this room.
Reading your deals…
Browse the deal by folder and open exactly what's been shared with you. Locked documents still show — so you know what exists — and you can request access in a click. Comment on any open document, scoped to the people who can see it.
No documents loaded. Click “Open a shared room…” and choose a manifest a sender exported for you.
The deal's request list, both directions: documents you need from a counterparty, and documents they need from you — each with a deadline and a review window. Fulfilling a request grants exactly that access, set to expire when the window closes.
The request board and fulfilment are live — fulfilling a request is a real on-chain grant, scoped to expire at the end of the review window. Cross-party delivery of a request (so it reaches the other side's app, and their reply comes back) rides the same encrypted messaging layer as Q&A, which is pending; here the counterparty side is staged so you can see the full flow.
Questions and answers that live behind the same gate as the documents — the same named identities, the same on-chain audit trail, scoped to exactly who should see them. Revoke the deal and the conversation seals with it.
Governed Q&A rides Sui Stack Messaging — Mysten's own SDK — so the conversation inherits the very same key servers, identities and audit trail as your documents instead of bolting on a second system. The catch is purely timing: that SDK currently targets an earlier generation of the stack (Sui 1.45 / Seal 0.9.6), while Elur already runs the current generation (Sui 2.x / Seal 1.1.x). Bridging two generations means dependency gymnastics — a forced Move Registry override — that we won't bake into a product people trust with deal documents.
So we did the honest thing: built a working spike that proves the design end-to-end. The SDK's migration to the current generation is already underway upstream — we'll adopt it the moment it ships, rather than bolt on a hack now. This isn't a feature we couldn't build; it's one we're sequencing behind a dependency and our audit. This is the first build of Elur, and we take on no clients until that audit lands anyway.
The spike runs two custom Ed25519 identities with a gasless reader and exercises the full path: send, receive, and the removal-semantics test — when a member is removed, do they lose thread history? They do, which is exactly the property we want: revoke the deal, the conversation seals. The blocker was the generation mismatch: the SDK needed a Move Registry (MVR) override to resolve against our packages even though packageConfig shouldn't have required it. Payloads are tiny next to documents, so messaging is a natural fit once the versions align — same token = identity + audit, smaller blobs.
Files are encrypted locally, on your machine — they never touch a server, ours or anyone's. Share the sealed copy anywhere, revoke anytime.
It needs your identity to sign. No password to remember — and signing out never loses your files.
Recover access with a phrase instead
Restoring a wallet from its 12-word recovery phrase:
These rules apply to whoever holds the file — and you can revoke everyone, anytime, from this room.
You'll get a sealed file to share however you like — email, Drive, USB. Elur never sends anything.
Every identity that holds a key — people and AI agents alike. Name them here (names live only on this Mac), grant or revoke each on the ledger. An agent is just an identity you can switch off.
Granting and revoking are signed by your identity on the public ledger — sign in to begin. Nothing leaves this Mac unsealed.
Everyone who can open your documents — people and agents. You always know who; the public ledger sees only addresses. Your own access never depends on this list.
An Elur identity is a Sui address, derived from each person's own Google sign-in. The salt that produces it lives behind their login — so no one, not even us, can turn an email into an address without that person signing in first. That's a privacy guarantee, not a shortcut we skipped.
The friendly version we're building — invite a counterparty from inside the deal and have identities exchanged automatically: in-app, no address-copying, no links, no email — rides Sui Stack Messaging, which today targets an earlier generation of the stack (Sui 1.45 / Seal 0.9.6) than Elur runs (Sui 2.x / Seal 1.1.x). We're sequencing it behind that dependency rather than shipping a workaround we'd have to unwind. Until it lands: the other side copies their address from their Elur in one click, or use generate a test identity below to try the whole flow yourself.
Reading the ledger…
No documents yet. Add a folder or a file above — each one is sealed on your Mac and stored on Walrus.
Each document is sealed and governed the moment you add it. Then choose who can open it — a person or an AI agent, same list — up in Who holds a key. An agent is just an identity you can revoke.
Export the manifest above and point your own AI — Claude, Cursor, or any MCP client — at Elur's connector. It opens these documents through the gate as the identity you granted, and the moment you revoke, its next read returns access denied. The agent lives where it already lives; only the key answers to you.
Your governance history, read live from Sui — seals, grants, opens, revocations. Recorded on rails neither party can edit. Not even Elur.
Reading the ledger…
Files are never uploaded or stored by Elur. Access is governed by the sender and revocable anytime — nothing ever leaves this Mac unsealed.
Encrypt, govern, and revoke documents — and the AI agents that read them — live on-chain. Sign in to enter the full app. No wallet, no crypto; gas is sponsored.
Evaluation build for Sui Overflow judges — it runs in your browser so you can try Elur with no install. In production, Elur ships as a native desktop app, where your keys live in your OS keychain and nothing runs in a browser.