Identity for people, workloads, and AI agents
One platform for single sign-on over SAML 2.0 and OpenID Connect, network and infrastructure access, device trust, and workload identity, now in development. Every AI agent gets its own identity and is tied to the person it acts for.
Everything you expect from an identity platform. Bring your own identity provider or use ours.
Single sign-onApps over SAML 2.0 and OpenID Connect.
Network accessPrivate networks per person and device, no VPN.
Infrastructure accessShort-lived SSH, Kubernetes, and Postgres access.
Workload identityServices and CI jobs without stored secrets.
ProvisioningSCIM accounts that follow joiners and leavers.
Passkeys and MFAPhishing-resistant sign-in, hardware keys included.
Device trustAccess from managed devices only.
Audit and reviewsEvery access logged, and reviewed.
Every AI agent gets an identity of its own. It acts for one person, from one device.
- Narrowed to the task
Each token names the person, the device, and the tools it may call. It lasts 5 minutes.
- Signed twice
Hemmer signs against your policy. Your edge checks every claim again and countersigns.
- Revoked by either side
Revoke a person, an agent, a device, or a key, and its tokens stop verifying.
Your identity keys stay yours. Only your admins can sign a change to them.
- Two teams to widen
A new admin, signing key, or identity provider needs approval from two of your teams.
- A day to object
Each change that widens access waits 24 hours on your edge's clock, and any admin can veto it.
- One admin to narrow
Removing a key, an admin, or a domain needs only one admin.
- Recovery without Hemmer
Any two of three offline recovery keys restore control. Hemmer holds no copy.
Questions
Where Hemmer is today, and what it works with.
Google WorkspaceSign-in, directory sync, and SCIM
Microsoft Entra IDSign-in, directory sync, and SCIM
OktaSign-in, directory sync, and SCIM
macOSDevice trust through your MDM
When can we use Hemmer?
Not yet. Hemmer is pre-prototype: the specs are drafts and the core libraries are built. The services come next.
Do we have to replace our identity provider?
No. Bring Google Workspace, Microsoft Entra ID, or Okta, and Hemmer follows its directory. Or keep your people in Hemmer's own directory.
Which devices are supported?
Macs enrolled in your MDM come first, with keys in the Secure Enclave. Windows and Linux aren't supported yet.
What does Hemmer see about our people?
Agent tokens carry opaque IDs, never names or emails. Profiles are encrypted to a key your organisation holds.
Can we review the design?
Yes. The specs go out for outside review before the code is public. Ask for them when you request early access.