Current status

The iOS app ships through TestFlight and is not on the App Store. Signing up at relayapp.im normally grants access right away; a set number of people are let in each day, and anyone past that is emailed when there is room. The developer API is open to anyone holding an Agent Token. Live service status is at status.relayapp.im. What ships next is on API availability. Route existence, local implementation, and a real user outcome are three different levels of proof. Every status claim in these docs uses one of the labels below.

Status labels

	Label	Meaning
✅	Production-proved	The complete user and backend flow has passed in the named production environment.
🔵	Available in developer preview	The public route and schema exist. Not a claim about the consumer flow in production.
⚠️	Proved locally	Implementation and local or simulated checks pass. Not shipped.
⏳	Coming later	Specified or intended, unavailable in the current public product.

Built and available

	Area
✅	Postgres-backed stored messages with ordered typed parts
✅	Transactionally assigned message ordering, and idempotent writes keyed by the client-minted `message_id`
✅	One durable event log per participant, surviving restarts
✅	Consumer sync and WebSocket routes
✅	Native iOS inbox, conversation, onboarding, profile, composer, and notification paths
✅	Phone sign-in with a one-time code
✅	Attachments, voice memos, link previews, reactions, and groups
✅	Agent creation with a one-time Agent Token, plus rotation, on Better Auth’s api-key plugin
✅	Blocking, reporting, and account deletion
✅	Versioned REST API, OpenAPI contract, and public documentation
✅	Production API and documentation domains
✅	Public status page with API, Agent runtime, website, and documentation monitors
✅	TestFlight distribution and its release automation
✅	Public quickstart proved end to end against production: fresh agent, signed webhook, receive-and-reply, idempotent retry (July 26, 2026)

Every new account starts with @relay, the agent Relay operates. Every other agent is one a person creates or installs. API availability lists the current API surface in detail.

Open proof gaps

	Gap
⚠️	Local SQLite persistence and cursor recovery, pending physical-device recovery proof
⚠️	Viewport-gated durable Read queues on iOS and Desktop, pending shipped client proof
⏳	Production backups and the full automated core-path release proof
⏳	The public agent roster is small, so a new account sees few agents to install
⏳	App Store review and distribution beyond TestFlight

The gate for open distribution

Leaving TestFlight for open distribution requires all four of these:

Identity

Phone sign-in and account deletion, both proved in production.

Agents

Enough dependable agents that a new account has something to install.

Conversation

Reliable text threads, local persistence, cursor recovery, and visible send states.

Operations

Push, monitoring, backups, automated core-path checks, and App Store review.

The user gate:

A new user completes setup without help. They install Relay, verify their phone, and message a useful agent. They can then reinstall and recover the same conversation.

The developer gate:

A developer follows the public docs without help. They create an agent, receive an event, and send one stored reply.

Start here

Send

Receive

Connect what you already run

Reference

Relay for Business

About Relay

Current status

Status labels

Built and available

Open proof gaps

The gate for open distribution

Identity

Agents

Conversation

Operations

See also

​Status labels

​Built and available

​Open proof gaps

​The gate for open distribution

Identity

Agents

Conversation

Operations

​See also

Status labels

Built and available

Open proof gaps

The gate for open distribution

See also