Beta · Now Open

Load what you need.
Share what you've made.

Relay moves your context — across sessions, tools, and teammates — so you show up ready every time. Load up. Do the work. Pass it forward.

Register → How it works
/ load fast · share what you've made · secure by design · private by default
/

The pipe runs both ways.

Every Relay transfer moves in a direction. Load context before you begin. Move it forward when you're done. Both directions. One pipe.

Source

Load context
before you begin.

Claim a Relay before issuing your first command. The brief, the ICP, the prior session — already loaded. No briefing, no catching up. Your agent starts fully informed, not blank. Stack multiple Relays. Load everything at once.

Load context. Act informed.
Create Relay →
relay: R9LYrelay · context
← Claim Relay
/

Platform

Start free.
Scale when you need to.

Unlimited transfers, single-use PINs, and transfer encryption — free, always. Platform features available on paid plans.

Free · Standard · Team · Enterprise — see all plans →
Free
Always free
$0 / month
50 transfers included · private & team-scoped · 30-day expiry · full app access. No credit card required.
Start free →
Standard
$15/moBETA — FREE
Encrypted transfers, 6-month history, webhooks, extended metadata, email support.
Sign up →
Team
$18/seat/moBETA — FREE
Org accounts, transfer visibility, per-agent analytics, admin panel + API.
Sign up →
Enterprise
Custom
Custom integration, SLA, regional node options, dedicated support for operators.
Talk to us →

Billing via Stripe. Paid tiers free during beta — we'll give plenty of notice before billing goes live.

See all platform plans →
/

How It Works

Four steps. Connect, create a Relay, share the PIN, claim it anywhere. That's the whole loop.

01
🔌 Connect once.
Add the Relay Connector to your Claude session — takes 30 seconds.
›
Add the Relay MCP server to your Claude Desktop or API setup. One config block — no app to install, no UI to learn. Once connected, every MCP tool is available in any session.
Tell your agent what to package — a brief, a decision log, a research summary, a prompt chain. Relay creates a transfer and returns a relay ID. That code is the key.
The relay ID is short and human-readable. Drop it in a Slack message, a GitHub comment, an email, a new chat window. It doesn't matter where. Relay finds it.
Claim your Relay in any new session. The full context loads instantly — ready before you type your first command. Context goes where the Relay ID goes, and nowhere else.
That's the loop. Want step-by-step code, MCP config, and a full FAQ?
See the full Product guide →

Ready to move context deliberately?

Connect in 30 seconds. Beta access in exchange for your feedback.

Register → See full guide ↗
/

What People Do With It

Source
📥 Start with everything you need.
Claim a Relay before issuing your first command.
›
Load the brief, the ICP, the prior session — whatever that agent needs. It already has everything before you type a word. No briefing required. No catching up. The AI starts informed.
Source before you act.
Decisions, direction, momentum — packaged into a Relay and sent to a teammate or agent. They pick up exactly where you left off. The work doesn't stop when your session does.
Share what you've built. Keep things moving.
Then give your command. The AI already knows everything it needs. The output reflects all of it — coherently, without contradiction. Stack as many Relays as the work requires.
Load before you launch.
Source and share in a continuous loop. One agent packages the output; the next agent claims it and continues. The collaboration never loses the thread — even across completely separate sessions.
Define the collaboration. Relay handles the pipe.
Every session starts enriched, not blank. Every agent hits the ground running. Define which agents can create Relays, scope PINs to your org, and get fleet-level visibility across all transfers. Relay gets out of the way. Your product stays in front.
Relay is infrastructure. You build on top.
/

How It's Built

Agent
A
source
Context Pipe
RELAY
source
Agent
B
The pipe runs both ways. Share packages context and pushes it forward. Load pulls context in before acting. Context goes where you send the relay ID — nowhere else.

Relay is designed around a specific set of constraints — not as limitations, but as deliberate choices. Each one reflects a belief about how context should move in agentic systems.

🔀
The pipe, not the vault.
Relay moves context. It doesn't store it indefinitely. Your content transits the pipe and is consumed. The envelope moves. The payload stays yours.
transit · not storage
🎯
Single-use by default.
Every Relay is single-use unless you configure otherwise. Context goes where you send it, and nowhere else. Multi-claim is a platform feature — not the default.
claimed once · consumed
💨
No trail, by design.
Default: nothing retained after a transfer is claimed. Enterprise plans add the audit controls that compliance teams need. You choose the visibility model — Relay doesn't assume you want one.
no retention · opt-in audit
🔌
Works where you work.
Share the relay ID. Drop it in any chat, task, or message. Claim it. Context in. No new app. No new UI. Relay integrates into the tools you're already using.
any tool · any session
Full technical overview →

Still have questions?

How PINs work, what's encrypted, multi-agent setups, operator APIs, data retention — all answered. No fluff.

Read the FAQ →

Move your context.
Keep the work moving.

Apply below — an access code will unlock your account immediately. No code? We'll review your application and be in touch.

Questions? contact us or email support@relaycontext.com

Have a code — your account unlocks instantly.