Serve product images in several sizes from your own domain

What you send and what you get back

One signed request carries the original. The answer carries the addresses — you store them, you never build them yourself:

POST /api/v1/put?kind=prodimg&key=sku-1841&variants=thumb,card,full
X-Media-Tenant: yourshop      X-Media-Key-Id:  k7
X-Media-Ts:     1758300000    X-Media-Sign:    <HMAC-SHA256>

{ "key": "sku-1841",
  "variants": {
    "thumb": "https://img.yourshop.com/prodimg/sku-1841/thumb.webp",
    "card":  "https://img.yourshop.com/prodimg/sku-1841/card.webp",
    "full":  "https://img.yourshop.com/prodimg/sku-1841/full.webp" } }

The set is named and finite. There is no ?w=473: an open resize parameter is an open invitation to generate a million images nobody asked for, and you pay for every one of them.

What you no longer write yourself

• a resize worker and its queue — the answer for an image is already the finished set;
• cache headers and cache busting — a variant address never changes content, so it is immutable and cached forever;
• virus scanning on intake — the file is scanned before it is stored;
• metadata stripping — EXIF and GPS do not survive the re-encoding;
• SVG handling — it is never accepted and never served, on purpose.

Sending the same file under the same key twice does not redo the work: the intake is idempotent by content hash and returns the same addresses.

What it costs

The free plan needs no card: 1 GB of storage and 5 GB of delivery traffic is enough to put a real catalogue behind it and see the numbers. Paid plans are billed per month, and above the package storage and traffic are metered per gigabyte rather than cut off.