Since you don't have yet a published roadmap yet, I'd like to ask your plans about this security feature:
Right now, when authorize a secret key it gets access to all endpoints, for example with "books" provides access to endpoint POST to create a new book, or GET to read all books inventory.
However, it is important for each secret key to select permissions only specific endpoints. Here are some examples with "users" table (instead of books): - one secret key is allowed to list all users, but not create or edit users (like read permissions). - one secret key is allowed to search for a specific user match, but not list all users (to verify password) - one secret key is allowed to edit users, but not create new ones (like password reset) - one secret key can create users (administrator).
A: Hi koenigworks9, We are OPEN to ANY feedback or feature suggestions you have. You can email our support and they check and analyze those further. And we have implemented a TON of new features in last 1 year based on the community feedback (see our 'Updates from NoCodeBackend' section above). Regarding your ask on Security for individual endpoint, I totally get it and it actually makes sense...
Thank you for your response, YES, I have seen your good updates based on feedback, since I had purchased your product T3 :-) Notice my comment regarding roadmap was just a fact (never a critic): many applications don't publish an open roadmap to "keep under business control" and not open "internet's free will". I do that myself as well, so I understand the reasons behind. Best regards an keep up!
Thanks very much for the videos on Greta integration, they are very helpful. There is still a lot of manual work to run it properly though. Do you have plans to allow Greta to create and delete rows etc via the API in Greta, the same as we can using Supabase? At the moment I'm not sure if I'll keep as I need to keep adding tables etc manually and it is time consuming and defeats the purpose of vibe coding to some extent. If this feature is included. I can share with my vibe coding network. Great work so far! Thank you.
A: Hi, Most of the work is taken care when you generate the APIs inside NoCodeBackend. Now it's from Greta end to have native integration with NoCodeBackend just like Supabase. You can ask Greta team to try developing this integration with NoCodeBackend within their infrastructure. Thanks
Q: Questions on GDPR/DPA timeline and future rate limits
Hi team. I'm ready to buy but have two critical questions.
On Aug 19, you said you were "very close" to a legal DPA for GDPR compliance. It's been a month, can you provide a firm timeline for its release? This is a deal-breaker for me.
Regarding upcoming rate limits: If I buy a plan now, will it be subject to these future limits? Also, if I buy Tier 2 now and upgrade to Tier 5 later when limits are active, will my upgraded plan have those limits?
Clarity on these points is needed before I can purchase. Thank you.
A: Hi, 1. We don't have any firm deadline yet for these. But we have already implemented all the critical aspects of data security and compliance such as regular data backups, ability to delete your account, email opt in, no sharing of PII with 3rd parties, etc. And once we are done with other aspects of DPA, we will have DPA published on our website.
Q: Security for individual endpoint
Since you don't have yet a published roadmap yet, I'd like to ask your plans about this security feature:
Right now, when authorize a secret key it gets access to all endpoints, for example with "books" provides access to endpoint POST to create a new book, or GET to read all books inventory.
However, it is important for each secret key to select permissions only specific endpoints. Here are some examples with "users" table (instead of books):
- one secret key is allowed to list all users, but not create or edit users (like read permissions).
- one secret key is allowed to search for a specific user match, but not list all users (to verify password)
- one secret key is allowed to edit users, but not create new ones (like password reset)
- one secret key can create users (administrator).
I'm aware it's a big request that takes long...
Riya_NoCodeBackend
Sep 25, 2025A: Hi koenigworks9,
We are OPEN to ANY feedback or feature suggestions you have. You can email our support and they check and analyze those further. And we have implemented a TON of new features in last 1 year based on the community feedback (see our 'Updates from NoCodeBackend' section above).
Regarding your ask on Security for individual endpoint, I totally get it and it actually makes sense...
Share NoCodeBackend
Verified purchaser
Thank you for your response, YES, I have seen your good updates based on feedback, since I had purchased your product T3 :-) Notice my comment regarding roadmap was just a fact (never a critic): many applications don't publish an open roadmap to "keep under business control" and not open "internet's free will". I do that myself as well, so I understand the reasons behind. Best regards an keep up!
Awesome 😃🙌🏼
Q: Greta - NCB Vs Supabase
Thanks very much for the videos on Greta integration, they are very helpful. There is still a lot of manual work to run it properly though. Do you have plans to allow Greta to create and delete rows etc via the API in Greta, the same as we can using Supabase? At the moment I'm not sure if I'll keep as I need to keep adding tables etc manually and it is time consuming and defeats the purpose of vibe coding to some extent. If this feature is included. I can share with my vibe coding network. Great work so far! Thank you.
Riya_NoCodeBackend
Sep 22, 2025A: Hi,
Most of the work is taken care when you generate the APIs inside NoCodeBackend. Now it's from Greta end to have native integration with NoCodeBackend just like Supabase. You can ask Greta team to try developing this integration with NoCodeBackend within their infrastructure.
Thanks
Share NoCodeBackend
Q: Can it import MySQL and SQL Server data?
Riya_NoCodeBackend
Sep 21, 2025A: Hi.
You can copy paste your existing MySQL commands to setup a new database, but cannot import any data.
Share NoCodeBackend
Q: API/Webhook Available?
Does this have it's own API/Webhook? Or just makes them?
-13omb3r
Riya_NoCodeBackend
Sep 21, 2025A: Hi,
We don't have our own APIs, (for different security reasons) but rather an API builder.
Thanks
Share NoCodeBackend
Q: Questions on GDPR/DPA timeline and future rate limits
Hi team. I'm ready to buy but have two critical questions.
On Aug 19, you said you were "very close" to a legal DPA for GDPR compliance. It's been a month, can you provide a firm timeline for its release? This is a deal-breaker for me.
Regarding upcoming rate limits: If I buy a plan now, will it be subject to these future limits? Also, if I buy Tier 2 now and upgrade to Tier 5 later when limits are active, will my upgraded plan have those limits?
Clarity on these points is needed before I can purchase. Thank you.
Riya_NoCodeBackend
Sep 21, 2025A: Hi,
1. We don't have any firm deadline yet for these. But we have already implemented all the critical aspects of data security and compliance such as regular data backups, ability to delete your account, email opt in, no sharing of PII with 3rd parties, etc. And once we are done with other aspects of DPA, we will have DPA published on our website.
2. If you purchase now, you will get same...
Share NoCodeBackend