relays
Bring a workflow

Automate the busywork.

Relays builds and runs AI workflows for the work your team repeats: renewals, onboarding, support escalations, document review. In your cloud, and kept working by us.

Bring us a workflowSee how it works

Illustrative run

Customer renewal workflowRunning
Artifact

At-risk accounts

Executive briefReady
Outreach sequenceNeeds review
View

Station 01

One workflow. Mapped.

Renewal prep, customer onboarding, implementation handoffs, support escalations. We sit with the people who do it, collect real cases and the exceptions nobody wrote down, and agree what done looks like.

Intake · what we ask for
  • A named workflow
  • An accountable owner
  • Historical examples
  • Known exceptions
  • Integration access
  • A human review path
  • A measurable result

Station 02

Built in your cloud.

Integrations, software and the agent itself, deployed where your data already lives. You keep the code, the credentials and the logs.

Deployment boundary · intended default
Your cloudWorkflow serviceCredentialsSource dataLogs & runbooks
Model providerVia the Relays gatewayFallback armed

Station 03

Checked before it acts.

We run it against your real cases before launch. Anything consequential waits for a yes from the person who owns it. Your team approves the work instead of doing it.

Case review · synthetic
CaseExpectedResult
Renewal, usage downFlag + briefMatch
Champion leftEscalateMatch
Contract in legalHoldTo review
Multi-year, healthyNo actionMatch

Station 04

Kept working. By us.

Monitoring, maintenance and the changes you ask for. When it breaks, we hear about it, not your team. Every model request lands in a ledger you can read.

Ledger · illustrative
  1. renewal_interventionok
  2. provider attempt 1timeout
  3. provider attempt 2ok
  4. owner review queuedheld

  • Provider gateway

    OpenAI and Anthropic-compatible APIs, streaming and tools, one place to hold keys.

  • Deterministic fallback

    When a provider fails, the next one in your policy takes the request.

  • Append-only ledger

    Each request and every provider attempt, recorded and never rewritten.

  • Dashboard

    Keys, usage, budgets and receipts in one quiet screen.

  • Python & TypeScript clients

    Typed clients for the code your team already writes.

  • Runbooks

    Written down, handed over, kept current as the workflow changes.

  • Human review

    Consequential actions stop at the owner's desk, not after.

  • Your source code

    The workflow is software in your repository, not a black box.

  • Streaming & tools

    Streamed responses and tool calls pass through untouched.

Yours,
not ours.

Your cloud, your keys, your data, your code. We run the workflow; you own what it runs on. Every engagement writes this down before the first line of code.

PartDetailsHeld by
Cloud accountWhere the workflow runs.You
CredentialsSystem and model keys, in your vault.You
Source dataStays in your systems of record.You
Logs & backupsWritten to storage you control.You
Source codeLives in your repository.You
UpgradesProposed by us, approved by you.Shared
IncidentsWe answer when it breaks.Relays
Model connectionPrompts reach the provider you choose. Data sent there leaves your environment.Shared

Ask
away.

Hand us the busywork.

Tell us the workflow your team keeps doing by hand. We will tell you plainly whether it fits, then map it, build it and run it. You take the afternoon.

Bring us a workflowRead the mission