RD1 RelayDesk One

WEB FIRST · ONE FEED · PLUGGABLE CONNECTORS

All your communication. One web feed.

RelayDesk is now being built as a browser-first unified communication app. Matrix is the first bridge and transport adapter, while RelayDesk keeps its own neutral feed model so direct Microsoft, Slack, Gmail, email and future connectors can plug in beside it.

Web 2.3.0 Action CenterMessages become tasks and follow-upsPortable local workspace
RD1 · WEB 2.3.0 · Action Center
Priority feedSAMPLE
O

Sarah Johnson · Project Atlas

Outlook + Teams · Client timing and QA now appear in one RelayDesk thread.

G

Gmail · Travel

Your itinerary changed. New gate information is available.

W

WhatsApp · Family

Can we move dinner to 7:30 tonight?

S

Slack · Client Delivery

Cutover is approved. Who owns rollback coordination?

T

Teams · Product

QA passed. Final release sign-off is still open.

One Unified FeedNormalize messages from many transports into one calm web experience.
Matrix + direct APIsBridge broadly where Matrix fits; use provider-native adapters where they are better.
Replaceable adaptersNo transport, bridge or AI provider is allowed to own the RelayDesk core.
WEB APP NOW2.3.0Action Center · imports · backup · local rules
MATRIX ADAPTERConfiguration PreviewReplaceable bridge/transport slot · production session work remains
PLUGGABLE COREAdapter RegistryMatrix plus direct provider adapters

Unified Feed is the product. Matrix is the first bridge/transport adapter, AI stays optional, and unsupported services remain clearly labelled until a bridge or direct connector is actually configured.

THE RELAYDESK EXPERIENCE

Fewer places to check. Less to miss.

The vision is a genuine combined feed, not a collection of marketing claims. The interface below uses sample information; production access depends on each platform’s official authorization and application programming interface.

FOCUS VIEW

What needs you now

3 priority items

O

Outlook · Project Atlas

The meeting changed. Please confirm the new time.

W

WhatsApp · Demo team

Tomorrow’s walkthrough needs one final decision.

T

Teams · Product

The latest validation cycle is complete.

Sample data only. A real combined feed requires user-authorized official connectors.

WEB-ONLY PRODUCT STATUS

The browser is now the product.

RelayDesk development is focused on a genuine web Unified Feed. Matrix provides broad bridge reach, while direct adapters remain available wherever provider-native APIs are better.

AVAILABLE NOW

RD1 Web App 2.3.0

The working local Action Center adds tasks, follow-ups, calendar exports, contacts and a safe draft queue. Portable Workspace imports JSON, CSV and EML messages into the Unified Feed, applies local priority rules, and exports or restores a private backup without connector tokens.

Open the web app →

FIRST TRANSPORT

Matrix bridge adapter

Connect a Matrix homeserver and consume rooms through RelayDesk. Third-party networks require their actual Matrix bridge or a separate direct connector.

Open connectors →

NEXT

Direct provider adapters

Microsoft Graph, Slack, Gmail/API email and other approved adapters normalize into the same RelayDesk feed without changing the user experience.

See architecture →

RELAYDESK WEB 2.0 · DEVELOPER PREVIEW

Open the app. Connect a transport.

The active product now runs in the browser. Start in sample mode, then connect a test Matrix homeserver to synchronize real Matrix rooms into the same Unified Feed and send messages back to the selected room.

TRUST BY DESIGN

No fake unified inbox.

Adapters must earn access

Matrix rooms appear only after a Matrix account is connected. Other networks appear only when a real bridge or direct provider adapter is configured.

Matrix stays pluggable

RelayDesk owns the canonical feed contract. Matrix is the first bridge/transport family, not the permanent database, identity system or user interface.

Browser secrets are temporary in the preview

The current Matrix developer preview keeps its test access token in browser session storage only. Production authentication will move to a stronger server-side/session design.

Roadmap claims stay labelled

Cross-service coverage depends on actual bridge deployments and provider permissions. RelayDesk will not present an ecosystem listing as a working private inbox connector.