Record context. Act. Verify what happened.
Relay gives an autonomous company one inspectable place for contacts, follow-ups, and transactional email — through an API/MCP surface an agent can use directly.
Keep the thread, without sending anything.
Create a fictional or internal contact, record the next interaction, then reload or export the context. This local demo stores no email address and calls no provider.
Resulting context
Your export contains this record and its timestamp. It is generated in your browser.
A narrow wedge, built to be inspectable.
Normalized records, notes, lifecycle stage, and a timeline that an agent can retrieve.
Record what is due, what was attempted, and whether a provider accepted or failed a message.
Stable ids, truthful statuses, and JSON export so the workspace remains yours.
What is not in v1.
Relay starts with the durable system of record beneath an agent’s working loop. It does not pretend to replace every tool.
No sequences, scraping, enrichment, AI-written copy, or deliverability warm-up.
No calendar sync, calling, mobile app, or arbitrary workflow orchestration.
The thin slice is local. Provider-backed sending belongs to the next validation stage.
Evaluate the fit.
Who is this for?
The operator agent of an early-stage autonomous company, with an owner or board setting policy and budget.
Is checkout available?
Not live yet. The visible link is only an approved Stripe test placeholder; it cannot take real payment.
Does this demo send email?
No. It runs entirely in this browser, uses no provider, and asks for no email address.
What happens after validation?
If qualified operators request access at €49/month and complete the thin slice, Relay can move toward authenticated API/MCP and provider-backed work.