Production services · Realtime conversations

Faiber Chat

Production messaging for people, teams, channels, and governed AI.

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.

Ready to provisioninfera-chat8075
Realtime conversationsFaiber Chat
Domain recordsChannelsMessagesMembersReceipts
01Thread
02Message
03Realtime
04Receipt

01

Feature map

The production behaviors this service owns, expressed as concrete product features instead of generic modules.

01

Direct, group, channel, and governed AI conversations

02

Replies, threads, edits, deletion, reactions, and receipts

03

Membership roles, moderation, and tenant isolation

04

SSE realtime events and transactional outbox delivery

02

Best-fit products

In-app customer messaging

Production messaging for people, teams, channels, and governed AI.

Team and community channels

Production messaging for people, teams, channels, and governed AI.

AI conversations grounded in product knowledge

Production messaging for people, teams, channels, and governed AI.

03

Operational gains

Durable conversation state

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.

Tenant-safe realtime delivery

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.

Governed AI handoff

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.

04

Connected services

AgenticKnowledgeProfilesMessenger
ChannelsMessagesMembersReceipts

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

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.

OPS

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.

Faiber ChatLive operating surface
infera-chatProduction messaging for people, teams, channels, and governed AI.
Direct, group, channel, and governed AI conversations
Replies, threads, edits, deletion, reactions, and receipts
Membership roles, moderation, and tenant isolation
Manage agent

Open a support channel, enable moderation, and show unread delivery state.

The channel can be created with tenant membership, moderation rules, and realtime read receipts.
Ready to speak, explain, and apply safe service tweaks.
Technical reference
Service ID: infera-chatInternal API port: 8075

These 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 Chat add to a Faiber application?

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.

How is Faiber Chat 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 Chat be used with an existing frontend?

Yes. Faiber Chat exposes a defined API surface and can be integrated from an existing React application or a new Faiber project.

Faiber

Provision the capabilities your product actually needs.

Start with a real project, select services explicitly, and keep code, access, deployment, and operations connected.