Skip to main content

The marketing site and the dashboard

CoRelayer
CoRelayer
Cooperative Relayer Infrastructure for Autonomous Transactions

Both front ends are built: co-relayer.com, the marketing site, and app.co-relayer.com, the dashboard. Both are React 19 with TypeScript and Tailwind 4, built on @corelayer/ui.

The marketing site​

Twelve routes: the product, pricing, the network, the agent story, the developer entry point, the Finance Computer argument, the brand page, security, and the legal pages. It prerenders, so every page is static HTML with its own metadata, and it serves a Markdown twin of every page at <path>.md plus /llms.txt and /llms-full.txt for machine readers.

Two things on it are calculators rather than claims:

  • the plan calculator, which takes a volume and shows what each tier would cost, including where pay-as-you-go becomes more expensive than the next tier up;
  • the Relay Unit estimator, which applies the published formula to a transaction's gas limit, gas price, data size and guarded flag — the same arithmetic the API does, in the browser.

Both are driven by the launch pricing snapshot, which is also the source this documentation's tier table is checked against.

The dashboard​

Wallet login, then the account: plan and checkout, billing and deposits, usage and transactions, latency, relayers, senders, API keys, notifications and incidents.

The relay flow is the part worth naming. It is built around a single signature: the assignment names the relayer, the transaction is signed once, and the only case that asks for a second signature is an explicit dialog that says the first attempt sent nothing and never will. (One signature)

What they talk to​

Nothing, for now. Both run against the mocked API in development and against fixtures in their tests; no build of either contacts a chain. That is a property, not a workaround — the front ends never speak to a node directly even in production, only to the CoRelayer API.