SERVICE CARD / cloudflare-imgbed

CloudFlare-ImgBed

An image and file manager in its external-link fallback profile with KV metadata

DECIDE FIRST

What is this project

A self-hosted image and file management entry point

What problem does it solve

Website images and files depend on a hosted image service, leaving links and metadata outside the deployer's account

Who it is for

  • Small websites and content teams
  • Creators who need a simple image-management tool

What it can do

  • Manage image metadata and sharing links
  • Store management metadata in your own KV
  • Operate in a fallback mode using external image URLs

Before you deploy

  • A Cloudflare Worker and KV
  • The deployer reviews external image origins and link availability

What to know first

  • The catalogue card describes an external-link fallback, not private binary storage
  • Content availability depends on external image origins

WHAT HAS BEEN CHECKED

Discovered2 EVIDENCESPEC 0.2.12026-08-03
Public evidence, scoped to this version and date.

How it runs

CloudFlare-ImgBed verified service screenshot
Screenshot referenced by the published Evidence Pack
CloudFlare-ImgBed 架構與資料流（依部署契約機械生成）使用者WorkerKV 儲存使用者指定端點cn.bing.como4507644548022272.ingest.us.s…frozen-sentinel.pages.dev使用者設定端點
Architecture generated from the Service Card data flow.

Give this to your Agent

Please follow https://github.com/smallgreen-cloud/adapter-cloudflare-imgbed/AGENTS.md to deploy this service

Where it runs and what it touches

Upstream
MarSeventh/CloudFlare-ImgBed
License
MIT
Profile
small-app
External services
(user-directed)、cn.bing.com、o4507644548022272.ingest.us.sentry.io、frozen-sentinel.pages.dev、(user-configured)
Data flow
This verified fallback profile registers external image URLs and manages metadata in KV because no binary storage channel is configured

Source evidence

← Back to service index