A distributed application — no backend, no accounts. The page you are on is the whole thing.
No server, just peers
Your data lives in a signed graph that replicates directly between the people using it. Open this page in a second browser window and the two become peers — the second is talking to the first, not to a server in the middle.
Nothing here yet? That is the point rather than a fault: no server is holding anything for you. What you see is what the peers connected right now are sharing — so start by creating something, and it is yours from the first signature.
Three sides, one graph
- Operator — runs the platform, arbitrates, moderates.
- Client — briefs campaigns, breaks them into tasks, assigns and approves.
- Creator — picks up work and delivers it with proof.
Try it in a minute
- Enter as the operator with 🛡️ Superadmin (demo) — the role that signs everyone else's.
- In a second window, generate a new identity and pick a side.
- Roles are granted by a signature, not a database flag, so keep the operator window open: it is what promotes a newcomer from guest to their side.
The part that matters
An approval here cannot be forged. A delivery stays the creator's own signed record; the verdict on it is a separate signed record, owned by whoever decided it. A creator cannot approve their own work, and a client cannot rewrite what was delivered — tested against a client running tampered code, not just claimed.
Nothing is overwritten
A delivery sent back keeps the verdict that rejected it, reason and all. Delivering again adds a new attempt beside it rather than correcting it, and the payment is a third signed record next to the approval.
So the history still answers what was asked, what came back, why, what changed and what was settled — long after a status column would have forgotten every step but the last.
Evidence, not a link to evidence
Attach the file itself. Its fingerprint is signed into the delivery before anyone judges it, so the record names the file that was accepted — and swapping it afterwards is visible to everyone holding a replica.
Small files ride in the graph and are on the reviewer's device before they look. Larger ones stay on yours and travel straight to whoever asks, which means they are available while you are.
Reviewing in bulk says so
Select several deliveries and decide them in one act, and that act is itself a signed record naming what it covered. Each delivery still gets its own verdict; what the batch adds is the honest part — that they were judged together, which anyone reading later can weigh for themselves.