Exactly. Or drastically changes their pricing model (see: Contentful).

I understand the benefits of all of these individual services, but I also miss the days of the only service I had to worry about when I handed off a client site was hosting.

Now it's often the headless CMS hosting (i.e. Contentful, GraphCMS), actual hosting (Netlify), CDN, Image CDN, Search (i.e. Algolia). So many places for things to break. So many separate charges.

I also love headless CMS's but much prefer self-hosted ones. Directus has been a favorite to experiment with so far.

Checkout daptin if you are looking for an open source self hosted solution for headless cms

https://github.com/daptin/daptin

I definitely can understand this point of view! But this is actually the case for all SaaS's out there. I would even say that this is also the case for open source projects if there aren't maintained anymore and the costs for trying this yourself are too high.

One benefit of the nature of a headless CMS though, is that there can't really be a vendor lock-in on your content.

If there was a commitment to open source if the service was being shut down, I would sign up.

Content is a much larger problem than many realize u til they are dragged into projects that run late, grow too big, and need too many signoffs to be ready.

I've run into this recently. We're exploring using headless Wordpress for some static sites. Seems to work pretty well.

as a client, I would rather be paying a hosting company specializing in one area 24x7 rather than a dev maintaining the database on and off basis. there is nothing more infuriating than not being able to get a hold of the dev when your site is offline for whatever reasons.