Henry_CQ: API usage and future plans?
Hi team,
I’m currently evaluating your platform and had a couple of questions regarding API usage and future plans:
1. Does NocodeBackend provide built-in rate limiting for its auto-generated APIs?
2. If yes, how is it configured (per API key, per user, or global limits)?
3. If not, are there any recommended ways to implement rate limiting when using your platform?
Also, I couldn’t find a public roadmap.
4. Do you have any roadmap or an upcoming features list available?
5. How can we stay updated on what new functionalities your team is currently working on?
Thanks in advance for your support!
Riya_NoCodeBackend
Mar 22, 2026A: Hi there, thanks for your questions!
1–3. Rate limiting
We don’t have built-in rate limiting on our APIs at the moment.
However, you can enforce rate limits on your side by introducing a middleware or proxy layer in front of our APIs. This layer can control request frequency before forwarding calls to NoCodeBackend. You can leverage tools like Cursor or similar to quickly set up this logic.
That said, built-in rate limiting is on our roadmap and planned for the future.
4–5. Roadmap & updates
While we don’t maintain a public roadmap, we’ve been consistently shipping updates over the past year, with both major releases and continuous improvements. Recent highlights include:
1. MCP Server (integrations with Cursor, Antigravity, Claude Code)
2. Row-Level Security (RLS)
3. AI-powered database editing
We actively share all updates via:
-Email newsletters
-YouTube videos
-AppSumo “Updates” section
So you’ll always stay up to date with what we’re building and releasing 🚀