Manage customer identity
Handle registration, sign-in, renewable sessions, and recovery while keeping application policy under your control.
01 / The machinery
Back to topThree pillars. One foundation.
M7 brings Identity, Active Tags, and federation together on one shared foundation without requiring the whole stack. Use what you need. Keep what works. Add more only when it earns its place.
Three independently useful capabilities
Modular by design
Use one. Combine several. Keep control.
Each M7 layer is built to work on its own and connect cleanly with the others. Use one, snap several together, and keep the rest of your stack on your terms.
02 / M7 Identity
Back to topGeneral-purpose IdP / Human + machine auth
One identity provider for people, machines, and every tenant.
M7 Identity is a general-purpose identity provider for custom applications, organizations, and federated services. It combines OAuth 2.0 and OpenID Connect integration with multi-tenant identity, explicit human and machine principals, renewable sessions, and lifecycle control.
Identity and access lifecycle
-
01
Establish the principal
Authenticate a person, application, service, or device and issue credentials for the intended tenant and audience.
-
02
Sustain trusted access
Renew and validate session or machine authority with scoped tokens, rotation, binding, and explicit policy.
-
03
Revoke and recover
Inspect, revoke, close, recover, and offboard credentials and identities through explicit lifecycle controls.
Designed for connected systems
Separate control and member identity
Manage organizations, members, groups, applications, and tenant-local policy while keeping each identity in its intended security context.
Keep every principal explicit
Use interactive OAuth and OpenID Connect flows for people and client credentials for service-to-service access, each governed by its own rules.
Connect applications and services
Combine discovery, PKCE, device authorization, dynamic client registration, and M7-aware session controls across custom systems.
Security focus
Authentication starts an identity lifecycle. It does not define the whole system.
M7 keeps principal type, organization context, audience, scope, binding, renewal, revocation, and recovery explicit across human and machine access.
04 / Federation and adoption
Back to topBuild what you want. Keep what you build.
M7 is designed for independent operators, not platform tenants. Use services others provide, offer capabilities of your own, and keep ownership of the products and customer relationships you create.
M7 services
Start with what helps.
Adopt one M7 service without moving the rest of your stack.
- Product fit
- One useful M7 service
- Required boundary
- Choose the capability you need while keeping the rest of the application stack in place.
Your existing service
Bring your own service.
Federate a capability you already own and operate.
- Product fit
- Existing service + federation
- Required boundary
- The service remains independently operated and implements the supported federation and identity contracts.
A larger product
Assemble the product.
Connect M7 services, your services, and capabilities operated by others.
- Product fit
- M7 + independent capabilities
- Required boundary
- Each service keeps its own operating, identity, authorization, and business-policy boundaries.
A capability others need
Let others use what you build.
Set access terms while retaining ownership and operation of the capability.
- Product fit
- Builder capability + federation
- Required boundary
- Provider discovery, commercial terms, billing, and settlement remain under development.
Keep building through what comes next
We intend to earn your business, keep it, and stand behind what we build. Exact support, maintenance, migration, and continuity commitments still need to be defined.