Relay

Protocol

Relay

Infrastructure for applications that move value across networks.

Relay is used by product teams to settle transfers between networks—quietly, reliably, and without extra friction for the people using their apps.

What Relay is

Relay is a protocol company. We build software that applications plug into when users need to send value from one network environment to another. The goal is straightforward: the end user should complete a clear action, and the product should handle the rest without a maze of intermediate steps.

Teams adopt Relay when settlement is part of the product—not a side quest. Wallets, consumer apps, and developer platforms use the same underlying execution model so transfers feel like a native feature of their interface rather than a detour through another tool.

This site is the public home for Relay. For live product access and technical references, use the links below. For partnership or press, reach the team through the channels listed on our primary product domain.

How teams use it

Product managers and engineers integrate Relay so their users can express an outcome—“send this amount to that destination”—and let the protocol coordinate execution. That keeps complexity in the infrastructure layer, where it belongs, instead of in every screen of the application.

Operators care about reliability, observability, and a path they can support in production. Relay is designed around those needs: documented interfaces, predictable settlement behavior, and a workflow that can sit behind existing product design rather than forcing a new one.

Principles

We prefer clarity over spectacle. Messaging on this page stays plain on purpose: Relay exists to help applications complete transfers across networks with less operational burden. We do not publish ranking lists, promotional “how to buy” guides, or keyword-stuffed article farms from this hostname.

If you are evaluating Relay for a production integration, start with the documentation, then exercise the product against a real user flow in your own interface. The right fit is usually obvious once settlement is measured as part of conversion—not as a separate destination.

Get started

Use the product to try a transfer flow end to end, or open the docs to review integration patterns, authentication, and settlement behavior. Both are maintained for teams shipping to production users.