NoCodeBackend Reviews

I have absolutely loved using NoCodeBackend for projects in the past. It was easy to set up and use initially. However, I came across a major issue and when I inquired, I was told it just won't work. Once you have built everything, if you need to edit and file within a table, it simply cannot be done.

I had to build a frontend that allowed me to edit data files in my database. I have since moved back to supabase for my larger projects.

Great software for simple projects where editing a file on the backend for a client is not needed.

EDITED: Received your reply. The support team stated record editor wasn't working but I could edit via APIs. That is why I built the frontend. After I responded, the support team went dark and failed to respond again.

I used NoCodeBackend MCP to set up the database for three mini‑projects that had been sitting on my shelf for way too long. The real blocker wasn’t the ideas, it was my lack of confidence around setting up a backend quickly, cleanly and then iterating on it....

The MCP just worked. I used it with Codex and everything ran smoothly. Updating the database schema while vibe coding felt almost effortless, which is not something I say often.

Honestly, it’s been a long time since a tool saved me this much time and effort. Then having a clean API to move data around without friction made the whole experience magical.. This solves a very real problem, and it does it incredibly well.

Honestly, I was very very skeptical. Bought it this week, love it so far.

This tool is my top 1 purchase.
Since I'm using nocodebackend I can create MVPs in hours

Here's my build :
Claude 4.6 + PM book as reference + user pain point , user interview

To create user journey mapping, data modeling , feature listing

The I review files and transform them into clear user stories

Then I use Claude + MCP Server Nocodebackend + Bind Ai or Greta for the front.

With MCP servers it's very easy to setup and manage ur DB

I bought the highest tier no regrets everything is clean and the founder + team do YouTube content that is simple , actionable and WORKING as it is presented

No fluff , no surprise !

I got NCB to use as a backend to Greta after failing to get password reset emails working in Supabase in the first iteration of an app I am developing (despite thousands of Greta Tokens, consulting ChatGPT, Supabase help bot etc). That process was certainly much easier with NCB.

NCB is generally easy to use and the recent addition of Row Level Security is a real boon, as is MCP, which will simplify connecting to front-end development apps. Greta will apparently be providing MCP support by end of February 25.

Help is via YouTube videos that cover much of what you might want to do. And support is via email, which is responsive. Development seems pretty speedy, however there is no published roadmap.

One thing to be aware of is that while NCB state on their website that backups are 'automatic', that applies to NCB's own system backup, not users. That is, if you make an error and accidentally delete a table, say (as I have done) or somehow corrupt your data, there is no NCB recovery. NCB's recommendation is to export your data yourself if you want a backup. The restore is problematic though as NCB doesn't support the SQL INSERT command. They recommend you use something like Zapier or Make to re-load records individually. Hardly optimal.

I appreciate NCB is a work in progress and I really like the concept, so I'm prepared to cut it some slack because of that. However, as others have commented, lack of transparency and data security is a concern and some of their claims e.g. comparisons with Supabase, for example, are exaggerated.

Review: I am updating my review to 5 stars to reflect the exceptional interaction I just had with the support team.

My Initial Experience: Originally, I faced some technical hurdles regarding domain validation (my specific TLD was rejected) and I had concerns about implementing frontend security without a native user authentication system. I was initially frustrated because it blocked my specific use case.

The Turnaround: However, the team's reaction was outstanding. Instead of ignoring the feedback, they engaged in a real technical discussion with me.

They are currently actively working with me to resolve the domain validation constraints.

They listened to my feedback regarding security and confirmed that Native User Authentication is already in the testing phase and coming very soon.

Verdict: It is rare to find a SaaS team that listens to critical feedback and acts on it so fast. While we are still finalizing the setup, I am upgrading my rating to 5 stars specifically for their transparency, their technical expertise, and their dedication to making the platform production-ready.