Take images off your application server

Moving what you already have

Two things make a migration survivable. First, already-finished copies go over without re-encoding — running a finished thumbnail through the encoder again loses quality for nothing:

POST /api/v1/put-variant?kind=prodimg&key=sku-1841&variant=card

Second, you can check the whole batch without changing anything:

POST /api/v1/reconcile
{ "kind": "prodimg",
  "items": [ { "key": "sku-1841", "variant": "card",
               "bytes": 23438, "sha256": "…" } ],
  "only": "problems" }

Each record comes back ok, missing, mismatch, pending or unverified, up to a thousand at a time, plus a digest of the batch. A migration you cannot verify is a migration you will re-run at the worst possible moment.

What your server stops doing

• holding user files that no deploy should ever touch;
• resizing on request, or keeping a worker that does;
• serving large files and paying for that traffic twice;
• scanning uploads for viruses and stripping metadata by hand.

The address belongs to the service and is stored by you: GET /api/v1/resolve answers what a key has if your record is lost, and GET /api/v1/inventory walks our whole picture in pages when you want to compare the other way round.

What it costs

Start free with 1 GB and no card. Paid plans are $5, $19 and $79 a month; above the package, storage and delivery traffic are metered per gigabyte in hundredths of a cent, because a gigabyte costs less than a cent and rounding would eat the bill.