Q: Clarification on Scaling, Limits & Infrastructure for Large SaaS
Hi Team,
I’m planning a serious SaaS on NoCodeBackend with a long-term target of up to 1M users, so I need clarity before scaling.
Please confirm:
1. Is there any per-second/minute API limit or burst limit?
2. Are limits per project, API key, or user?
3. What happens if traffic suddenly increases (5k+ concurrent users)?
4. Does the system auto-scale? Single or multi-region hosting?
5. Rough monthly API call capacity per project?
6. What exactly triggers Fair Usage? Any warning before restriction?
7. Can higher limits be requested?
8. Token expiry time? Refresh token support? Concurrent sessions allowed?
9. Webhook retry logic? Any webhook limits?
10. Team member limits and role-based permissions?
We are planning long-term growth and want to design correctly from the start.
Riya_NoCodeBackend
Feb 18, 2026A: Hi Shareez,
Thanks for the thoughtful questions — it’s great to see you planning for long-term scale.
Here’s some clarity:
• There are currently no strict API rate limits. We monitor fair usage based on workload patterns and data types to maintain platform stability. For example, we don’t allow blob/base64 or non-structured data storage.
• The system supports concurrent users without issues, and most applications run smoothly even during traffic spikes.
• These lifetime plans are designed primarily for startups and early-stage products. If you scale to very high usage (e.g., hundreds of thousands or millions of users), we typically work with you on a custom plan aligned with your scale and infrastructure needs.
• Auto-scaling and multi-region deployments are available for enterprise setups.
• Token expiry is 7 days by default.
• Webhook limits and team member limits are exactly as listed on the deal page.
If you expect significant scale, we’d be happy to discuss your architecture and ensure the right setup from the start.
Best,
Riya
Verified purchaser
Good questions , Waiting for an answer, as i am also wanting go full scale and these are what needs to be answered