Nope, but it seems like it's still on a waitlist - are you planning on launching soon?

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).

▲

artahian 3 hours ago | parent [-]

The reason why we didn't build a generic platform instead is because everyone already has access to Cursor and Claude Code for building free form applications, and each stack is uniquely different in its challenges. We're picking a particular stack so that the integration between all pieces can be seamless, reliable and pre-built, rather than AI connecting everything from scratch.

	▲	stoicsession 3 hours ago \| parent [-]
		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!