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 topSecurity-focused CIAM / OAuth-compatible
Customer identity built for what happens after login.
M7 Identity is a security-focused CIAM platform for custom applications and federated services. It provides an OAuth-compatible integration path and an M7-aware hardened profile for customer identity, renewable sessions, and lifecycle control.
Customer identity lifecycle
-
01
Register and authenticate
Create customer accounts, establish identity, and begin a renewable session.
-
02
Protect the renewable session
Maintain session authority through validation, rotation, and controlled renewal—not login alone.
-
03
Close and recover
Handle logout, revocation, recovery, and offboarding through one versioned lifecycle contract.
Designed for custom applications
Manage the customer identity lifecycle
Bring registration, profiles, sign-in, sessions, recovery, and account closure into one product boundary.
Integrate with OAuth-based applications
Use the supported OAuth-compatible path, or adopt the M7-aware profile when stronger session controls matter.
Keep application policy with the application
M7 establishes identity and session authority; each application controls routes, objects, tenants, permissions, and business rules.
Security focus
Login starts the session. Security has to survive everything after it.
M7 focuses on lineage-scoped session authority, cryptographic continuity, controlled renewal, and explicit closure and recovery across application boundaries.
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.