Self-Sovereign Identity
Create and control your own DIDs and Verifiable Credentials. Your identity lives on your device — no platform can revoke it.
Open-Source Decentralized Platform
Community-driven tools for decentralized identity based on W3C standards. DIDs, Verifiable Credentials, IPv6-first peer-to-peer mesh, and DIDComm v2 for decentralized messaging — no central authority required.
The trust triangle (VCs)
W3C Verifiable Credentials involve three roles. The holder sits at the center of control: they receive credentials, store them in a wallet, and choose what to show a verifier.
-
Holder
The person or organization the credential is about. They keep the credential in their wallet, control when it leaves the device, and share only what is needed—often as a verifiable presentation.
-
Issuer
The authority that creates and cryptographically signs the credential. Verifiers check those signatures and policies against the issuer’s published keys and metadata.
-
Verifier
The relying party—an app, service, or gate—that receives a presentation, validates proofs and status (such as revocation), and decides whether to trust the claims.
IPv6-first P2P mesh
Nodes discover each other with libp2p and keep the DID document registry in sync with no central server. IPv6 is the default for peer addressing and reachability; IPv4 remains as a compatibility path for legacy networks, not the long-term design center.
Built on W3C Standards
Implements DID Core, VC Data Model 2.0, and Data Integrity. Interoperable by design.
DIDComm v2
Standard protocol for encrypted, decentralized messaging between DIDs — exchange messages, credentials, and proofs without a central message broker.
Use cases
Concrete experiences the platform enables. Click any card to read the full flow and architecture.
Why a decentralized platform
Decentralized identity spreads trust across peers and standards — not a single company or server.
Always-on availability
Centralized services go down whenever their servers do. Here there is no single point of failure: as long as any node in the network is up — in your area, your region, or the world — the service keeps running.
Control & censorship resistance
Self-sovereign identifiers and credentials stay with the holder. Your digital identity is not the same as a revocable account on one provider.
Interoperability
W3C DIDs and Verifiable Credentials let other systems verify and exchange data without proprietary, closed APIs.
IPv6 over IPv4 by design
A decentralized mesh needs truly reachable peers. The stack treats IPv6 as the primary path for libp2p multiaddrs and discovery, cutting through NAT pain at global scale. IPv4 is still supported, but the architecture assumes IPv4 as a legacy fallback—not the end state of the network.
Sovereignty & deployment
Run your own node, choose your infrastructure, and align with internal policy or jurisdiction — without mandatory reliance on our cloud.
Transparency & trust
Open-source code and public standards mean behavior can be reviewed and audited instead of taken on faith alone.
Platform Modules
Three community-built components that work together as a decentralized network.
Almena
Unified desktop product: the network node (gRPC/REST, libp2p, DID document sync, IPv6-first) and the issuer console ship together—one install instead of separate daemon and desktop shells.
Rust · Tauri v2 · React · TypeScript · tonic · libp2p Wallet
Mobile-first identity wallet for holders. Create DIDs, store credentials, biometric auth, cloud backup, and QR exchange.
Tauri v2 · React · TypeScript CLI
Operator tooling for the node over gRPC: subcommand-first workflows for scripts and CI, plus an optional Ratatui dashboard for peers, storage, and logs when you want a full-screen view.
Rust · clap · ratatui · crossterm Community-Driven, Open Standards
Built in the open by contributors around the world. No vendor lock-in, no paid dependencies. Run your own node, audit every line of code, and help shape the future of decentralized identity.