Reference

Limits and quotas

Kubeadapt usage meters, export caps, attribution caps and API rate limits, and where to see your current usage.

This page lists the limits Kubeadapt applies today and where to see your current usage: usage meters under Settings → Billing, caps that apply to every organization (export row counts, attribution team splits), and API rate limits.

Usage meters

The Billing tab (Settings → Billing) shows four usage meters for the current 30-day window. There is no namespace limit and no API rate-limit meter on this page.

Meter	What it counts	Display unit
Clusters	Connected clusters in the organization	count
vCPU avg (30d)	Mean vCPU averaged over the trailing 30 days	vCPU
Members	Organization members with any role	count
Data retention	Days of cost data retained for queries	days

Each meter shows used over max. Unlimited values render as the infinity glyph and the meter labels itself "Unlimited".

When the used value reaches the max, the meter shows "Full"; above 80%, it turns amber. The max values come from your organization's billing configuration.

Retention specifics

The data-retention meter shows current retention in days against your plan's maximum. When the retention max is 365 or more, the label switches to year-rounded form: "Full — 1-year retention" instead of "Full — 365-day retention".

Cost Explorer export caps

Both the CSV and PDF exports cap their output. Bigger queries don't fail — they return the first N rows with a toast asking you to narrow filters.

Export	Cap
CSV	10,000 rows
PDF	500 rows

The cap applies after the current group-by, filters, cost mode, and time window are applied. If you need a larger CSV, group at a coarser level (namespace instead of pod, controller instead of container) or narrow the date range.

PDF exports are designed to be shareable artifacts — 500 rows fit cleanly into the report layout. CSV is the path when you need the full dataset; for queries that would exceed 10,000 rows, run multiple exports broken up by namespace, cluster, or time slice and concatenate.

Attribution caps

Maximum teams per workload (10)

Every namespace, workload, or PV can be cost-split across up to 10 teams, with percentage weights that must sum to 100. The limit applies to all three entity kinds.

Where it bites: the "Split cost" dialog in the Assignment Workbench refuses to add an 11th team; submitting via API with more than 10 weighted-team entries returns a validation error.

If you need to attribute cost across more than 10 teams, build the split at the namespace level instead of the workload level (so the same 10-team split applies to every workload in the namespace), or use Departments — a Department can hold any number of Teams.

Label-based attribution

Label-based attribution has no cap on the number of distinct label values. The 10-team cap only applies when you're manually splitting cost in the Workbench.

Channel and rule caps

Smart Alerting has no cap on the number of rules or channels per organization. The four supported channel kinds are:

Slack: incoming webhook URL.
Email: distribution list.
Webhook: POST to a configured URL with the incident payload.
In-app: bell icon in the Kubeadapt UI.

The four configurable alert types are documented in Smart Alerting → Rules.

API limits

API rate limits are not shown on the Billing tab. The REST API allows 100 requests per minute per API key (sliding window; 429 RATE_LIMITED with Retry-After) and 6 per minute per key on the FOCUS export. List pages are capped at 500 rows, Cost Explorer pages at 100 rows (10,000 with export=true), and request bodies at 1 MiB. Contact support for a higher limit. See Rate limits.

What's not capped

A short list of things readers sometimes assume are capped but aren't:

Namespaces per cluster: no limit. Every namespace the agent observes is captured.
Dashboards saved per user: no hard cap.
Reports archived: no hard cap.
Snapshot frequency: set agent.config.snapshotInterval in your Helm values (default 60s, minimum 10s). Shorter intervals increase load on your cluster.