stoicsession

Totally agree on Claude's generic approach, minus the deploy/hosting hassle.

That's why I personally really appreciate any solution offering different paths to the same goal: shortening that idea-to-MVP gap even for non-devs. Excited to hear more from you and your team!

We're maintaining a waiting list while we validate GDPR metrics with pilot companies (we're in Germany).

Why did you choose to be strict with the stack instead of opening it up to meet user needs?

While talking to companies and users we found out that prescribing a stack comes with more speed, but hinders progress afterwards (many Lovable users face this issue).

This is why we opened it up completely. Users must manage the backend themselves, but the project is more sustainable (and without lock-in).

Have you checked out MainMVP (https://www.mainmvp.com) yet? It is completely stack-agnostic and gives you complete freedom in choosing it. You can also use your own keys (BYOK).