All blog posts
Updates 2 min read

Commonveil 0.17.0: Commonveil Identity

Commonveil 0.17.0 records commonveil Identity. Here is the project history, technical detail and reasoning behind the update.

By Comutability Published Update from

Historical Commonveil release, 6 November 2026. Based on the project's official versioned release record. This does not establish an independent cryptographic audit.

Commonveil 0.17.0 records commonveil Identity. Here is the project history, technical detail and reasoning behind the update.

Why this update matters

Commonveil Identity changes the centre of trust from an email inbox to keys, trusted devices and explicit recovery methods. Users can sign in with passkeys, approve unfamiliar browsers and manage devices from settings. This reduces dependence on an external email provider, but also makes clear recovery instructions and responsible key storage more important.

What changed in version 0.17.0

The official release notes recorded the following changes. These describe the version at the time, and later releases may have replaced, improved or removed particular mechanisms.

  • On self-hosted sites, accounts are a username and password, with no email.
  • Sign in with a passkey, kept on one device or synced by a password manager.
  • A browser signing in for the first time is confirmed with a passkey, your recovery phrase or private key, or from a device you're already signed in on. Signed-in devices are listed in settings, where you can disconnect any of them.
  • Your private key is your recovery phrase written as one string: either proves the account is yours. Getting back in takes one of them, or a passkey.
  • Accounts made with an email still work, and are asked to add a passkey and confirm their phrase before email sign-in goes away.

How this fits the wider Commonveil direction

Comutability's wider aim is useful, accessible technology that gives people more control. For Commonveil that means encrypted communication, meaningful user permissions and the option to run a site independently. We also need to keep a clear boundary between what the project records as implemented, what has been tested and what still needs expert review.

The detailed release notes above provide a starting point for members and contributors to test the behaviour, read the documentation and challenge assumptions.

What to check next

Continue helping people understand backup and recovery without creating hidden administrator backdoors.

Original sources

Sources and further reading

Explore the evidence and original project records behind this article.