ThunderID is a lightweight, open-source IAM stack built to secure access for humans, AI agents, and machines.
Designed for the agentic era, ThunderID provides a developer-first IAM stack and supporting tools for securing applications, APIs, services, and agent-driven workflows. It works across traditional and decentralized identity ecosystems, with post-quantum-ready security built in from the start.
Core design goals of ThunderID include:
- Agent-native identity: Manage AI agents as first-class identities with delegated authority, consent-aware access, traceability, and support for issuing verifiable credentials to agents. ThunderID also aims to expose IAM capabilities through interfaces that agents can use safely and programmatically.
- Post-quantum-safe by design: Build on a crypto-agile foundation where algorithms, key types, signing methods, and token protection mechanisms can evolve over time, including support for post-quantum-safe algorithms and hybrid transition approaches across key management, credential issuance, assertions, and secure service-to-service communication.
- Decentralized identity: Bridge the adoption gap for relying parties by making it practical for service providers to consume, verify, and trust decentralized identity in real-world applications, including DIDs, verifiable credentials, digital wallets, trust registries, and issuer-verifier-holder interaction models.
- Lightweight runtime with GitOps support: Provide a lightweight, containerized runtime that can run across on-premises and cloud environments, with declarative identity flows, policies, and configuration suitable for automation, versioning, and GitOps practices.
Getting Started
Get started by exploring how ThunderID can be used to secure:
- Applications - by following Securing B2C Application Guide
- AI Agents - by following Securing AI Agents Guide
- MCP - by following Securing MCP Guide
To learn more about overall requirements, solution patterns of these scenarios, refer to the Use Cases section.
Visit Get ThunderID to learn more about installation methods.
Architecture
Features
-
Identity Management
- Humans, AI agents, and machines as first-class identity types
- Hierarchical organizational units (OUs) and groups
-
Standards
- OAuth 2.1 and OpenID Connect, with PAR and PKCE
- Verifiable Credentials — OpenID4VCI (issuance) and OpenID4VP (verification)
- WebAuthn / passkeys
- IdP federation — Google, Microsoft, GitHub, and any OIDC or SAML provider
-
Decentralized Identity
- Issue Verifiable Credentials to user wallets from configurable credential templates
- Verify presented credentials against presentation definitions and trust anchors
- Use them on their own, or as part of an identity journey
-
User Journeys
- Login, registration, and recovery defined as journeys
- 20+ built-in executors - password, passkey, OTP, social login, consent, and more
- Orchestratable in the server or the application
- Themeable end-user UI
-
Authorization
- Hierarchical resources with derived permissions
- Role-based access control across users, agents, and applications
- Consent management with user-facing review
-
Developer Experience
- Console UI, REST APIs, and SDKs
- MCP server for managing and querying IAM from AI agents
-
Declarative and GitOps-Ready
- YAML resource definitions for every entity
- Immutable runtime
Conformance
Contributing
Please refer to the Contributing Guide for the different ways to contribute to this project and the relevant guidelines.
For code contributions, refer to the Contributing Code section for details on the prerequisites and instructions for running ThunderID in development mode.
License
Licenses this source under the Apache License, Version 2.0 (LICENSE), You may not use this file except in compliance with the License.