Live · serving 6,219 assets from Cloudflare R2

This is where our images
actually live.

Iceberg is a small, self-hosted CDN we run on top of Cloudflare R2. Every image used across katalyst-crm.com is stored here and served straight from Cloudflare's edge network — no per-GB bandwidth bill, no vendor lock-in.

6,219

Images stored

2.7GB

Total library

$0/GB

Egress

Quick start

Three ways to use Iceberg — pick the one that matches the work you're doing.

Drop the URL straight into any <img>, <video>, CSS background-image, or fetch — no auth required.

HTML

<img src="https://cdn.katalyst-crm.com/t1/cloudinary/sample.jpg" alt="…" />

Convert an existing Cloudinary URL: drop res.cloudinary.com/dcuswyfur/image/upload/<transforms>/v123/ and prepend cdn.katalyst-crm.com/t1/cloudinary/.

The iceberg CLI is a single static Go binary. Install it once, then use it from anywhere.

Setup

# Requires Go 1.26+ — installs the binary into $GOBIN (usually ~/go/bin)
go install github.com/IRCHrocks25/katalyst-iceberg/backend/cmd/iceberg@latest

iceberg login --url https://dashboard.katalyst-crm.com
iceberg config set --cdn https://cdn.katalyst-crm.com

Common commands

# Upload (bytes go client → R2 directly, never through the API)
iceberg upload ./hero.jpg --key brand/hero.jpg

# List everything in your tenant
iceberg ls --limit 50

# Get the public URL to embed
iceberg url brand/hero.jpg
# → https://cdn.katalyst-crm.com/t1/brand/hero.jpg

# Delete
iceberg rm brand/hero.jpg

# Bulk migration from a Cloudinary account
iceberg migrate cloudinary --apply --workers 4

Server-to-server: mint an API token in the dashboard and pass it as a Bearer header. Uploads use a three-step presigned flow so bytes never traverse the API.

1. Init upload — get a presigned R2 URL

curl -X POST https://dashboard.katalyst-crm.com/assets/init-upload \
  -H "Authorization: Bearer kic_…" \
  -H "Content-Type: application/json" \
  -d '{"key":"hero.jpg","content_type":"image/jpeg"}'

2. PUT the bytes directly to R2 — no API in the path

curl -X PUT "$UPLOAD_URL" \
  -H "Content-Type: image/jpeg" \
  --upload-file ./hero.jpg

3. Mark ready — Iceberg HEADs R2 + flips the row

curl -X POST https://dashboard.katalyst-crm.com/assets/complete \
  -H "Authorization: Bearer kic_…" \
  -H "Content-Type: application/json" \
  -d '{"key":"hero.jpg"}'

CLI reference

Every iceberg subcommand.

Command	Purpose
iceberg login	Authenticate and cache an API token at `~/.iceberg/config.json`
iceberg whoami	Show the account behind the saved token
iceberg config show	Print saved url + token + tenant + cdn
iceberg config set --cdn X	Pin the public CDN base URL
iceberg upload <file> --key K	Presigned PUT directly to R2; promotes catalog row to ready
iceberg ls --limit N	List assets in your tenant
iceberg url <key>	Print the public CDN URL for embedding
iceberg rm <key>	Delete both the storage object and the catalog row
iceberg migrate cloudinary	Bulk import from a Cloudinary account (dry-run by default)

How it's built

The architecture is intentionally boring. Each layer has one job.

Storage

Cloudflare R2

Object storage that's S3-compatible and bills $0.015/GB stored. Egress to the internet via Cloudflare's edge is free.

Delivery

cdn.katalyst-crm.com

Custom domain on the R2 bucket. Every read goes through Cloudflare's edge cache. The API is never in the byte path.

Catalog

Go API + Postgres

Small Go binary on Railway. Owns auth, tenant policy, presigned-URL minting, and the metadata rows. Egress here stays flat regardless of image traffic.

Uploads

Direct-to-R2 presigned

Client → R2 directly. The API hands out a one-time signed URL and verifies completion. A 5 GB upload costs the same in server bandwidth as a 5 KB one.

Common questions

What if a URL returns 404?

Most likely you're missing the /t1/cloudinary/ path prefix, or the page hasn't had its old Cloudinary URLs swapped yet. Paste the URL into Slack and someone can confirm the asset is in the bucket.

Can I resize an image on the fly?

Not yet. Phase 3 of the build wires up Cloudflare Image Transformations so URLs like cdn-cgi/image/width=800,format=auto/<key> serve the right variant at the edge.

What does this cost monthly?

Around $5/month total — fixed compute for the API + Postgres + a few cents of R2 storage. The bill does not scale with image traffic; that's the whole point of the architecture.

This is where our images actually live.