SERVICE CARD / fluxgate

FluxGate

A self-hosted Cloudflare AI image-generation gateway with REST and MCP endpoints

DECIDE FIRST

What is this project

A self-hosted Cloudflare AI image-generation gateway

What problem does it solve

Personal sites and AI agents need a controlled image-generation entry point without handing keys, images and usage data to an opaque third party

Who it is for

  • People who want to deploy an image tool in their own Cloudflare account
  • Educators, creators and small teams that need one REST and MCP entry point

What it can do

  • Turn plain-language intent into a style, subject and FLUX prompt
  • Generate and serve images through REST or MCP
  • Manage manual keys and usage in KV, store images in R2 and clean old images with Cron

Before you deploy

  • Your own Cloudflare Workers, Workers AI, KV and R2
  • Resource bindings are required; Firebase membership and a cross-account forwarder are optional

What to know first

  • Layout dimensions are composition-policy targets; FLUX.1-schnell determines the actual output size
  • This card is currently discovered; a clean-account rerun, backup/restore and full operational alerting still need independent verification

WHAT HAS BEEN CHECKED

Discovered1 EVIDENCESPEC 0.4.02026-08-29
Public evidence, scoped to this version and date.

How it runs

FluxGate 架構與資料流(依部署契約機械生成)使用者WorkerWorkers AIKV 儲存R2 物件儲存Cron 排程oauth2.googleapis.comfirestore.googleapis.comwww.googleapis.comapi.telegram.org
Architecture generated from the Service Card data flow.

Where it runs and what it touches

License
MIT
Profile
small-app
External services
oauth2.googleapis.com、firestore.googleapis.com、www.googleapis.com、api.telegram.org
Data flow
REST and MCP requests call Workers AI; manual keys and usage counters stay in KV, generated images stay in R2, and Firebase membership plus Telegram alerts are optional

Source evidence

← Back to service index