cloud_api
Use the official Meta webhook path when the standard integration surface is the requirement.
The same relay still enforces policy, tool exposure, reminders, memory, and outbound governance after the message lands.
Policy-first WhatsApp agent gateway
WhatsApp automation that behaves like infrastructure.
Sentinel Relay sits between inbound messages and agent execution with privacy modes, provider and tool allowlists, durable memory, recurring reminders, background jobs, and a tamper-evident audit chain.
- Meta Cloud API + QR sidecar
- Memory + reminders + background jobs
- Policy gates + audit proof
Diagram showing Sentinel Relay as a central hub processing inbound WhatsApp messages through policy gates, tool execution, provider calls, and durable memory.
Rust runtime
Hash-chained audit logging
Sender-scoped sessions
Hybrid memory retrieval
Background agent queue
Control center API
Adapter surface
One relay, two ways to reach WhatsApp.
qr_sidecar
Use linked-device QR login when you need a practical local bridge without rebuilding the orchestration layer.
QR status, outbound pull, and sidecar authentication stay explicit while the rest of the runtime remains shared.
Governed automation
Built for teams that need control before convenience.
01
Protect the boundary around every tool and provider call.
Sentinel Relay keeps privacy modes, allowlists, signature verification, replay checks, and structured denials inside the runtime instead of hoping prompt text does the job.
02
Keep long-lived conversations operational, not fragile.
Durable memory, recurring reminders, one-shot reminders, and background sub-agents let WhatsApp workflows continue after the first response without losing context.
03
Leave an operator-grade trail behind every action.
The control center, runtime diagnostics, proposal workflows, and append-only audit chain give operators a clean browser surface without turning the public site into the control plane.
Message lifecycle
From inbound text to governed action.
-
01
Receive
Cloud API or QR sidecar hands the message into one consistent gateway.
-
02
Normalize
Sender, replay, and session state are resolved before any model or tool use starts.
-
03
Route
Conversation, retrieval, tool, or background-task mode is selected for the turn.
-
04
Execute
Provider calls and skills only run when policy, provider allowlists, and skill allowlists all align.
-
05
Persist
Memory capture, reminders, and audit events keep the result durable enough for real operations.
-
06
Operate
Operators can inspect posture through the control-center APIs while the public site stays clean.
Sentinel Relay
When the chat surface is simple, the control plane should still be serious.
Build WhatsApp workflows on a relay that remembers context, enforces boundaries, and leaves proof behind.