(03) Events and messagingIn development

Relay

Every message accounted for.

(01) Communicate

Relay takes an event from your product and gets it to the right person, service, device or AI agent, on the right channel and at the right time, within consent rules. It handles retries, failover and preferences, and keeps a record of what happened to every message, including the ones it chose not to send and why.

(02) The question

“How does this event or message reach the right person, service, device or agent?”

(03) Principles

  1. 01

    One entry point

    Send events through one API or as CloudEvents. Idempotency and deduplication keys prevent accidental double sends.

  2. 02

    Right channel, right time

    Fallback, escalation, quiet hours and the recipient's time zone are handled for you, without code in your product.

  3. 03

    Consent in the send path

    Preferences, legal consent, one-click unsubscribe and country rules are checked before every send, and a send is skipped when a check fails.

  4. 04

    A reason for every skip

    When a message is not sent, Relay records why and which rule decided it. “Why didn't I get it?” has an answer.

  5. 05

    Replies that find their way back

    Messages stay in the inbox or mailbox even if a push is lost, and replies are matched on whichever channel they arrive.

(04) Capabilities

Channels

  • iOS, Android and web push
  • Email through providers or your own SMTP
  • SMS and voice codes
  • WhatsApp, Slack, Microsoft Teams, Telegram and Discord
  • In-app inbox with real-time updates

Workflows

  • Visual editor, files in git, or code
  • Wait, digest, throttle and conditions
  • Fallback, fan-out and last active device
  • Escalate unless seen
  • Scheduling and recurring notifications
  • Topics and subscriptions

Reliability

  • At-least-once delivery with durable idempotency
  • Retries with backoff and circuit breakers
  • Provider failover to verified providers only
  • Priority lanes so security codes are never shed
  • Fair limits per customer
  • Dead-letter queue and replay

Consent and compliance

  • Message classes from security to marketing
  • Preference center by category and channel
  • Turkey's İYS consent registry
  • One-click unsubscribe
  • Country rules for Turkey, the EU and the US
  • Crypto-shredding for personal data erasure

Content

  • Versioned templates per channel and language
  • Templates that never run code
  • Responsive email layouts
  • Brands, including per customer
  • Previews and test sends

Webhooks and insight

  • Signed webhooks
  • Delivery to queues, streams and object storage
  • Embeddable webhook portal
  • “Why didn't I get it?” lookup
  • Delivery funnel reports
  • OpenTelemetry tracing

(05) Agent-native

Agents can ask a person a question and wait for the answer without holding a process open. Relay holds the wait and hands the answer back.

  • Waitpoints that resolve from any channel
  • Notify, question and review messages
  • Durable agent mailbox, read in order
  • Wake-up signals for sleeping agents
  • Escalation chains that never auto-approve
  • MCP, A2A and AG-UI support

(06) Standards and protocols

  • CloudEvents
  • Standard Webhooks
  • APNs
  • FCM
  • Web Push
  • SMTP
  • WebSocket
  • Server-Sent Events
  • RFC 8058
  • OpenAPI 3.1
  • AsyncAPI 3
  • MCP
  • A2A
  • AG-UI
  • OpenTelemetry

(07) At a glance

Delivery
At-least-once with durable idempotency
Built with
Elixir, OTP and Phoenix
Requires
PostgreSQL and Valkey
Regions
Separate installations for Turkey, the EU and the US
SDKs
Server, iOS, Android, React Native and Flutter, plus inbox components
Long waits
Up to 90 days, stored durably

(08) Works with

(09) Questions

What is suiss Relay?

Infrastructure for notifications, messaging and event delivery. It sends over push, email, SMS, chat apps, in-app and webhooks, with consent rules, retries and a record for every message.

How does Relay handle consent?

Every send passes one decision layer that checks message class, preferences, legal consent including İYS, country rules and quiet hours. If a check fails, the message is skipped and the reason is recorded.

Can AI agents use Relay?

Yes. Agents can ask a person and wait for the reply, read a durable mailbox after waking up, and connect over MCP and A2A.

Is Relay available?

Relay is in development.