GRIN · Cloudflare

GRIN is already on Cloudflare in three places.
Gia is the fourth.

The marketing pitch on grin.co is clear: "You don't buy seats. You hire Gia." Free-forever affiliate for everyone, charged only when Gia takes on real management work. That economic model is only sustainable if Gia's per-creator inference cost stays predictable as the 750K-creator graph scales.

From the public DNS, GRIN already routes meaningful traffic through Cloudflare. The Gia-shaped piece is the one that isn't on us yet — and it's also the piece where AI cost-attribution becomes the line between "free forever" and "free until it isn't."

api.grin.co
on CFStoplight.io API gateway proxied through Cloudflare anycast
auth.grin.co
on CFAuth0 tenant routed via auth0-ingress on Cloudflare's CDN
help.grin.co
on CFIntercom help center fronted by Cloudflare
grin.co (marketing)
SucuriWordPress behind Sucuri Cloudproxy — natural consolidation lane
app.grin.co
AWS ELBPlatform on us-east-1 ELB — origin stays put; edge gets richer
grin.ai (Gia)
newThe AI-native product — where AI Gateway, Workers AI, Vectorize all sit underneath
GA · June 2026 Your AI bill is out of control. Cloudflare can fix it now.
AI Gateway ships dollar-denominated spend limits, per-customer attribution, PII redaction, and automatic fallback routing — across every model provider, in one log line. For a free-forever model where Gia's cost is the line between margin and loss, this is the runtime piece that makes the business defensible. Read the announcement.

Three places Cloudflare's developer platform maps directly to how Gia actually works:

AI Gateway — under every Gia call: sourcing matches across 750K creators, outreach generation, content scoring, performance summaries. Per-brand cost attribution, dollar caps, fallback to cheaper models when budgets tighten.
Vectorize — for the creator-matching semantic layer. 750K creators × brand personas × content history is the canonical vector-search workload.
R2 — for the content tracking surface. Every post, story, and video Gia collects across Instagram / TikTok / YouTube, stored at zero egress.

One question for the platform team:

Is the bigger AI-side pain right now on the cost-attribution side — keeping per-brand Gia spend predictable as the program scales — or on the infrastructure-consolidation side — pulling Sucuri's job into the same platform that already fronts your API, auth, and help center? 20 minutes to find the right starting point.

Deeper Dive

The full architecture, ready when you are

A detailed primitive-by-primitive mapping — including the Gia agentic-AI pipeline, the 750K creator-graph retrieval pattern, the free-forever unit-economics math, and the path from Sucuri to a Cloudflare-native security posture — is in progress. Tell me which slice would be most useful first and I'll send it.

Request the expanded version →
Grab 20 minutes →
Matt Holscher Cloudflare · Developer Platform