Verified purchaser
Not a complete solution
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.
Riya_NoCodeBackend
Mar 5, 2026Hi,
Thanks for taking the time to write such a detailed review and for trying out NoCodeBackend. We're glad to hear that authentication and password reset flows were easier to get working for your app, and we appreciate you highlighting features like Row Level Security and MCP.
Just to clarify a couple of points for readers:
Backups: When we mention automatic backups, it refers to platform-level infrastructure backups, not user-level table restore. User-managed exports are currently the recommended way to maintain restore points. More flexible backup/restore tooling is something we’re actively evaluating.
SQL INSERT / restoration: NoCodeBackend is designed as an API-first managed backend, not a raw SQL interface, so direct SQL commands like INSERT were never part of the advertised workflow. Instead, data operations are typically handled through APIs or integrations.
Our main goal with NoCodeBackend is to make backend setup much faster for modern development workflows, especially for builders using AI or “vibe coding” tools. For example:
Direct integration with tools like Cursor and VS Code via MCP, allowing NoCodeBackend to act as a native database for apps built in those environments
Native user authentication
Automatic Row Level Security policies
Auto-generated API documentation
AI-assisted database setup
Because of this approach, we position NoCodeBackend as a cost-effective Supabase alternative focused on AI-native development and faster backend setup, rather than a traditional SQL-first database platform.
We really appreciate the constructive feedback and the recognition that the product is evolving. It helps us continue improving the platform. 🚀