The execution layer between client source content and every place it needs to go.
Relay takes your immutable source files and turns them into exact deliverables — resized, reformatted, and sent where they need to be. One mental model: source + output spec + destination = artifact. Same path for saved recipes, ad-hoc requests, and full automation.
01
Built for the people who actually move content from source to screen.
02
How it works
Every deliverable follows the same path, whether it comes from a saved recipe, an ad-hoc request, or an automated pipeline.
Client files go into an immutable source library. Tagged by role: hero image, logo, product shot, raw asset. The source never changes.
Save it as a recipe for reuse or define it ad-hoc. Dimensions, format, quality, crop, metadata, whatever the destination requires.
03
WordPress, Webflow, Shopify, download pack, webhook, API return. Tell Relay where the artifact goes.
04
Relay generates the artifact, validates it against the spec, and delivers. Every run produces a durable artifact with clear lineage back to source.
Less resize/re-export churn. Fewer dev bottlenecks. Faster campaign and site turnaround. One system across channels.
Every project gets a source library. Files are tagged by role on upload. The original never changes. Every output is derived.
Save output specs as reusable recipes or run one-off requests. Both follow the same execution path. No special cases.
Publish, export, webhook, API return. Durable artifacts with validation and delivery records at every step.
Alt text, captions, tags, quality signals, smart crop: generated as part of execution, not a separate tool or upsell.
Outputs go where they're needed. Verification before things go live. Download packs, direct publish, webhooks, or API.
Runs operate across your source library, not one file at a time. Batch outputs, campaign sets, and derivative packs from the same execution.
Relay is not another CMS, DAM, or media library.
Connector-level integration with the platforms you already use.
05
Destinations
Named destinations with spec-aware outputs. Same source, exact formats, reliable delivery.
Direct publish and post/media prep workflows. Images sized, optimized, and delivered to your WordPress media library or posts.
CMS and site delivery aligned with your Webflow collection structure. Artifacts land where Webflow expects them.
Product media and storefront-oriented outputs. Variant images, collection banners, and lifestyle shots from the same source library.
Export packs, webhooks, and API-returned artifacts for headless stacks, internal tools, and one-off client builds.
Derivative sets for Meta, Google Ads, LinkedIn, and other paid social and display specs, including sizes, ratios, and safe zones, all from the same immutable source.
Bundled output sets for client handoff, internal review, or offline use. Every pack traces back to source with full lineage.
06
Agents & machine payments
Autonomous agents call the same path as people: discover capabilities, validate request, get a quote, pay per run, receive verified artifacts.
Agent reads Relay's capability manifest to understand available output specs, destinations, and pricing.
Request is validated against source and spec. Agent receives a quote before committing to the run.
x402 micropayment authorization before execution. Agent pays per run, per capability. No subscription required.
Verified artifacts delivered via API. Full lineage, validation status, and delivery confirmation included.
One-line bridge: Humans use subscriptions and agency billing. Agents pay per execution via x402. Same model: source + output spec + destination = artifact.
07
Founding offer
We're building Relay in the open. Lock in founding access while we're in development. Limited window, terms honored post-launch.
Lock in your rate during development. Here's what you get between now and public launch on June 1:
Pre-launch. Limited window. Founding terms honored.
Can't commit now? Get notified when we go live:
Public pricing announced before launch.
Relay is pre-launch. Feature completeness, support availability, and fair-use terms will be refined before June 1. Founding members get transparency and input throughout.
08
Your account tier is locked in at the founding rate for as long as Relay exists as a product. If we introduce usage tiers or caps post-launch, founding members keep their original terms. Major product pivots (not feature additions) would be handled with notice and a credit or refund option.
Yes. During the development period (before the June 1 public launch), if Relay doesn't meet your needs, contact us for a full refund or account credit. No questions asked.
Source files are stored as immutable objects in secure cloud storage. Files are isolated per project, encrypted at rest, and only accessible to authorized project members. We do not use your content for training or any purpose outside of generating your requested artifacts.
A CMS stores and edits content in place. Relay treats source as immutable, generates derived artifacts from output specs, and delivers them to configured destinations: publish, download packs, webhooks, or API. It bridges the gap between messy client files and exact deliverables.
Yes. Agents call the same execution path as people: discover capabilities, validate, quote, pay per run via x402, receive verified artifacts. No UI required. The roadmap also targets MPP for high-frequency agent sessions.
Lock in founding access while we're building. $100 lifetime — limited window before public launch on June 1.
Stay in the loop on Relay's development, early access milestones, connector launches, and the June 1 public launch.