Relay has a substantial backend, native iOS client, public API contract, and developer documentation. The remaining work before beta is deploying and production-proving the multi-user messenger. 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

​
Built and available

The developer preview availability matrix lists the current API surface in detail.

​
Open proof gaps

​
The first release gate

The first credible release is an invite-only beta for roughly 20–50 people. It requires all of:

Identity

Working phone authentication and account deletion.

Agents

A few dependable curated agents with explicit installation and removal.

Conversation

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

Operations

Production push, blocking, reporting, privacy, support, monitoring, backups, automated core-path checks, and TestFlight distribution.
The user gate is simple to state and hard to prove:
A new user can install Relay, verify their phone, add and message a useful agent, receive replies and notifications, go offline, relaunch or reinstall, and recover the exact same conversation without assistance.
The developer gate is equally concrete:
A developer can create an agent, copy its one-time token, receive a message event, return a finalized reply or supported native stream, and see the user receive one canonical message by following the public docs exactly.

​
Deliberately later

Proving the reliable text relationship comes first. These are intentionally out of scope until it holds: an open marketplace, payouts and subscriptions, automatic routing, production voice and video calls, payments, location, general interactive cards, and Android.

​
See also