Creative Asset Automation Built for Agencies

Upload Once. Deliver Everywhere.

Creative asset automation for agencies and marketing teams — turn one campaign master into destination-ready variants without the resize and re-export grind.

  • Immutable source files Upload once, deliver many times
  • Reusable recipes Same path for campaigns and automation
  • Destination-aware delivery CMS, ads, social, and export packs

$100 lifetime license · Lock in early pricing

Example run

Approved spring campaign hero → destination-ready pack in one execution.

Relay creative asset automation illustration

01

Source

campaign-hero.tif — immutable source in the project library.

02

Recipes

Meta 1080×1080, LinkedIn 1200×627, email banner, WordPress featured, Webflow CMS.

03

Deliver

Ad upload pack + CMS media libraries + client download ZIP.

source + output spec + destination = artifact

01

Who This Is For

Built for agencies and marketing teams that ship campaigns across channels — and the people who keep that production moving.

AgenciesStop burning retainer hours on resize and re-export. One approved master becomes every client deliverable with lineage you can show.
Marketing & SocialSelf-serve channel variants from the same library without waiting on design or dev for every size, crop, or platform format.
Ops & DevelopersLock recipes, defaults, and guardrails once. CLI, API, and config-friendly pipelines that marketing can run without breaking specs.
Client stakeholdersUpload source, review outputs, approve. No platform jargon — clear artifacts with a path back to the original file.
  • Fewer design bottlenecks on multi-channel launches
  • Less resize / re-export churn per campaign
  • One system from source library to CMS, ads, and handoff packs

02

One Mental Model

Every deliverable follows the same path — saved recipe, ad-hoc request, or automated pipeline. Relay is the content execution layer between client source content and every place it needs to go.

source + output spec + destination = artifact

01

Upload source

Client files go into an immutable source library. Tagged by role: hero image, logo, product shot, raw asset. The source never changes.

02

Define output spec

Save it as a recipe for reuse or define it ad-hoc. Dimensions, format, quality, crop, metadata — whatever the destination requires.

03

Pick a destination

WordPress, Webflow, Shopify, ad platforms, download pack, webhook, API return. Tell Relay where the artifact goes.

04

Execute

Relay generates the artifact, validates it against the spec, and delivers. Every run produces a durable artifact with clear lineage back to source.

03

Where Artifacts Go

Named destinations with spec-aware outputs. Same source, exact formats, reliable delivery — WordPress-first connectors with Webflow, Shopify, ads, and custom paths.

WordPress

Direct publish and post/media prep workflows. Images sized, optimized, and delivered to your WordPress media library or posts.

Webflow

CMS and site delivery aligned with your Webflow collection structure. Artifacts land where Webflow expects them.

Shopify

Product media and storefront-oriented outputs. Variant images, collection banners, and lifestyle shots from the same source library.

Ad Platforms

Derivative sets for Meta, Google Ads, LinkedIn, and other paid social and display specs — sizes, ratios, and safe zones from the same immutable source.

Download Packs

Bundled output sets for client handoff, internal review, or offline use. Every pack traces back to source with full lineage.

Custom Apps & Bespoke Builds

Export packs, webhooks, and API-returned artifacts for headless stacks, internal tools, and one-off client builds.

04

$100 Lifetime Access

We're building Relay in the open. Lock in founding access while we're in development. Limited window, terms honored post-launch.

Public Launch

September
subscription pricing TBA

Can't commit now? Get notified when we go live:

  • Full platform access at launch pricing
  • All connectors and destinations available
  • API access for production pipelines
  • Usage-based tiers to be announced

Public pricing announced before launch.

Relay is pre-launch. Feature completeness, support availability, and fair-use terms will be refined before September. Founding members get transparency and input throughout.

05

Trust & Clarity

What does "lifetime" mean?

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.

Is there a refund policy during development?

Yes. During the development period (before the September public launch), if Relay doesn't meet your needs, contact us for a full refund or account credit. No questions asked.

How is my source content stored?

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.

What is the difference between Relay and a CMS or DAM?

Relay is not a CMS or media library. A CMS stores and edits content in place. A DAM organizes brand assets. Relay treats source as immutable, generates derived artifacts from output specs (recipes), and delivers them to configured destinations — WordPress, Webflow, Shopify, ad platforms, download packs, webhooks, or API.

Who is Relay built for?

Agencies and marketing teams that need to turn one approved campaign master into many destination-ready variants without repeated resize and re-export work. Developers and ops teams can also define reusable recipes, pipelines, and guardrails via CLI, API, and config.

Upload Once. Deliver Everywhere.

Lock in founding access while we're building. $100 lifetime — limited window before public launch in September.