Passwords and repeated sign-ups
Every new service demands its own account and its own recovery flow.
HummerAuthSystem product · Identity
One HummerID.
All of life and work.
The ecosystem's free public identity: Passkeys, MFA, OAuth/OIDC, SAML, organizations and families, device and consent management. Personal and corporate contexts are strictly isolated.
- 01The owner creates one HummerID and confirms sign-in with a Passkey.
- 02Contexts are created separately: personal, family, professional, corporate.
- 03Third-party apps add 'Sign in with Hummer' via OAuth/OIDC.
- 04The organization connects its corporate IdP via SAML and SCIM.
- 05Devices, sessions and consents are visible and revocable in one click.
Identity — HummerAuthContexts are isolatedPortable Profile — only with consent
Hover or focus a node to see its role. One HummerID serves four contexts; data never mixes between them.
Where sign-in breaks
More accounts than systems
Identity today is smeared across dozens of services: each with its own password, consents and access history.
Personal mixes with work
One account serves both personal and corporate tasks — data boundaries are nominal.
Consents are impossible to audit
Who was granted what is impossible to recall: revocation screens are scattered across services.
Companies rebuild sign-in from scratch
Every product re-implements OAuth, roles, invitations and corporate federation.
A public IdP
A public IdP and the ecosystem's branded sign-in
HummerAuth is a free public identity provider. It serves HummerTech products and is available to third-party apps as a standard OAuth/OIDC provider.
- One ID. a personal identity that belongs to the person, not a company
- Context isolation. personal, family, professional and corporate perimeters are separated at the data level
- Passkeys by default. passwordless sign-in, with MFA and risk scoring layered on top
- Organizations and families. invitations, roles, delegation and offboarding without losing history
- Consent center. one list of granted permissions with terms and a revoke button
- Portable Profile. preferences move between products only with explicit consent
What's in Auth
What HummerAuth includes
System product modules available to every other product in the ecosystem.
HummerID
Personal identity and the owner's profile.
Organizations & Families
Organizations, families, invitations and roles.
Passkeys / MFA
Passwordless sign-in, second factor and recovery.
OAuth / OIDC
Standard sign-in for third-party apps.
SAML · LDAP · SCIM
Federation and account provisioning.
Consent Center
One center for consents and revocation.
Devices & Sessions
Device list, active sessions, remote sign-out.
Developer Console
App registration, keys, redirect URIs.
Risk Engine
Sign-in risk scoring and adaptive requirements.
Portable Profile
Portable preferences, by consent.
Three sign-ins
What it looks like in real life
Three short scenarios: an individual, a company and a third-party developer.
01
A person creates a HummerID
A Passkey is created on the first device; the second is confirmed by QR sign-in. From then on, all ecosystem products open without a password.
02
A company onboards employees
The organization is created from the corporate IdP; roles and groups arrive via SCIM. Employees' personal contexts stay inaccessible to the employer.
03
A service adds 'Sign in with Hummer'
The developer registers an app in the Developer Console, gets a client_id and wires the standard OIDC flow. The user sees the requested permissions before consenting.
The corporate directory
The source of truth stays with you
HummerAuth does not supplant the corporate directory. The organization keeps managing employees in its IdP, and HummerAuth receives that data and follows it.
Left — sources of truthRight — identity consumers
Employee credentials stay in the corporate directory. HummerAuth receives roles and statuses but never becomes their owner.
Corporate IdPLDAP / Active DirectorySCIMHR systemsThird-party OAuth appsDevice Passkey providers
The agent and credentials
Native AiHummer and compatible providers
Integration depth differs — and the page says so plainly.
AiHummer in HummerAuth
AiHummer gets no access to credentials. The agent acts on the user's behalf within granted permissions and confirms significant actions with a human.
- The agent acts within a role and context — not 'as the administrator'
- Every agent action is recorded in the Hummer Proof access log
- Switching context instantly changes the data available to the agent
Third-party agents and models
Third-party apps and agents connect as ordinary OAuth/OIDC clients: they request a minimal set of permissions, see only permitted scopes and are revocable by the owner from the Consent Center.
Routing goes through the AI Gateway, permissions through Hummer Trust. Setup takes extra work, and access to context and actions is limited by the organization's policies.
Connect your own agentThe security perimeter
What an app sees and how it deploys
Identity, connections, permissions, confirmations and deployment — the ecosystem's shared mechanisms applied to this product.
Contexts in HummerAuth
A context is a boundary of data and permissions. It is chosen explicitly, shown in the interface, and defines which connections, memory and agents are available.
PersonalFamilyProfessionalCorporate
How HummerID worksConnect once
HummerAuth answers who you are; the Connection Vault answers what you can access. A connection is made once and reused by all products within the context's boundaries.
The owner sees the list of connections, scopes and terms, can narrow the data volume and revoke access in one click.
Connection Vault in FabricMinimal permissions
An app gets exactly what it requested and the owner confirmed.
Transparent consents
A list of granted permissions with term, source and a revoke button.
Access log
Who accessed the data, when, and from which app.
Perimeter separation
The personal context is inaccessible to the employer; the corporate one stays off personal devices by policy.
Формат поставки
The public HummerID runs as a cloud service: sign-up, Passkeys, devices and consents are available right after launch. Free for individuals.
An organization can deploy a HummerAuth Business perimeter in its own infrastructure: its own policies, its own log retention, federation with the internal IdP.
Personal HummerIDs stay in the public perimeter; corporate accounts and policies stay on the organization's side. The perimeters link by federation, not by copying data.
What's nearby
What HummerAuth works alongside
Products are independent. Your HummerID, connections, agents and settings move with you.
Soon
HummerHome
The entry point to all products after sign-in.
OpenSoon
HummerPortal
External parties get access through the same HummerID.
OpenSoon
HummerEnterprise
Corporate IdP, policies and multi-entity structures.
OpenSoon
HummerStore
Extensions request permissions through the Consent Center.
OpenSecurity
The full model of permissions, confirmations and audit.
OpenDevelopers
App registration and wiring 'Sign in with Hummer'.
OpenSoonNo public launch announced. HummerID registration opens with the ecosystem's first product.
Add Hummer sign-in to your product
We are building a list of pilot apps and organizations that need single sign-on, isolated contexts and clear consents. Applying commits you to nothing.
Powered byHummerTechThe mandatory master-brand badge
Application
Tell us about your task — we will get back with an answer and pilot details.
Request received
We will get back to you at the address provided. If it is urgent, write to info@hummer-tech.ru.