Skip to content
Soxom

Usage limits

Each plan caps four things: seats, operations per target, Custom Code per target, and which authentication methods are available. Limits are enforced by the API at the point of action — adding a seat, configuring auth, or running a build.

Current usage for every limit is displayed in Organization Settings → Billing.

Seats

Section titled “Seats”

The number of members in your Organization, including pending invites.

Caps: Professional 10, Business 50, Enterprise unlimited.

When exceeded: inviting an additional member fails with seat limit reached. Existing members keep access; only new invites are blocked.

How to recover:

  • Remove or downgrade an existing member, or
  • Revoke a pending invite, or
  • Upgrade the plan from Organization Settings → Billing.

Operations per target

Section titled “Operations per target”

The number of operations (paths × methods) in the OpenAPI spec for a target, after filtering through the resources: block in soxom.yaml.

Caps: Professional 50, Business 100, Enterprise unlimited.

When exceeded: the build for that target fails with operations limit exceeded: <count> > <cap>. Other targets and builds for other projects are unaffected.

How to recover:

  • Narrow resources: in soxom.yaml so the target exposes a smaller surface, or
  • Split the SDK into multiple targets across separate projects, or
  • Upgrade the plan.

Custom Code per target

Section titled “Custom Code per target”

Lines of code you’ve added on extended/* branches in the Staging Repository, measured by diff against the latest codegen/next commit.

Caps: Professional 1,000 lines, Business 10,000 lines, Enterprise unlimited.

When exceeded: the build fails with custom code limit exceeded: <lines> > <cap>. The diff includes anything not present in codegen/next, so edits to generator-managed files count too — keep extensions in dedicated files to keep the count predictable.

How to recover:

  • Move custom logic into the extension directory and revert any edits to generator-managed files, or
  • Reduce the amount of hand-written code, or
  • Upgrade the plan.

See Custom Code for how to add and structure extensions.

Authentication methods

Section titled “Authentication methods”

Header-based authentication (bearer token, API key, basic auth) is available on every plan. OAuth2 requires Business or higher.

When exceeded: setting authentication.default: oauth2 in soxom.yaml or referencing an OAuth2 security scheme from the OpenAPI spec on a Professional plan rejects the build with oauth2 requires Business plan or higher.

How to recover:

  • Switch the API to header-based auth for the SDK, or
  • Upgrade to Business.