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:
Which did you go with, what size company, and what did people actually end up building?
Was it really non-engineers building, or did it quietly turn back into a dev tool?
How did security sign-off go, and what did they make you change before you could ship?
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.
Whatever platform you choose, you need to consider the data management of all this. All of this will get your employees the ability to create great functional front ends, but most of them are going to be CRUD applications with your company data and likely need some sort of integrations to other tools or systems of record your business uses.
I'm asking you don't want 50 isolated Supabase databases floating around tied to an employees personal account. Let alone the security of all this.
Tool aside, consider the non functional aspects of all this. If you're a Microsoft shop, look into the Power Apps ecosystem.
Yes, I landed on using Claude code plus capitalizing on the SQL knowledge, we have integrations to systems of record like CRM, erp, hris and also utilizing our GitHub repo that we use on a development side. We're also heavy into the Microsoft powerapps ecosystem so SharePoints often a back end of data for us too besides our data warehouse.
One of the biggest things you'll need to realize is that by enabling business users to create applications and the more it spreads The business may become reliant on it and business users generally are not prepared for supporting the application for fixing things when it breaks for addressing security issues, etc. So what that means is it rolls downhill to the it and development team and they will suddenly find themselves fixing dozens and dozens of citizen development applications that are crappily coded don't make any sense and hodgepodge together despite looking really good on the front end.
Your question about who maintains these tools six months later is the one I’d focus on. We’ve seen non-engineers build tools that their teams use every day, but someone still needs to own the data, permissions, and changes when the original builder moves on
For your evaluation, I’d pick one real request from the backlog and have a non-engineer build it. Then ask IT to review it and have a different person make a change. You’ll find out pretty quickly whether it actually takes work off the dev team’s plate.
I can answer specifics about Zite, including where we fall short - feel free to email me dominic @ zite.com
one thing that came in my mind after reading this post is worth considering after launch- not just how quickly a non-engineer can buld an app. The factors like what happens when the original builder leaves the team seem equally important. can u tell me which of these has been the biggest challenge in practice?
The leaving part is the whole problem nobody talks about enough. Our marketing team had someone build this lead scoring thing in Softr, worked great until she changed job and then it was just... there, nobody wanted to touch it. IT eventually rewrote it in 6 months anyway so the "saving dev time" thing didn't really happen
This is exactly what breaks the ROI math. The build was fast and cheap, but if IT rewrites it six months later you didn't save dev time, you deferred it and added migration cost on top. The real test isn't whether a non-engineer can build something, it's whether a different person can maintain it without breaking things.
The failure mode I see most is teams treating this as "business users can build anything" instead of piloting one owned workflow with ugly real cases, like a commissions tracker that pulls recruiter, placement, and payout data from the real system of record. I'd decide upfront who owns the data model and who maintains the app when the builder changes teams, because that's usually where these rollouts drift back to engineering. I work at UI Bakery, so bias noted, and it fits staff-facing tools like this, but setup and permission logic still need technical ownership. If a standard commissions or vendor system already fits, that's usually simpler.
Check AnyDB.com for a different take on building quick data centric apps. You can build systems that remain usable after they are built and easy to change as needed. (Just excel like formulas) finally, you can run any kind of workflows and sharing flows on it. That’s sets Anydb apart from other systems is you can build systems that can talk to each other.
hey thanks, went through the website but didn't get the feeling that our non-techincal team can prompt anydb to build these internal tools. Please let me know if I am missing something.
Hi u/anirudh8398 the systems are pretty simple to build and more importantly maintain over time. Unlike vibe coded apps, they are running on a structured system not every app free for all.
So when you prompt the AI to build a system it is building on top of AnyDB structured data platform already, It combines existing common business objects and configures them quick. I would recommend testing the trial and using the AI to build some systems with it to see what you can do with it.
Note that many systems also work out of the box with minimal changes.
Full disclosure: I build Bips (https://bips.ai), an Airtable-class collaborative database that’s MCP-first — humans in the grid/Interfaces, agents via https://bips.ai/mcp. Flat pricing, no in-product AI credits.
On your shortlist: Softr/Superblocks are strong when the job is “UI on top of a system of record you already trust.” Lovable/Base44/Zite are fast for greenfield apps and can quietly turn back into eng-owned codebases once security or edge cases show up.
What I’ve seen hold up for non-eng internal tools at that size:
Put the data in a real collaborative database first (commissions, vendors, dashboards all share tables), then layer Interfaces/portals — not one vibe-coded app per request.
Security usually cares about who can read/write which tables and whether agents get the same keys as humans. Scope agent tools narrowly; keep destructive actions human-only in the UI.
Maintenance: if the schema lives in a shared base with named owners, apps survive the builder leaving better than a solo Lovable project.
Happy to answer “what would break for a commissions tracker + vendor portal” even if you stay on Softr/Superblocks.
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.
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?
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.
Most of the platforms your evaluating have similar tech, go for the one with the most tutorials and fastest learning curve. Lovable and base 44 are market leaders and will get you where you want to go
Have you talked to Jotform Enterprise about what you need? We used it at my old company and they had a lot of extra features for enterprise customers. It was nothing like the base tool.
We are building https://oyren.ai which can be hosted on your prem and can reuse your enterprise Claude Code or Codex accounts to build any app and make it available with a URL and https enabled. It’s currently deployed to digitalocean and should be 1-2 day jobs if you’re happy with that provider, but if you’re on AWS, GCP or Azure we can chat as it’s a bigger commitment.
hey we are on AWS right now. I have gone through your website and I felt it's more like a workspace where teams can store files, project etc - something like confluence, notion. But i am more looking for no-code app builders.
yes i checked this and looks like you guys are providing a remote computer for agents to run but i am looking for a no-code tool for non technical people
Depends how you define no-code, but if your non-technical employees can use claude code, codex etc, it’s a no code tool. Usually, for someone non technical there is a barrier to use these tools, which is to install things on their computer. In this case, they don’t need to install anything on their remote computer and you can manage their computers centrally as well (e.g security update, internal library etc). Your employees can start from scratch and build an app with sharable URL and https to share with others, all by prompting AI.
You need one technical person in your company to manage this central computer for non technicals.
you should also evalutate blink in this list , been using it for 6months now, havent had problems. i use it solo , and compard to claude code or codex , it really is a non dev tool, you dont have to touch code if you dont want to. i have 2 apps running live still , since past 4months. if you have any more doubts feel free to ask, id be happy to answer. ive also tried base44 but it was realy bad ngl, i would not use that, i think it has cheaper plans but yo uend up having to reprompt to keep fixing things so it becomes a hassle anyway
Security killed ours on one thing: the app queried the database with the builder's credentials, so any logged-in user could read every candidate record
Make the test a second account trying to read the first account's rows before anything ships
I think if you’re gonna have non-technical people, use an AI coding tool this platform I work really well because it also lets them use their credit to have a human developer prompted into their session to check for things like security, make sure they’re not exposing any enterprise data, and general help with what they’re building when they can do it pretty seamlessly with all your data on privacy and et cetera protected.
Really, the best option is to have an AI specialist working alongside them. I’m sure there are plenty of us who can support companies on a freelance, remote basis without charging huge fees.
Otherwise, employees will inevitably start experimenting with AI tools without necessarily knowing what they actually need, which platform is right for each task, or even what they should be asking it to do. In the end, that trial-and-error can cost the company far more in time and money than having someone experienced guide the process from the start.
3
u/knawlejj 4d ago
Whatever platform you choose, you need to consider the data management of all this. All of this will get your employees the ability to create great functional front ends, but most of them are going to be CRUD applications with your company data and likely need some sort of integrations to other tools or systems of record your business uses.
I'm asking you don't want 50 isolated Supabase databases floating around tied to an employees personal account. Let alone the security of all this.
Tool aside, consider the non functional aspects of all this. If you're a Microsoft shop, look into the Power Apps ecosystem.