Plans and limits
These are repository defaults. Active catalog settings determine feature availability; project, monitor, and asset counts are backend plan quotas. Feature toggles do not change those counts. API-key quota settings can override defaults.
| Limit | Free | Teams | Enterprise |
|---|---|---|---|
| Active API keys | 5 | 10 | 25 |
| Custom projects (capability workspaces included) | 3 | 100 | 100 |
| Monitors | 3 | 25 | 100 |
| Assets | 0 | 20 | 200 |
| API requests/second | 5 | 50 | 1,000 |
| Concurrent API requests | 10 | 50 | 500 |
API-key creation also has a five-per-minute rate limit. API token buckets allow a bounded two-times burst; sustained traffic must remain within the limit.
Each new API key can be assigned to one project and given an optional UTC calendar-month credit cap. Project workspaces group matching sources and MCP tools; they do not store lists of indicators.
Feature availability
Free includes lookup, projects, and monitors. Teams enables additional detection, asset, and Slack capabilities. Rules/conversion/YARA MCP tools require Teams or Enterprise. Providers still need applicable configured credentials.
Dashboard, billing, key management, BYOK, notifications, and Settings are account surfaces. A plan flag for a future feature does not implement that feature.
Teams and Enterprise accounts can create a team workspace, invite verified members by email, and share portal projects, saved lookups, and monitors. Members choose a team or personal workspace; their personal dashboard and profile stay private. Team admins manage roles, invitations, and settings.
Enterprise accounts can create an organisation with multiple sub-teams. Organisation admins can manage and inspect their sub-teams; members see resources only in their selected team. Organisation access does not cross tenant boundaries.
Deployment and enterprise scope
OAuth requires provider configuration; SAML/SCIM scaffolds do not establish completed enterprise SSO. Native Microsoft Teams alerts, white-label tenant APIs, AI endpoints, configurable enterprise retention, and packaged OEM workflows are not established shipped capabilities. Uptime, residency, and support guarantees must be confirmed through your contract and deployment.
Rate-card execution uses configured tool and source prices; cached, BYOK and failed work adds no charge. Flat billing remains available during rollout.
See credits for grant and charge behavior.