Wakemark

Compare · the honest map

Who's a supplier, who's a rival, and where we fit.

Most "X vs Y" pages are thinly veiled attacks. These aren't. Half the products below are suppliersWakemark literally runs on top of — the pitch is "keep them, stop depending on them," not "leave them." The other half are the neutral layers that are genuine competitors, and we treat them with more seriousness, not less. Every number here was checked against a live page on 2026-07-10, and every page tells you where the other product is the right choice.

Container cranes silhouetted against a warm orange sunrise over calm harbor water
Suppliervs fal

Looking for a fal alternative? Keep fal. Stop depending on fal.

fal is an excellent model host — and a single point of dependency. How Wakemark sits above fal for failover, byte-exact custody, and provenance.

Read the comparison →
Top-down aerial view of a white speedboat carving a burst of white spray and wake across brilliant turquoise water
Suppliervs Replicate

A Replicate alternative — or the custody layer Replicate never tried to be

Replicate deletes API outputs after ~1 hour and is joining Cloudflare. Why custody and neutrality are a layer above Replicate, not a rival to it.

Read the comparison →
A brass maritime signal lamp on a dark ship bridge at night, casting a teal beam across rain-flecked glass
Neutral layervs OpenRouter

“OpenRouter, but for media” — and where the router stops and the proof layer starts

OpenRouter now routes image and video too. Where a neutral router is enough — and where byte-exact custody and provenance start.

Read the comparison →
A dark wooden pier stretching into black water, a teal lantern reflecting below
AI gatewayvs Cloudflare & Vercel AI Gateways

A Cloudflare (or Vercel) AI Gateway alternative for generative media

Cloudflare and Vercel AI Gateways proxy model calls and route media. Why generative-media custody and provenance need a proof layer, not a caching proxy.

Read the comparison →

The occupied gap

Each of these is copyable alone. The combination isn't.

Routing is insurance, and it rarely fires — we say so on every page. The reason to put a layer above your provider isn't the routing; it's what the layer records while it routes. Three things, together, that a single-provider business or a caching proxy can't assemble without ceasing to be what it is:

Cross-company failover

Fail a job over to a differentcompany's cloud on a 429 or outage — which an aggregator can't do without cannibalising its own lock-in.

Neutral custody

The master lives in yourbucket, under your keys, indefinitely — not on a vendor's CDN on a vendor's clock, and not inside one cloud that owns the whole stack.

Compliance-grade provenance

An append-only ledger, per-asset sha256, and lineage across providers — honest about being the log layer, not a fake green tick.

Designed for the audit question

"What is this, who made it, and can you prove it" is a different product category from inference or proxying — and Article 50 just gave it a deadline.

The through-line of every page here: we don't replace the providers, we run on top of them. One prompt, five providers, five real outputs — each streamed into byte-exact custody with its own receipt.

prompt“aerial drone photograph of a lone white boat crossing open turquoise sea in golden morning light, a long white wake trailing behind it, sparkling sun glitter on the water, premium editorial photography”
Aerial drone view of a lone white boat crossing deep turquoise sea in golden morning light, a long white wake trailing behind it
falFLUX.1 [dev]
Aerial drone view of a white boat crossing bright turquoise sea toward a band of golden sun glitter, a long white wake behind it
ReplicateFLUX 1.1 [pro]
Aerial drone view of a small white boat crossing deep green-turquoise sea in low golden light, a white wake trailing behind it
Black Forest LabsFLUX 1.1 [pro]
Aerial drone view of a white cabin boat crossing turquoise sea beside a wide field of golden sun glitter, twin white wake lines behind it
OpenAIgpt-image-1
Aerial drone view of a white boat crossing turquoise sea under a bright sun path, a long white wake spreading behind it
Runwarerunware:101

One prompt, five providers, five real outputs — each streamed into byte-exact custody with its own job id and sha256 recorded in the ledger. The receipts live in the showcase manifest, not in a caption.

The regulation behind the urgency

Why any of this is dated: EU AI Act Article 50 starts applying 2 August 2026, and the marking duty lands on more companies than expect it. Our long-form take lives on The Wake.

You're still a providerSee a provenance receipt