Limits
Quotas across products – free-tier allowances and paid-plan ceilings.
Norcube enforces a handful of hard quotas to keep behaviour predictable.
Hitting one returns 403 LIMIT_EXCEEDED (when you try to create a
resource) or queues work (when concurrency is the limit).
LangSync
| Code | Default (free) | Description |
|---|---|---|
LANGSYNC_CONCURRENT_TRANSLATIONS | 5 | Maximum simultaneous AI translation jobs. |
Plus rate limits on cost-driving endpoints – see LangSync → Limits and errors.
Backup
| Code | Default (free) | Description |
|---|---|---|
SNAPDB_MAX_DATASOURCES | 5 | Max data sources per organization. |
SNAPDB_CONCURRENT_BACKUPS | 2 | Max simultaneous running jobs. |
See Backup → Limits and errors.
DomainRadar
| Code | Default (free) | Description |
|---|---|---|
DOMAINRADAR_CONCURRENT_CHECKS | 30 | Max simultaneous lookups in flight. |
DOMAINRADAR_MAX_BULK_DOMAINS | 1,000 | Max domains per bulk job. |
Plus monthly free-tier allowances per check method and rate limits per hour. See DomainRadar → Limits and errors.
See your current usage
app.norcube.com → Limits (in each product's sidebar) shows your live usage vs each limit.
Paid plans
Paid plans raise every concurrency and monthly-allowance limit substantially. Enterprise plans support custom limit overrides per code via admin tooling.
See the pricing page for each product's specific ceilings. Reach out via the dashboard to discuss custom limits.
Behaviour and edge cases
- Limit checks happen at request time, not on a schedule. The current-usage counter increments and decrements as jobs start and finish.
- Concurrency limits queue, they don't reject. Submitting a 6th concurrent translation when the limit is 5 doesn't fail – it waits.
- Resource-count limits reject on the create endpoint. The 6th data
source
POST /datasourcesreturns403 LIMIT_EXCEEDED. - A blocked organization (failed payment, hard cap hit) has every write blocked, regardless of limit headroom. See Dunning.