a small, boring static asset endpoint
A single-origin endpoint that serves static files over HTTPS. It exists because three small projects kept re-uploading the same fonts, icon sprites and a handful of PDFs to whichever host they happened to be on that month, and every move broke somebody's bookmarks.
It is deliberately unambitious. There is one machine. There is no dashboard, no sign-up, no API keys and no plan to add any. Files are pushed over rsync by the two people who need to push them, and everyone else reads.
If you landed here from a broken image, the file was probably renamed rather than removed. The changelog records renames going back to the first upload.
It was object storage for about eight months. The bill was small and the latency was fine, but every provider migration meant rewriting URLs across repositories that nobody wanted to touch. A name we control, pointed at a box we control, turned out to be the cheaper kind of boring.