Fictional developer-tool template · product behavior, metrics, customers, pricing, integrations and assurances are illustrative

Fictional product conceptsample UI

Ship background jobs
without the infra.

RELAY demonstrates how an edge-job product can explain queues, retries and observability with confidence. Replace every capability and performance claim with verified product evidence before launch.

6

complete demo pages

4

code language tabs

0

runtime asset requests

Fictional logo placeholders · replace with permissioned customer marks

CortexfielderSTACKFORMluminosveritasQUORUM

The problem

Background jobs are simple in theory.
In production, they're a nightmare.

You start with a simple queue. Then you need retries. Then a dead-letter queue. Then observability. Then regions. Six months later, you're maintaining infra you never wanted.

Silent failures

Jobs fail and disappear. No alert, no trace, no way to know what went wrong or replay it.

3am alerts

A worker crashes, a queue backs up, users don't get their receipts. You're debugging at midnight.

Infra sprawl

SQS queues, Lambda functions, CloudWatch alarms, DLQ redrive policies — all for a simple email send.

Zero observability

How many jobs ran today? What's the p99 latency? Which queue is backed up? Nobody knows.

Type-unsafe glue code

JSON.parse() with `any` types, magic string queue names, no compile-time safety between enqueue and handler.

Single-region lock-in

Your workers run in one region. Your users are everywhere. Latency is a feature you forgot to ship.

RELAY solves all of this. Out of the box. No config files.

Features

Everything you need. Nothing you don't.

RELAY is designed for developers who want to ship features, not manage queues.

Topology slot

Edge-native execution

Show how distributed workers could run close to a product's users.

This sample feature card demonstrates how a real product could explain routing, failover, and regional controls without turning the page into a wall of infrastructure jargon.

Zero lost jobs

Dead-letter queues built in

Failed jobs don't disappear. Every failure is captured, inspectable, and retryable.

Configure retry policies with exponential backoff. Inspect payloads, stack traces, and execution logs from the dashboard. Replay any job with one click.

Dead-Letter Queue3 jobs
job_2n4kx…TIMEOUT
userId: usr_1232 min ago
job_9mxpq…HTTP_500
orderId: ord_78918 min ago
job_4tkry…MAX_RETRIES
webhookUrl: ...1 hr ago
P99 in dashboard

Real-time observability

See every job's status, latency, and error in a live dashboard.

Stream job logs in real time. Set alerts on queue depth, p99 latency, or failure rate. Export metrics to Datadog, Prometheus, or your own sink.

SDK-first, not YAML-first

Define jobs in code, not config files. Type-safe from enqueue to execution.

First-class SDKs for Node.js, Python, Go, and Rust. Full TypeScript generics — your payload type flows from enqueue() to the handler with zero casting.

How it works

Show a clear path from setup to first verified result.

No infrastructure to provision. No queues to manage. Just define, enqueue, ship.

01
Define

Define your job

Use the SDK to write a typed job handler. Set retry policies, timeouts, and queue routing — in code, not config.

snippet
relay.defineJob({
  id: "send-invoice",
  queue: "billing",
  retries: 5,
  timeout: "30s",
  handler: async (payload) => { ... }
})
02
Enqueue

Enqueue from anywhere

Call .enqueue() from your API, webhook handler, or scheduled function. RELAY routes to the nearest edge worker instantly.

snippet
await sendInvoice.enqueue({
  userId: "usr_123",
  amount: 4999,
});
// -> job_7xnm | eu-west-1 | 21ms
03
Monitor

Monitor and recover

Every execution is logged, every failure is captured in the DLQ, and every metric is in your dashboard — real time.

SDK examples

Demonstrate the integration story.

First-class SDKs for every major language. Or use the HTTP API from anywhere.

ts25 lines
import { relay } from "@relay/sdk";

const generateReport = relay.defineJob({
  id: "generate-report",
  queue: "analytics",
  retries: 3,
  timeout: "5m",
  async handler(payload: { reportId: string; format: "pdf" | "csv" }) {
    const data = await fetchReportData(payload.reportId);
    const file = await renderReport(data, payload.format);

    await storage.upload(`reports/${payload.reportId}.${payload.format}`, file);
    await notify.email({ template: "report-ready", data: { reportId } });
  },
});

// Enqueue from your Express/Next.js API
app.post("/reports", async (req, res) => {
  const job = await generateReport.enqueue({
    reportId: req.body.id,
    format: "pdf",
  });

  res.json({ jobId: job.id, status: "queued" });
});

Integrates with your stack

Template composition

6

Complete pages

Landing, pricing, docs, changelog, waitlist and 404

4

Code examples

Node, Python, Go and cURL presentation tabs

8

FAQ slots

Typed answers ready for verified product facts

0

External assets

Self-hosted fonts and code-native visuals

Sample social-proof pattern

Developers ship faster with RELAY.

“Use this card for a permissioned migration outcome with a specific baseline, measured result and enough context for buyers to trust it.”

Photo of Illustrative customer voice
Illustrative customer voice

Replace with consented attribution · Verified proof

“Use this card to explain how the product changed an operational workflow, backed by supportable reliability or incident evidence.”

Photo of Illustrative platform lead
Illustrative platform lead

Replace with verified role · Consented customer

“Use this card for a scale or implementation result only after the volume, time period and comparison can be documented.”

Photo of Illustrative executive voice
Illustrative executive voice

Replace with consented attribution · Measured outcome

Illustrative pricing model

Make plan differences easy to scan.

Compare hierarchy, limits and upgrade paths; validate every price, allowance and term before launch.

Hobby

An entry-tier example for side projects and early experiments.

Free
  • 100,000 job executions / month
  • 3 queues
  • 5 edge regions
  • 72-hour log retention
  • Community support
  • + 1 more features
Preview Hobby
Most popular

Pro

For growing teams that need reliability, observability, and scale.

$49/ month
  • 10M job executions / month
  • Unlimited queues
  • 40+ edge regions
  • 30-day log retention
  • Priority email support
  • + 4 more features
Preview Pro

Enterprise

For teams with compliance, SLA, and volume requirements.

Custom
  • Unlimited executions
  • Unlimited queues
  • Private edge regions
  • 1-year log retention
  • Dedicated Slack support & SLA
  • + 5 more features
Preview Enterprise

RELAY vs building it yourself

estimated savings / month
What you're avoidingDIY est. costWith RELAY ProYou save
SQS + Lambda infra setup~8 hrs eng0 hrs$800+
DLQ monitoring + alerts~4 hrs / moBuilt in$400+
Multi-region job routing$200+ / moIncluded$200+
Ops overhead (on-call, fixes)~6 hrs / mo0 hrs$600+
Total monthly savings$49 / mo$2,000+

Engineering time estimated at $100/hr. Infrastructure costs vary. RELAY Pro at $49/mo.

FAQ

Common questions, straight answers.

Waitlist pattern

Ship faster.
Sleep better.

Preview a focused signup journey, then connect consent, storage, delivery and a real launch timeline before publishing.

Front-end demo · no account, subscription or waitlist record is created here.