Kanidm is a self-hosted identity management server written in Rust. It aims to be the whole identity provider for a small lab or a large organisation: one deployment that speaks OAuth2/OIDC, RADIUS, a read-only LDAP gateway and SSH key distribution, so you do not have to bolt Keycloak, FreeRADIUS and a directory server together yourself. Its stated goal is strict defaults and self-healing components rather than a long configuration checklist.
Kanidm positions itself against OpenLDAP and 389 Directory Server (which are directories only), FreeIPA (which bundles LDAP, Kerberos, DNS and a CA), and Keycloak (an OIDC provider that still needs a directory behind it). The project’s own benchmarks with 3000 users and 1500 groups report roughly three times faster searches and five times faster writes than FreeIPA, and it advertises two-node replication instead of FreeIPA’s heavier topology. If you only want a small LDAP server with a web admin page, LLDAP is the simpler choice; Kanidm’s advantage is the built-in OAuth2/OIDC side of the house.
The documented evaluation path is a single container: pull the kanidm/server image, write a server.toml with a domain and a matching https origin, run kanidmd cert-generate to create the TLS chain, then start the server with a data volume mounted at /data. The admin and idm_admin passwords are printed by kanidmd recover-account, and the web UI answers at /ui. Because WebAuthn is tied to the origin, HTTPS is mandatory and the origin in the config has to match the hostname you actually browse to. Sample users, groups and OAuth2 clients can be seeded from JSON or hjson files in a migrations directory, which is handy for evaluating the flow before you import anything real. A production install follows the same shape with persistent TLS certificates and a backup job.
Kanidm is opinionated and moves fast: the configuration format, the API and the schema change between minor releases, so read the release notes before upgrading. Administrative work is still mostly CLI, and the web UI is meant for users rather than admins. Running it needs a hostname you control plus a reverse proxy or valid certificates, which is more setup than a single-binary password manager-style tool. For passkey-only shops that want something lighter, Pocket ID covers the OIDC provider role with far less surface area.