> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relayapp.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Current status

> What Relay can prove today, what the developer preview exposes, and what must work before beta.

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

|     | 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 canonical messages with ordered typed parts                                                                              |
|  ✅  | Transactionally assigned message ordering and idempotent writes                                                                          |
|  ✅  | Durable user and agent event logs                                                                                                        |
|  ✅  | Consumer sync and WebSocket routes                                                                                                       |
|  ✅  | Native iOS inbox, conversation, onboarding, profile, composer, and notification paths                                                    |
|  ✅  | Live text and model responses                                                                                                            |
|  ✅  | Agent creation with a one-time Agent Token, plus rotation                                                                                |
|  ✅  | Versioned REST API, OpenAPI contract, and public documentation                                                                           |
|  ✅  | Canonical production API and documentation domains                                                                                       |
|  ✅  | 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) |

The [developer preview availability matrix](/roadmap) lists the current API
surface in detail.

## Open proof gaps

|     | Gap                                                                                                                                                                                   |
| :-: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|  ⏳  | Production phone OTP, blocked until Twilio is fully activated                                                                                                                         |
|  ⚠️ | Local SQLite persistence and cursor recovery, pending physical-device recovery proof                                                                                                  |
|  ⚠️ | Attachments, voice memos, link previews, reactions, discovery, installation, removal, blocking, reporting, and account deletion: implemented, pending deployment and production proof |
|  ⏳  | Production push, monitoring, backups, and the full core-path release proof                                                                                                            |
|  ⏳  | A new production user may still see an empty public agent roster                                                                                                                      |

## The first release gate

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

<Columns cols={2}>
  <Card title="Identity" icon="phone">
    Working phone authentication and account deletion.
  </Card>

  <Card title="Agents" icon="robot">
    A few dependable curated agents with explicit installation and removal.
  </Card>

  <Card title="Conversation" icon="messages">
    Reliable text threads, canonical streaming finalization, local persistence,
    cursor recovery, and visible send states.
  </Card>

  <Card title="Operations" icon="shield-check">
    Production push, blocking, reporting, privacy, support, monitoring, backups,
    automated core-path checks, and TestFlight distribution.
  </Card>
</Columns>

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

* [Developer preview availability](/roadmap)
* [Why Relay](/why-relay)
* [Compare your options](/alternatives)