What does this mean?:
> bknd runs directly inside your frontend app — no separate backend required.
> It supports Postgres
How is the postgres credentials kept secret from the client?
replies(2):
bknd runs directly inside your frontend app — no separate backend required. It works with Next.js, Remix, Astro, React Router. It also runs standalone on Cloudflare Workers, AWS Lambda, Bun, or Node.
It supports Postgres, LibSQL (Turso), D1, SQLite and has adapter-based storage. You get instant APIs, multi-strategy auth, media handling and a built-in Admin UI.
Curious what you’d build with it, feedback welcome!
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.
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?