I agree, my connotation of "web framework" is that it competes with Next.js or Remix or something. This seems like a schema-driven ORM a la Prisma, plus API layer. In other words, you could conceivably use it alongside a "web framework".
I would lean in on the unified schema aspect, I think that distinguishes it from a lot of web-focused ORMs. It actually feels like it could be compared against GraphQL given the schema and API features.
Of course, that leads me to wonder about the hairy stuff: permissions, rate limiting, schema evolution, etc.
I would lean in on the unified schema aspect, I think that distinguishes it from a lot of web-focused ORMs. It actually feels like it could be compared against GraphQL given the schema and API features.
Of course, that leads me to wonder about the hairy stuff: permissions, rate limiting, schema evolution, etc.