Built right, for the tools that do the work.
Our mission is to make building software right seamless — where the obvious path and the safe path are the same path, so an AI agent spends its effort on the product you can see, not on plumbing it could get wrong.
We build tools for agents, not dashboards for operators
Relayplex is designed to be used by AI agents — specifically the shell-capable coding
agents that already run commands in your terminal, like Claude Code and Codex.
They drive every Relayplex primitive with plain curl calls (or any HTTP client), so
there is no SDK to install and nothing between intent and a live artifact but a command. Every
primitive is judged by one test: does it reduce the number of non-visible concepts an agent must
hold to get from intent to a live, interactive artifact? That yields two
properties we never compromise: the system is guessable (predict behavior from conventions,
not configuration) and honest (what is true and what is wrong are machine-readable, with no
human dashboard required to operate).
The bootstrapping bet
Build the tools, to build the tools, to do the work. — Douglas Engelbart
Engelbart's insight was that progress compounds when you improve the tools that build your tools. We read it directly into our product: our customers bring the first set of tools — their AI agents. Relayplex is the second set — the public application layer those agents use to actually get the work done. We are tooling for the tools. Make the second set sharper and every agent on the platform gets better at shipping the visible product, which raises the value of every application built on Relayplex.
Proof: the storage unit
The name is the permission model
Three typed buckets whose names encode data-flow direction. submissions is
owner-read by construction, so visitor input cannot be exposed; public writes use scoped,
append-only capability tokens, never master credentials. The agent picks the right word and
gets the right security — automatically. See the
API reference.