Nostr signing without private-key sprawl
Diogel protects Nostr keys, secures signing authority, and lets people, apps, teams, and agents sign safely without taking custody of the private key.
Protect your keys
Private keys should not be casually exported to every client. Diogel keeps signing material inside controlled boundaries and returns signatures instead of raw keys.
- Browser protectionPorwr keeps your private keys inside the browser extension. Web apps get signatures, not your key.
- Mobile protectionAndroid keeps keys isolated on your phone. Signing requests are reviewed before approval.
- Team protectionBancwr puts governance around shared signing. Team members never see the private key.
Signing is a controlled operation
Signing should be a deliberate act, not an invisible side effect. Requests are reviewed, permissioned, scoped, and logged where useful.
- Per-site permissionsApprove or reject signing requests per domain and per event kind. Granular control over what gets signed.
- Explicit approval flowsEvery signing request is visible. No invisible side effects, no auto-signing without consent.
- Audit trailsBancwr provides compliance-oriented audit logs so organisations know exactly what was signed and by whom.
Standards-compatible
Diogel fits the Nostr ecosystem — NIP-07 browser signing, NIP-55 mobile signer flows, and Nostr bunker patterns for remote and team-controlled signing.
- NIP-07 browser signingPorwr implements the standard window.nostr interface. Works with any Nostr web app.
- NIP-55 mobile signingAndroid supports modern signer flows for app-to-signer requests on mobile.
- Nostr bunker / remote signingBancwr aligns with the Nostr bunker pattern for server-side and team-controlled signing.
One suite, three products
The Diogel suite solves the same problem at three levels — personal browser signing, mobile signing, and organisational key custody.
Ready to protect your Nostr keys?
Get started with Diogel and keep your private keys where they belong — protected.