Introduction

The communication layer for PostgreSQL applications.

Efelant Core runs entirely in PostgreSQL. It is a standalone messenger and an embeddable conversation / activity-feed layer. There is no Node, Nest, Express, FastAPI, Redis, or Kafka in Core. REST and gRPC for third-party apps are PostgreSQL extensions that call the same SQL functions.

Clients synchronize with conversation_id + last_sequence. LISTEN/NOTIFY only wakes the client. Message bodies are encrypted on the device. Private keys never leave it.

Product

Features

Same core, several shapes — not separate products.

Function API

Stored functions + RLS. efelant_app has no table DML.

Tenants & contexts

Attach chat to type + external_id without importing host tables.

Durable events

Status and messages share one per-conversation sequence.

Presence

Online means the app is heartbeating, not “a session still exists.”

Embed SDKs

Flutter, Stencil, JS. No React layer. Token catalog instead of Storybook.

REST / gRPC

Background workers in Postgres. Same authorization as SQL.

What this is not yet

Local / single-tenant preview is usable. B2B production is not. The Flutter app can set the host. It has no tenant switcher, invites, or SSO. E2EE is a first step, not a Double Ratchet. See readiness.