06 / Deliver
Serve content from the edge. Resize, crop, and optimize images on request. Upload once, use everywhere.
Included on every plan. No add-on, no separate bill.
What this replaces
Most headless systems hand you the content and stop there. You add a CDN subscription, an image service, your own caching headers, and an infrastructure bill nobody budgeted for. b10cks does that part itself.
How it works
Put the original in once at full quality. Ask for the size and crop you want in the URL. The result is built on request and kept at the edge for the next visitor.
Upload the source image at full resolution and full quality. That file stays untouched, so you never have to re-export a set of sizes.
Width, height, crop, format, quality. Add the parameters to the image URL and the variant is generated the moment it is requested.
Every processed image is cached at the edge. The first request pays for the work. Everyone after that gets the finished file.
Published content responses are cached at the edge too, by locale and by version, so the API answers from close by instead of from one origin.
Publish a change and the cached responses for it move on. No manual invalidation, no stale variant hanging around after you swapped the image.
The same source image feeds the website hero, the app thumbnail, and the email header. One asset, as many shapes as the screens need.
How you use it
No SDK call, no build step, no pipeline to maintain. Write the parameters you want into the image URL and let the edge do the rest. It works the same in a Nuxt page, a React component, or a plain img tag.
One source / many shapes
# the original, untouched
/ilum/<space>/<asset>/hero.jpg
# 1600 wide, modern format
/ilum/<space>/<asset>/hero.jpg?w=1600&format=webp
# square crop for a card
/ilum/<space>/<asset>/hero.jpg?w=400&h=400&fit=cropShip it fast
Fast delivery should not be a plan upgrade. Start with it on day one and see what your pages feel like.