RelayCTXOrigin Slide · Round-tableABC select · ◀▶ cycle · E ember · P pitch prompter · esc exit
Origin
It started with a mic and a whiteboard.
The initial goal wasn’t infrastructure. It was simple: speak a thought into a phone while you’re out in the world — and have it land somewhere structured. Sit back down, at any desk, any tool, any session — and pick up exactly where you left off. That desire for continuity is what Relay is built to deliver. The infrastructure — the encryption, the provenance, the transfer layer — is what it took to solve it properly.
“I just wanted my context to follow me. Everything else is what it took to do that right.”
RelayCTXOrigin · 02
Origin
Every session starts cold. Relay started with wanting to fix that.
A whiteboard prototype. Speak into a mic — have it surface as something structured and accessible. Go back to it anywhere. No briefing. No rebuild. Just continuity. That prototype became the question: what would it actually take to make context follow you? Relay is the answer.
“The demo is the product. This session is running on Relay.”
RelayCTXOrigin · 02
Origin
Before the infrastructure, there was a simpler goal.
Speak. Capture. Sit down anywhere. Pick up exactly where you left off.
That instinct is what Relay is built on.
RelayCTXOrigin · 02
Artifact preview — deck system v3.2 (parchment / ember) · page chrome — product system v3.4.1relay-john-deck-v3 · insert between Cover and The Problem
Case for AWarmest and most human — the founder is present in the prose, the pull quote earns the infrastructure. Risk: longest read on screen; presenter must not read it aloud.
Case for BBridges hardest into The Problem — headline does double duty and “the demo is the product” lands the proof early. Risk: leads cold before the room has warmed up.
Case for CMost confident in the room — four beats, all air; the presenter carries the story. Risk: needs a strong spoken origin or it reads as a placeholder.
Before any of the infrastructure thinking, I had a much simpler goal. I wanted to speak a thought into my phone — while I was out, between meetings, away from a desk — and have it land somewhere structured. Something I could pick up from anywhere, in any session, without having to rebuild what I’d already figured out.
That instinct led somewhere bigger. Because when you actually try to solve it — not just for one person, but across sessions, tools, AI agents, and teams — you realize there’s a missing layer. The tools exist. Claude, Cursor, Devin, dozens of others. But nothing moves context between them. Every session starts cold. Every agent starts blank. The work rebuilds from scratch every time.
That’s the invisible wall. And it gets worse as AI work accelerates.
Relay is the context layer. It captures the substance of work — decisions, state, intent — and moves it forward to whoever or whatever needs it next. Intentionally, with control over who sees what and a record of where it went.
Think of it as infrastructure the way OAuth is infrastructure. It sits under your tools. You don’t think about it. But everything built on top of it works better because it’s there.
The category is forming now. We’re early — and we’re protecting the architecture.
If any of this resonates, the next step is a short conversation.