I think the project is saying, in cases where you are deploying the Frontend with server side serving, then you can include this. Given projects like NextJS have a server side serving for react server-side-rendering and for APIs this project uses the server side to add additional services as mentioned in the post.
Yeah, the messaging isn't very clear.
Yes, I agree, but it's really hard to find the right words. How would you describe it better?
That bknd is "embeddable" doesn't mean it has to. Backends such as Supabase or Firebase run on separate deployments. Especially for Supabase, if you want to self-host it, you run multiple services including your frontend. I tried to express that if you host your app on Vercel, CF, etc. – your backend (excluding database) can be deployed together with it.
Of course you can deploy it separately, e.g. fully on Cloudflare using Workers, D1 and R2.
I think the language probably assumes some knowledge specific to that ecosystem, particularly the more recent trend of server rendering react.
To someone that works with more traditional server rendering frameworks like Rails and Phoenix, embedded to me implies storage will be clientside.
I'm guessing it might makesense to a frontend developer but people like me might be scratching our heads for awhile.
I'm assuming this is an alternative to using nextjs (or whatever flavor) with an orm. There's a lot of word salad in the why? that kind of suggests that. Maybe you can simply compare alternatives?