FIRST-PARTY / ONBOARDING

FluxGate

A self-hosted AI image gateway that turns plain-language intent into FLUX images

This is not a verified service yet

This page publishes the product purpose and onboarding status. It will enter the verified service index only after evidence is complete.

DECIDE FIRST

What is this project

A self-hosted AI image gateway that turns plain-language intent into FLUX images

What problem does it solve

People want image generation and MCP access in their own Cloudflare account without relying on a hosted image service or maintaining the prompt pipeline themselves

Who it is for

  • Individuals and educators who need their own image tool
  • Developers connecting image generation to a site or MCP client

What it can do

  • Route plain-language intent to locked visual styles and a FLUX prompt
  • Provide REST `/generate` and MCP `generate_image`/`check_job`
  • Store generated images temporarily in the deployer's R2 and clean them with a daily Cron

Before you deploy

  • Your own Cloudflare Workers, Workers AI, KV, R2 and a workers.dev subdomain
  • MCP usability needs R2; Firebase membership login and Telegram failure alerts are optional
  • The deployer manages Workers AI quota, image retention and API keys

What to know first

  • Provider safety filters may reject prompts near the boundary; hands and readable text remain FLUX model limitations
  • SIZES are layout/prompt targets; FLUX.1-schnell does not accept arbitrary width/height, so response dimensions come from the returned image bytes
  • The open-source default is a single Worker and does not include the maintainer's production cross-account forwarder
  • An isolated-resource E2E Evidence Pack exists, but an independent public Evidence Pack from a clean Cloudflare test account is not complete, so this is not a verified service
FluxGate 架構與資料流(依上架準備資料生成)使用者WorkerWorkers AIKV 儲存R2 物件儲存Cron 排程Google Firebase (optional)Telegram (optional)
Architecture generated from onboarding project data.

Current stage

MIT licensing, a portable Wrangler template, the three SmallGreen contracts, conformance CI, a deployer key CLI and a Firebase-free homepage are prepared; live isolated-resource E2E, teardown and an append-only Evidence Pack are complete in the logged-in account; CI conformance and an independent clean-account rerun remain

Before catalogue entry

  • Rerun health, MCP tools/list and draft-image checks for Workers AI, KV and R2 in a clean Cloudflare test account
  • Rerun CI conformance after the maintainer commits, and add R2 backup/restore plus Cron/alert acceptance
  • Have a maintainer review the public tree before deciding whether to make `ai-cooperation/fluxgate` public and create a release

← Back to service index