Skip to main content

Rate limits

urBackend enforces per-IP rate limits to keep the service stable for all projects. Requests that exceed the limit receive a 429 Too Many Requests response. Design your client to back off and retry after the rate limit window resets.

Storage limits

Files that exceed the limit return 413 Payload Too Large.

Database limits

When your project approaches the database quota, writes may be rejected with 403 Forbidden. Monitor your usage in the Dashboard.

AI session limits

AI features (like the AI Query Builder) that use urBackend’s platform Groq key are capped per account, per calendar month: Requests beyond the monthly cap return 403 Forbidden until the counter resets on the first of the next calendar month (UTC). To bypass this cap, configure a personal Groq API key at the developer or project level. Requests that resolve to a BYOK key are not counted against the platform cap. See BYOK for AI.

HTTP status codes

If you are using webhooks, respond to incoming webhook requests within 10 seconds. urBackend retries failed deliveries with exponential backoff, so a slow response can trigger unintended duplicate processing on your end.