Decentralized Identity for Developers

One identity, multiple devices, Git-native storage. Sign commits with a cryptographic identity that lives in your keychain — no servers, no blockchain, no GPG.

Get Started    Read Concepts

• One Identity, Many Devices

  ---

  Create a stable did:keri identity and link your laptop, phone, and CI server to it via signed attestations. Every device signs as you.

  How identity works

• Git-Native Storage

  ---

  Attestations are stored as Git refs — no database, no central server. Your ~/.auths repo is the single source of truth, with offline-first operation.

  See Git layouts

• Verify Anywhere

  ---

  Embed auths-verifier via WASM, FFI, or native SDKs. Verify attestation chains in browsers, CI pipelines, mobile apps, and backend services.

  Explore SDKs

• Key Rotation Built In

  ---

  KERI pre-rotation lets you replace signing keys while preserving your identity. Past signatures remain valid. No key re-distribution.

  Understand rotation

• Cross-Platform

  ---

  macOS Keychain, Linux Secret Service, Windows Credential Manager. Plus UniFFI bindings for Swift and Kotlin mobile identity creation.

  Installation

• AI Agent Governance

  ---

  Provision scoped identities for AI agents and CI bots. Capability attenuation ensures agents never exceed granted permissions. Revoke instantly.

  Agent identities

• 5-Minute Setup

  ---

  cargo install, auths init, git commit -S. Three commands to a signed commit. No key servers, no web-of-trust, no ceremony.

  Try Quickstart

---

Why Auths?

The modern developer workflow is great at code signing but terrible at identity. GPG was designed for email in the 1990s. SSH signing works per-key but doesn't connect devices. Blockchain adds cost and latency you don't need.

Auths gives you a multi-device cryptographic identity backed by Git. Link your laptop, phone, and CI server to one DID. Revoke a lost device in one command. Verify signatures without a network call.

---

How It Works

flowchart LR
    subgraph Identity
        A["auths init<br/><small>did:keri:E...</small>"]
    end

    subgraph Devices
        B["Laptop<br/><small>did:key:z6Mk...</small>"]
        C["Phone<br/><small>did:key:z6MK...</small>"]
        D["CI Server<br/><small>did:key:z6Mn...</small>"]
    end

    subgraph Verification
        E["auths-verifier<br/><small>WASM / FFI / SDK</small>"]
    end

    A -->|"signed attestation"| B
    A -->|"signed attestation"| C
    A -->|"signed attestation"| D
    B -->|"commit signature"| E
    C -->|"commit signature"| E
    D -->|"commit signature"| E

1. Create Identity — Generate an Ed25519 keypair, derive your did:keri, store the key in your platform keychain
2. Link Devices — Each device gets its own did:key, linked via dual-signed attestations stored as Git refs
3. Sign Commits — Git's native SSH signing invokes auths-sign, which loads your key from the keychain
4. Verify Anywhere — Embed auths-verifier (Rust, Python, JS, Go, Swift) to check attestation chains with zero dependencies

---

SDK Support

Language	Binding	Package	Status
Rust	Native	auths-verifier	GA
Python	PyO3	pip install auths-verifier	GA
JavaScript	WASM	npm install @auths/verifier	GA
Go	CGo (FFI)	go get github.com/auths/...	GA
Swift	UniFFI	Swift Package Manager	GA
Kotlin	UniFFI	Gradle	GA

View all SDKs

---

Open Source

Auths is fully open source under the Apache 2.0 license.

View on GitHub