All Infera servicesNotifications · Infera

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.

Activation depends on account access, configuration, and project resources.

Service capabilities

What can you build with it?

01

Notification send API and delivery records

02

Reusable templates with localized content

03

Channel configuration and recipient subscriptions

04

Scheduling, service registry, and RabbitMQ intake

Made for your product

Start with a clear use case.

Use this service as part of the backend for these products.

  • OTP and transactional alerts
  • Lifecycle and engagement messaging
  • Operational notifications
From setup to use

Choose, connect, and check.

01

Choose the service.

Check account access and the resources needed by your project.

02

Connect your product.

Configure access and connection settings, then use a compatible API or SDK in your code.

03

Review the result.

Test a real user journey and inspect the service and its data in the management panel.

Before you start

Your questions, answered.

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.

Infera

Explore more services.