We built a CMS for ourselves that we love to use, and we want you to give it a try.

Helga and I have spent years building websites, and every one of them needed a CMS. We've tried most of them. We even liked some of them.

But a quiet unease never went away. Our content, the thing the whole site was made of, lived in somebody else's database, behind somebody else's API, on somebody else's pricing page. The images lived on their CDN. The export button produced something that technically counted as our data. And lately every CMS has been growing an AI assistant we didn't ask for, while staying closed to the AI tools we actually use.

Meanwhile, the cloud quietly became amazing. A bucket on Cloudflare or Amazon costs almost nothing, serves files globally, versions them, backs them up. Image services crop and optimize on the fly. Most of what a CMS bills you for is already sitting there, in infrastructure you can rent for pennies and point anywhere you like.

So the CMS we wanted became obvious: just the editing layer. Schemas, validation, drafts, publishing, localization, history. Everything else belongs to the cloud, and the cloud should be ours.

That's Blobify. You bring a bucket. Blobify writes your content into it as plain JSON files: your entries, plus the summaries and indexes a website needs to render fast. Your site reads those files straight from your own storage and CDN. It never calls us. If Blobify has a bad day, your site doesn't notice.

That architecture changes what pricing can be. You can stop paying at any time and nothing breaks, because the files were yours the whole time. You pay when you want to edit, in the dashboard or through your AI tools, and only then. No asset counts, no request quotas, no cut of your bandwidth.

The AI part I built the way I wish everyone would. Blobify ships an MCP server, so Claude, ChatGPT, or agents you write yourself can design schemas, edit entries, import a thousand records, and publish, passing the same validation as a human editor. I didn't build an assistant into Blobify. I made Blobify a good tool for your assistants.

This isn't hypothetical. I've moved two production sites off Prismic with those same MCP tools: eclipse2026.is and icelandatnight.is. Eclipse2026 is the number one place to plan for the 2026 total solar eclipse in Iceland, and as the big day approaches, its traffic has exploded. The reward for that success was a CMS bill that jumped to $250 a month overnight. One afternoon of migration later, the site reads straight from a Cloudflare bucket its owner controls, and the bill is pennies. Same content, same site, a fraction of the cost.

I use Blobify every day. I've fixed a typo from my phone over breakfast and had the site update before the coffee got cold. And I know, with unusual certainty for this industry, exactly where my content is: in my bucket, as files, mine.

And Blobify is a family build. My wife and co-founder Helga Kristín was its first real user and its most demanding one: she publishes her DJ mixes straight from her own bucket and shares them with friends, and she kept pushing until the asset side of Blobify grew into something like a Dropbox or Google Drive that you own. Upload files, organize them, share them, and let anyone press play in the public player.

That's why we're sharing it. Maybe it's the tool you've been wanting too. It's free to get started, and if you try it, we'd love to hear what you think. Every piece of feedback makes Blobify a little better, and we read them all.