Relay
$ relay up

Relay

The operating system for client work.

Relay connects the tools you already ship with into one timeline per client, a knowledge base that answers “where are we?”, and a portal where your clients watch it all happen. AI drafts, you approve.

$ relay waitlist --join

Get early access

Drop your email and we’ll tell you the moment Relay is ready to run. No noise, no drip campaign.

Book a demo
$ play demo.mp4

See it run

Relay — timeline, portal, approval loop
demo recording — coming soon

A walkthrough of one signal travelling the whole loop. Recording soon; the waitlist gets it first.

$ cat what-is-relay.txt

What is Relay?

Relay is the orchestration and knowledge layer over the tools you already ship with. Every commit, PR, meeting, and message lands on a client timeline, gets embedded into a per-project knowledge base, and comes back out as answers with citations — for you in the app, for your client in a portal on your own domain. Nothing reaches a client until a human approves it.

signalcommit · PR · meeting · message
client timelineknowledge basesource of truth
AI draftsyou approvepushed to your tools
client portal+ Relay AI chat
Every feature in Relay strengthens this loop. Nothing reaches a client that hasn't passed the approval step — publishing is an explicit act, never a default.

timeline

Every commit, PR, meeting, todo, and decision captured against a client and project. “Where are we?” stops being a meeting.

knowledge engine

Everything tracked is embedded into a per-project knowledge base — the source of truth. Relay AI answers with citations, scoped in SQL, never in prompts.

client portal

relay.yourcompany.com — your clients see live progress, approve work, and ask Relay AI anything about their project. Your branding, your domain.

approval loop

AI drafts, humans decide. Issues land on GitHub, emails get sent — only after you hit approve. External writes are durable and retried.

integrations

GitHub, GitLab, Bitbucket, Slack, Discord, SMTP. Events flow in, notifications flow out — normalized at the edge, never vendor payloads.

self-hosted runtime

Declarative YAML manifests become docker-compose: modules, integrations, encrypted secrets. Your stack, your data, your client's trust.

$ man relay

Frequently asked

Yes. Declarative YAML manifests compile to docker-compose — modules, integrations, encrypted secrets — and the whole stack runs on infrastructure you control. Client data never has to leave it.

GitHub, GitLab, Bitbucket, Slack, Discord, and SMTP. Events are normalized at the edge, so the timeline stores Relay's own shape rather than whatever a vendor's webhook happened to send.

No. AI drafts; humans decide. Issues get filed and emails get sent only after you approve them, and external writes go through a durable outbox that retries rather than losing the work.

A portal on your domain with your branding: live progress, work waiting on their approval, and a chat with Relay AI that answers from their project's knowledge base — with citations, scoped to their project in SQL.

Relay is commercial software, not open source. You buy a licence and run the stack on your own infrastructure — the source stays ours, the deployment and the client data stay yours.

It's in private beta. Join the waitlist or book a call, and we'll come back to you with access, licensing, and what it costs.

$ subscribe --product relay

Hear about it before your feed does.

Build notes from Relay as it comes together, plus first word when licences open up.