Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Consumption and quotas

On this page (11)

Consumption is the use of resources (processing and AI), paid in credits. Quotas are the limits applied by each plan. This is the workspace's financial-operational dashboard.

Concepts#

  • Usage credits: balance in R$ that covers cloud consumption (processing queries, AI egress).
  • Monthly allowance: the included credits of the plan, credited exactly once per cycle (YYYY-MM).
  • Top-up: additional credits purchased (Pix), added to the balance.
  • Entitlements: resource limits per plan (scheduled reports, recipients, refresh modes, etc.).
  • Cost guardrail: byte-per-query cap that prevents surprise bills.

Availability#

  • Plans: all include an allowance, except Enterprise/custom (0 included credits — contract governs).
  • How it works: allowance, ledger and entitlements are deterministic and covered by automated tests.

Entitlements per plan#

EntitlementStarterGrowthBusinessScaleEnterprise
Scheduled reports110unlimited*unlimited*unlimited*
Recipients per report31050200200
Executive narrative by AI—✓✓✓✓
PDF attachment in report——✓✓✓
Smart alerts——✓✓✓
Update modesbatchbatchbatch, near_rtbatch, near_rtbatch, near_rt
Ingestion cadencedaily batchdaily batchbatch, micro-batch (5/15 min)batch, micro-batch (5/15 min)batch, micro-batch (5/15 min)

* "unlimited" = very high cap (999) in practice. Live mode (rt) only with own cloud (BYOC), outside the plan.

Permissions#

  • Managing credits/top-ups/plan requires owner (billing.manage).
  • Running actions that consume (query, refresh, AI, export, report) requires appropriate roles and fine-grained permissions — see Users and permissions.

Configuration#

  1. Monitor balance and statement in Custos / Consumo.
  2. The allowance is credited automatically per cycle (payment webhook + safety net via daily cron).
  3. Top up credits via Pix whenever you want headroom above the allowance.
  4. Adjust the entitlements by switching plan.

Validation#

  • The statement distinguishes franquia (franquia:<ws>:<ciclo>) from top-up (payment id) and from storage — each in its own bucket.
  • The allowance is idempotent: reprocessing the same cycle does not credit it twice.
  • The AI ledger is atomic (reserve → settle): consumption never "leaks" the cap.

Example#

Comércio Aurora (Growth) receives R$ 150 of allowance at the start of the cycle. When running pipelines and AI questions, consumption is debited from the balance. In a peak month, Maria tops up another R$ 300 (Pix) — the statement shows "Monthly allowance for the Growth plan — cycle 2026-09" and the top-up separately.

Cost#

  • Monitoring consumption/quotas: R$ 0.
  • Actual consumption (processing/AI) debits credits. The BRL amounts shown before a run are estimates; the amount charged is the one on the invoice.
  • The per-query volume cap limits cost per query.

Security#

  • Atomic AI ledger + fail-closed rate limit: without credits, the resource refuses (does not proceed "in the dark").
  • Budgets per workload are advisory and fail-closed — the platform never switches the execution mode by itself.
  • Consumption is audited per workspace.

Limits#

  • Advisors and budgets guide usage at large volumes; response time depends on the volume and the query.
  • No expiration/rollover of allowance today: the allowance adds to the single balance.
  • No pro-rata for mid-cycle upgrades (granted cycle is not recalculated).
  • /api/v1 (REST/OData) has fail-closed rate limit per key and per workspace. The REST query API is in early access and not yet open for external use.

Troubleshooting#

SymptomLikely causeWhat to do
Expensive action blockedusage credits balance exhaustedtop up credits (Pix)
"This month's AI usage limit has been reached"workspace monthly AI cap (default R$ 50/month; zero = no cap)contact the administrator — it's a separate control: topping up credits does not raise the cap, which resets at month boundary
Allowance did not appearcycle not processed / plan without included creditswait for the cron; Enterprise has no self-service allowance
Query cut due to costreached the per-query volume capreduce the query scope
Recipient limitplan cap per reportupgrade or reduce recipients

Next steps: Suspension and delinquency.

Related links