Preview · voice + text
Your users talk.
Your app acts.
Relay is a realtime assistant layer for the product you already have. It hears a request, calls your tools, and drives your own UI — navigation, filters, charts, forms and approved changes. No widget bolted on top.
user said
Show me deals closing this month as a chart
Why now
Clicks are the bottleneck, not the answers.
01
People already talk to software
Phones, cars, speakers. Then they open your app and go back to hunting through menus.
02
Chatbots answer; they don't act
A text box beside the product can explain a screen. It can't filter the table, fill the form or file the change.
03
Relay works inside the app
The assistant uses the same actions your buttons use, so what it does is visible, undoable and under the user's control.
How it works
Three parts. You keep two of them.
Your frontend and your tools service stay yours. Relay runs the realtime session in between and speaks a typed protocol to both.
Your app
Relay Web SDK- ›Microphone + chat
- ›Registered screen actions
- ›Renders surfaces with your components
Relay gateway
hosted- ›Speech in / speech out
- ›LLM + tool loop
- ›Approvals before any write
- ›Traces and metrics per turn
Your tools service
any language- ›GET /tools — discovery
- ›POST /tools/{name}
- ›Your rules, your database
- 1
They speak or type
The Web SDK streams the microphone over WebRTC, or text over a WebSocket.
- 2
Relay listens
Turn-taking, transcription and interruptions handled on the gateway.
- 3
Your backend decides
The model calls your tools service. Your data, your validation, your permissions.
- 4
Your app speaks and acts
Typed events drive your UI: navigate, filter, show a chart, fill a form, ask for approval.
What Relay handles
The parts that take months, done once.
Turn-taking, interruptions, latency, approvals, tenancy. You write tools and register actions.
Barge-in that remembers what was heard
Interrupt mid-sentence; the conversation keeps only the words that were actually spoken.
Screen actions
Navigation, filters, sorting, opening records — the assistant calls the actions your app registers.
Generated UI, rendered by you
Tables, charts, comparisons and cards arrive as typed data. Your design system draws them.
Form filling
Values the user says land in your form's inputs. Nothing submits on its own.
Approve → commit → verify
Tools that change data only run after a person approves that exact change.
Signed, per-user tool calls
Every call is signed and says which of your users it is for, so tools return only their data.
Your model key, per project
Each project runs on its own agent, tools URL and model key. Nothing is shared.
A trace for every turn
See what was heard, which tools ran and where the time went: relay logs <session>.
Experience Center
Don't take our word for it. Talk to one.
Real apps running on Relay. Each visitor gets a private copy of the data, so go ahead and change things.
Ecommerce
Oakline store
Shop by asking. Cart, checkout and returns by voice.
Travel
Wayline bus tickets
Find the bus, pick the berth, book — by talking.
Hospitality
Roostly stays
Find the place, check the dates, book — by asking.
Sales
Sales CRM
Ask your pipeline anything. Update deals by talking.
Financial services
Mortgage servicing
Rate corrections with a human in the loop.
Developers
From npm install to talking app in an afternoon.
A CLI for your project and keys, a YAML manifest for the agent, and a framework-agnostic SDK. Your coding agent can do most of it: relay init points it at the SDK's guides.
Sign in and create a project
shellnpm install -g @sumukhj1219-wkt-org/relay-cli
relay login
relay secrets set openaiDescribe the agent, push it
orders.yamlagent_id: orders
tools_url: https://tools.example.com
system_prompt: You help customers find and change their orders.
# then
relay agents push orders.yaml
relay keys create --kind publishableConnect your frontend
tsimport { createRelaySession, registerPlaygroundSurfaces } from "@sumukhj1219-wkt-org/relay-web-sdk"
const session = createRelaySession({ gatewayUrl, apiKey, agentId: "orders", transport: "small-webrtc" })
registerPlaygroundSurfaces(session, ({ surfaces }) => render(surfaces))
session.registerAction("filter_orders", ({ status }) => setFilter(String(status)), {
description: "Filter the orders table by status",
parameters: { type: "object", properties: { status: { type: "string" } } },
})
await session.connect()Pricing
Free while Relay is in preview.
You bring your own model key, so model usage is billed by your provider. Usage-based plans for production traffic will be announced before the preview ends.
Preview
$0
- › Voice and text sessions
- › Projects, agents, keys and allowed origins
- › Session logs and usage in the CLI
Production
Let's talk
- › Higher session limits
- › Usage reporting for billing
- › Help with your launch