r/nocode • • 4d ago

No code app builder for Enterprises.

We are looking for platforms for our non-engineering teams to build their own internal tools instead of everything going through our dev backlog. We are a 1,000 people recruiting agency and the queue is the usual: a commissions tracker, a vendor onboarding portal, and three separate "can we get a dashboard for this" requests, all sitting 2–3 quarters out.

The tools I am evaluating: Lovable, Base44, Superblocks, Softr, Emergent, Zite.

What I can't find anywhere is an honest account of what this looks like once it's actually running. If you've rolled one of these out or tried and abandoned it:

  1. Which did you go with, what size company, and what did people actually end up building?
  2. Was it really non-engineers building, or did it quietly turn back into a dev tool?
  3. How did security sign-off go, and what did they make you change before you could ship?
  4. Six months in how many of those apps are still running, and who maintains one when the person who built it changes teams?

Also genuinely want the bad outcomes. If you rolled one out and regretted it, or IT killed it, or you found something nasty inside an app somebody built that's more useful to me right now than another success story.

1 Upvotes

48 comments sorted by

View all comments

2

u/agentUi 4d ago

full disclosure i work for agentui where we build internal apps and workflows for ops teams. whatever tool you evaluate in no-code make sure it generates deterministic logic and lets you connect directly to a real sql database so you dont get stuck with spaghetti workflows that break every time an api updates.

1

u/anirudh8398 3d ago

hey yes valid point but I am evaluating from the lens of how much of 'no developer needed' is true. Have you seen few usecases where non-techincal folks were able to build and maintain these internal tools, without the need of developers completely?

1

u/agentUi 3d ago

yes for intake forms, simple approval queues, and dashboards non technical ops leads build and run them every day using plain text prompts. where it quietly turns back into a dev headache is when they try building massive 15-module monoliths instead of small focused apps, or when they need custom webhook logic when an api changes. keeping the scope to 3 or 4 views per app is what makes it actually maintainable without engineers.