Production services · Identity & access
Faiber Identity
Secure authentication and authorization for production applications.
Faiber Identity centralizes sign-in, account lifecycle, tokens, roles, and permissions so every service can enforce one consistent access model.
Identity & accessFaiber Identity
Domain recordsUsersRolesPermissionsSessions
01Login
02Token
03Policy
04Gateway
01
Feature map
The production behaviors this service owns, expressed as concrete product features instead of generic modules.
Registration, user status, lookup, and password lifecycle
Role-based access control with granular permissions
Token validation, refresh, logout, and one-time credentials
02
Best-fit products
Customer and workforce authentication
Secure authentication and authorization for production applications.
Multi-role SaaS applications
Secure authentication and authorization for production applications.
API and service-to-service authorization
Secure authentication and authorization for production applications.
03
Operational gains
One identity boundary
Faiber Identity centralizes sign-in, account lifecycle, tokens, roles, and permissions so every service can enforce one consistent access model.
Consistent access policy
Faiber Identity centralizes sign-in, account lifecycle, tokens, roles, and permissions so every service can enforce one consistent access model.
Faster secure onboarding
Faiber Identity centralizes sign-in, account lifecycle, tokens, roles, and permissions so every service can enforce one consistent access model.
04
Connected services
UsersRolesPermissionsSessions
Production wiring
How it runs in a Faiber project
Select the capability during deployment. Faiber records the manifest, wires service references, exposes the API boundary, and keeps lifecycle, health, logs, and administration visible in project context.
API boundary
Application code uses the service API or typed SDK contract. Identity, permissions, tenant scope, and project context stay explicit at every read and write boundary.
Manage-ready operations
Faiber Manage opens this service beside the rest of the enabled stack, so teams can inspect records, adjust settings, review health, and ask the Manage agent for guided service changes.
infera-idpSecure authentication and authorization for production applications.
Manage agent
Suspend risky sessions and require OTP for the support-admin role.
I found 2 active sessions and the role policy. I can rotate tokens and enable OTP enforcement.
Ready to speak, explain, and apply safe service tweaks.Technical reference
Service ID:
infera-idpInternal API port: 8002These values support deployment wiring. Product code should use configured endpoints or SDK clients, not hard-coded internal addresses.
FAQ
Questions teams ask before enabling it
What does Faiber Identity add to a Faiber application?
Faiber Identity centralizes sign-in, account lifecycle, tokens, roles, and permissions so every service can enforce one consistent access model.
How is Faiber Identity provisioned?
Select it as a project capability. Faiber records the service manifest, resolves its dependencies, and reconciles it inside the project's isolated Kubernetes namespace.
Can Faiber Identity be used with an existing frontend?
Yes. Faiber Identity exposes a defined API surface and can be integrated from an existing React application or a new Faiber project.
Production services
Works naturally with
User dataFaiber Profiles
View all services 
Faiber Profiles stores structured user information, typed custom properties, visibility rules, and trusted-service data in one queryable profile layer.
NotificationsFaiber Messenger
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
Realtime conversationsFaiber Chat
Faiber Chat owns direct messages, groups, organization channels, memberships, moderation, threads, reactions, read state, realtime events, and durable delivery—while AI turns stay governed by Agentic.
Faiber
Provision the capabilities your product actually needs.
Start with a real project, select services explicitly, and keep code, access, deployment, and operations connected.