Cloud

Quotas

Quotas enforce plan limits for projects, databases, external sources, storage, branches, agent capability invocations, embeddings, and backups.

Overview

Free Controlled Beta and Builder Beta need hard caps to prevent abuse and surprise bills.

Quota checks happen before provisioning and usage-sensitive control-plane operations.

Existing DB setup is also capped: Free Controlled Beta can connect 1 live-read external Postgres/MySQL source; Builder Trial and Builder Paid can connect 3 during controlled beta.

The legacy quota field agent_runs_month means monthly agent capability invocations. It does not mean Synapsor hosts autonomous agent loops.

Spend caps keep overages disabled by default.

Developer notes

Show quota warnings before hard rejection.
When a Free project hits a limit, show: You've reached the controlled beta Free limit. Request a Builder Trial invite for higher limits.
Return structured LIMIT_EXCEEDED errors.
Use spend caps for paid plans.
Throttle background jobs under tenant budgets.

Quota check

REST

GET /v1/control/quota-check?project_id=acme-support
Authorization: Bearer <account-session-token>

Examples

json

{
  "allowed": true,
  "plan": "free",
  "limits": {"projects": 1, "databases": 1, "external_sources": 1, "branches": 2, "storage_gb": 1},
  "usage": {"projects": 1, "databases": 0, "external_sources": 0, "branches": 0, "storage_gb": 0}
}