Ask HN: Help Presenting My Open Source Micro-Backend

Me and my buddy are currently struggling in finding a good term to describe our product: is it a micro-backend ? A Headless CMS ? A Backend-as-a-Service ? An API ?

https://manifest.build/ is a really simple 1-file backend to power the API of small to medium websites, apps, directories and so on.

We first presented it as "A complete backend that fits into 1 YAML file" and got some attention. However, it can be deceptive as it does not compare to "real" backend frameworks like Laravel, Django or NestJS. Nor does it compete with backend infrastructure products.

Talking with Manifest users, we found out that many of them were using it as a Headless CMS, so we are currently presenting it as such. However even there we are not 100% satisfied as it differs from the "rich content experience" offered by products like Sanity or Hygraph.

As a developer, how would you call Manifest ?