Production services · Notifications
Faiber Messenger
Template-driven notifications across channels and product events.
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
NotificationsFaiber Messenger
Domain recordsTemplatesChannelsRecipientsDeliveries
01Event
02Template
03Channel
04Delivery
01
Feature map
The production behaviors this service owns, expressed as concrete product features instead of generic modules.
Reusable templates with localized content
Channel configuration and recipient subscriptions
Scheduling, service registry, and RabbitMQ intake
02
Best-fit products
OTP and transactional alerts
Template-driven notifications across channels and product events.
Lifecycle and engagement messaging
Template-driven notifications across channels and product events.
Operational notifications
Template-driven notifications across channels and product events.
03
Operational gains
Consistent message templates
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
Channel-independent delivery
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
Auditable delivery history
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
04
Connected services
TemplatesChannelsRecipientsDeliveries
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-messengerTemplate-driven notifications across channels and product events.
Manage agent
Enable the payment-success SMS template for Persian users and schedule a retry policy.
The localized template exists. I can activate it and set delivery retries for the payment event.
Ready to speak, explain, and apply safe service tweaks.Technical reference
Service ID:
infera-messengerInternal API port: 7030These 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 Messenger add to a Faiber application?
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
How is Faiber Messenger 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 Messenger be used with an existing frontend?
Yes. Faiber Messenger exposes a defined API surface and can be integrated from an existing React application or a new Faiber project.
Production services
Works naturally with
Identity & accessFaiber Identity
View all services 
Faiber Identity centralizes sign-in, account lifecycle, tokens, roles, and permissions so every service can enforce one consistent access model.
AutomationFaiber Flow
Faiber Flow registers endpoint events, evaluates conditions, renders payload templates, gates downstream actions, and preserves run and step history for observable product automation.
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.