Everything we built, in one signal.
A live map of the Relay estate — the platform, the product, the brand, the board, the vault — and the way it was made: human + AI, in cloud sessions, with Relay itself carrying the context between them.
RelayCTX is trusted context.
MCP moves commands. A2A moves tasks. Relay moves — and proves — what agents know. Relay packages context into claimable Codes that travel between sessions, agents, and people, with provenance and custody attached. Data stays tight to its owner. That single idea fans out into every initiative below.
Product SaaS beta · live
The core product — send, receive, streams, sessions, series — onboarding external teams in the Beta / Early-Access Program today.
Trust Ladder gated
A five-rung climb (L0→L4) where each rung removes a party who could read your content — from hardened SaaS all the way to zero-knowledge.
Sovereign Relay gated
Relay on the customer's terms: own jurisdiction, own tenancy, provenance verifiable without calling home. The government-grade rung of the ladder.
Defence / IDEaS gated
Sovereign sense→verify→recognize line of effort. Submission imminent; provisional patent tracked behind the vault.
RelayCTX Enabled v3 line
"Powered by Relay" — the embeddable framework play, with FirmClerk as launch vertical (DEC-016).
Funding lanes gated
All-lanes sequencing — grants, SR&ED, AI compute credits, round — run as an operating discipline with its own kit.
Eight repos, one operating system.
Every domain of the company is a governed repository with its own MANIFEST.md — code, product, brand, management, knowledge, support, and law. Manifest drift is a bug. Click any card to open it up.
- Threaded HTTP core + FastMCP server; OTP-only auth (no passwords), JWT sessions, OAuth 2.1 for MCP
- 11-tool MCP surface, consolidated from 43 — enforced by a tool-count invariant
- 14 leader-elected background daemons: expiry sweeps, nags, drips, finance snapshots, trash purge
- Multi-region data residency (us-ca · eu) on Cloudflare R2 — fail-closed, never crosses jurisdiction
- 109 SQL migrations · 16 route families · notification fabric with 6 channel adapters
- Blue/green warm standby, auto-rollback deploys, Caddy drift-check, 13 GitHub Actions workflows
- Zero-framework vanilla-TypeScript SPA — hand-rolled router, pub/sub navigation, boot sentinel
- Dashboard, relays, streams, sessions, series, requests, cues, graph canvas (Canvas2D force sim)
- @relay/shared — single source of truth for domain types + typed API client
- Expo React Native mobile with auth → gate → app route groups mirroring the web IA
- @relay/ui — CSS-only design system package, shared by app and console
- SCP deploys with health-checked auto-rollback; staging lane on its own subdomain
- The management operating surface — leadership seats, roadmap, strategy, specs, operations
- Decision log DEC-001 → DEC-019 spanning both eras (relay-system → platform)
- Trust & Access Control canon — the L0–L4 ladder and custody doctrine live here
- Estate-operations handoff: the delegation canon for running the whole estate day-to-day
- Self-contained SR&ED kit — forkable tax-credit machinery for the corporate group
- Finance & fundraising vaults, search-excluded and Access-gated
- Canonical home of the brand — v3.5 neutral-first system, dual-value Context Teal, Open Signal mark
- Token files for CSS + Figma, brand guide, type specimens, accent explorers
- Full transactional email suite rendered against the platform's template engine
- Marketing + app + console prototypes, animatics, activation-flow mockups (this page lives here too)
- CATALOG.visual-assets — the indexed visual estate with derived-copy provenance table
- Public user documentation for the EAP cohort — quick start, core concepts, guides, reference
- Emits /llms.txt + /llms-full.txt so agents can read the manual too
- Freshdesk help widget wired in; strict MkDocs build on Cloudflare Workers
- Internal team knowledge base — product canon, brand canon, vocabulary & copy rules
- "Where things live" — the repo-separation and access map for the whole estate
- MCP surface docs, onboarding journeys, testing guide, process & workflows
- Answer-oriented support content backing the Freshdesk queue
- Troubleshooting FAQ, beta onboarding checklist, structured issue formats with severity labels
- Escalation: self-service → agent/Cowork → Platform → founder
- Attorney-client-privileged, board-level vault — access list of one (+ counsel case-by-case)
- Defence architecture bundle · patent source set · trade-secrets register · corporate & governance
- Own Cloudflare Worker route and stricter Access app; everything else sees outcome level only
A platform built like an instrument.
83k lines of deliberate Python: a threaded HTTP core with no web framework, a lean MCP surface with an enforced tool count, leader-elected daemons, and storage that fails closed across jurisdictions rather than leak a byte to the wrong region.
A product with its own vocabulary.
The web app is a zero-framework TypeScript SPA — every pixel hand-placed, every screen specified in SCREENS.md before it shipped. The mobile app mirrors the same IA in Expo. Both speak a six-word product language:
The entity itself — a claimable package of context. "Transfer" at the API layer.
The short claim token people actually share — ABC123.
A named context container grouping relays + sessions. Né "Pulse."
An AI agent session record — open/closed, handoff chain, Stream linkage.
A named sequence of relays sharing a lineage — reclaimable by name.
A re-engagement trigger — a relay that comes back on time or condition.
The design system is v3.5 neutral-first: the interface fully works in black and white, brand is a layer, and teal appears on ≤10% of any surface. One accent identity, two values — flip the theme toggle up top and watch #0d9488 become #2dd4bf. This page is built from those exact tokens.
Cormorant Garamond
Display — the single expressive moment per view. Signals importance without a gradient, an icon, or a chip.
Outfit
The operational layer — UI, labels, menus, and the RelayCTX wordmark at 600.
JetBrains Mono
Structured data — Codes, timestamps, token counts. The instrument readout.
Cloud-native, edge-served, sovereignty-aware.
A deliberately lean stack: standard-library Python at the core, the edge on Cloudflare, one droplet doing real work, and every deploy path automated with a health-checked rollback.
The mechanism layer — patent claims, defence architecture, trade secrets, finance internals — lives exclusively in relay-legal under a three-tier disclosure model: Mechanism → vault · Outcome → board/kb · External → gated behind the provisional. What can be said here is the ladder itself:
At-rest, single key — baseline SaaS.
shippedHardened SaaS — authorization rigor removes unauthorized readers.
standable todayPer-tenant keys — envelope encryption bounds any blast radius.
near-termCustomer-held keys, in-tenancy, region-pinned — removes the operator.
raise-fundedZero-knowledge / E2E — no one but the end user.
researchEach rung removes a party who could read content. Honesty canon: an app-level rule is never stated as a cryptographic guarantee.
A leadership team you can reclaim by name.
Relay runs an AI-augmented single-founder estate. Leadership is organized as seats — operating lenses, not headcount — and each live seat is a Relay series you can literally receive into a fresh session. The org chart is claimable.
Executive · CEO relay-strategy
Vision, narrative, the raise story; holds the disclosure line.
Finance · CFO relay-finance
The numbers — model, capital, grants + SR&ED, revenue. Internals gated.
Operations · COO relay-operations
The operating machine — delivery, Beta/EAP, success, GTM, estate & infra.
Strategy relay-strategy
Positioning, pricing, competitive landscape, roadmap gates.
Product
Specs, the Stream interaction model, shipping the roadmap.
Chief of Staff · GC relay-chief-of-staff
Owns the record and IP stewardship; estate coherence, disclosure-gate enforcement.
Legal & IP gated pointer
Intentionally empty here — the mechanism lives eyes-only in the vault.
From alpha to sovereign.
Narrative layer over GitHub milestones + Linear. Three interaction lanes — H2A, A2A, S2S — climbing one trust ladder.
Alpha → post-MVP jan – apr 2026 · shipped
The foundation phases — core relay primitives, auth, the first product surfaces.
Beta / EAP now · live
Public SaaS onboarding — external teams in the Early-Access Program, feedback loop running.
v1.0 — Public GA next gate
Stripe billing, open API, GA hardening. The security gate (DEC-015) is GA-blocking, by decision.
v2.0 ~sep 30
Analytics, compliance, crypto integrity, the notification/delivery layer, mobile v2.
v3.0 ~dec 31
Open-source self-host, multi-tenant, white-label — and RelayCTX Enabled embedding.
Defence / IDEaS lane 🛡 active · gated
1a submission Jul 21 · provisional ~Sep 15. Runs in parallel behind the vault.
Twelve weeks, seven hundred sixty-two commits.
Two eras — relay-system (DEC-001–010) and the platform era (DEC-011+) — and a repo estate that assembled itself in a single season. Every bar splits ■ human and ■ AI authorship.
DEC-001. The decision log opens — the relay-system era begins.
relay-support — the earliest surviving commit in the estate.
The knowledge layer assembles: creative (jun 02), kb (jun 12), board (jun 19).
The platform era. relay-platform's package epoch and relay-docs land the same week — DEC-011 collapses the MCP surface from 43 tools to a lean primitive set.
The vault and the surface: relay-legal (jul 09) and the relay-app monorepo (jul 13).
Canon week. Trust & Access Control canon, DEC-019 billing lifecycle, the consolidated funding plan — and this showcase.
IDEaS 1a (jul 21) → provisional (~sep 15) → v2.0 (~sep 30) → v3.0 (~dec 31).
Relay is built with Relay.
This is the part that should wow you, because it's true: the estate above was produced by human intent and AI execution running in cloud sessions — and the context that binds those sessions together travels as Relay Codes, through Relay's own MCP tools. The product is the process.
Strategy, disclosure line, ship-status — the reserved calls.
Remote containers, branch-per-task, 319 commits authored.
16 workflows, health gates, auto-rollback. main = prod.
Sessions seal handoffs as claimable Relay Codes with provenance.
Dogfood, verifiably
Handoff Codes are cited in the board's own changelog — the trust canon shipped under 4MB4XY, the v3.5 interface direction under 7HZQAX. The paper trail of building the company is made of the product.
Seats as claimable context
The CFO seat is relay-finance. Operations is relay-operations. Any session — human-driven or agent — reclaims a seat's full operating context by series name and picks up where the last one left off.
Governance as code
Every repo carries a MANIFEST (drift = bug), 19 logged decisions gate the architecture, a three-tier disclosure model compartmentalizes IP, and a pre-tool hook makes pushing to prod by accident structurally impossible.
An estate that runs itself
An AI estate-counterpart session carries the recurring ops; AI teammates hold named roles on the roster. The founder's job collapses to the things only a founder can decide.