Skip to main content

Limits and Configuration

This page lists the limits and settings that affect how you integrate with and operate OpenProdkt. For each one it states the value and unit, who can change it, and what happens at the boundary.

How to read it:

  • Enforced defaults are not service-level commitments. A value here describes what the software enforces. It is not an availability, latency, or capacity guarantee, and no throughput is promised. Latency objectives, and how far each has been validated, are on Performance Objectives; they are objectives, not commitments.
  • Fixed means the value is built in and no customer or operator setting changes it.
  • Plan means the value comes from the organization's entitlement, and a signed license can override it.
  • Operator means a self-hosted operator sets it with an environment variable and a restart.
  • Hosted-service infrastructure settings (gateway throttles, instance sizes) are not customer configuration and are not listed.

Plan quotas and rate limits​

Built-in plan profiles​

Entitlements define request-rate budgets and monthly quotas. The built-in profiles are below. A signed license (self-hosted Enterprise) can replace any of these values. Confirm the profile and any license override for your organization with your account team, because plan names and packaging can change.

ProfileRequests per second (integration)Decisions per monthApprovals per monthNotifications per monthSeats
Sandbox (hosted partner trial or self-hosted trial, 30 days)25500,000500,0001,000,0003
Free15,0005,00010,0001
Business25500,000500,0001,000,00025
Enterprise1,000No capNo capNo cap25

The approval quota equals the decision quota. The notification quota is twice the approval quota. A notification is an approval lifecycle event sent through email or webhook.

Dashboard budgets are separate from integration budgets. Defaults (provisional, and subject to change) are 60 requests per second for dashboard reads per organization and 20 requests per second for any single dashboard endpoint. Both are plan values and a license can override them.

Request-rate limits​

  • Scope. Per organization, never per key or user. Adding keys does not raise a limit.
  • Window. One second. Counters are shared across all API replicas through the database.
  • Budgets. Integration (requests.per_second) covers API-key requests and JWT requests other than GET. Dashboard (dashboard.requests_per_second) covers JWT GET requests. A per-endpoint cap (dashboard.endpoint_requests_per_second) applies inside the dashboard budget. The budgets do not draw from each other.
  • At the limit. HTTP 429. Retrying later is safe; nothing was evaluated.
  • If the counter store is unavailable. HTTP 503. Requests are refused rather than allowed.
  • Zero. A license value of 0 is a limit of zero and blocks all requests in that class. It does not mean unlimited. Negative values and unknown limit names are rejected when a license is loaded.

Monthly quotas​

  • Scope and period. Per organization, per calendar month in UTC. Usage resets at the start of the month.
  • What counts. One decision unit per recorded billable decision, including a policy-evaluation failure. Not counted: unknown assets (asset_not_registered), assets with no policies (no_policies_assigned), duplicate requests for the same pending operation, invalid input rejected before evaluation, and dashboard reads. Approvals and notifications are counted when created.
  • At the limit. HTTP 402 with decision_quota_exceeded, approval_quota_exceeded, or notification_quota_exceeded. The call is not evaluated and the upstream is not called by the control plane. A retry fails until the month changes or the plan changes.
  • Atomic. Usage is reserved atomically with the decision, so concurrent requests cannot exceed the quota.
  • Playground. Console playground evaluations of registered assets use the same decision quota.
  • Read usage. GET /v1/usage returns consumption and limits.
  • Unlimited. A plan with no practical monthly limit reports the largest integer JavaScript represents exactly, 9007199254740991 (2^53-1), in the limits of GET /v1/usage and in the quota fields of GET /settings. Treat a value at that number as unlimited.

Licensing​

Signed licenses are verified against the deployment's public key and cached for 1 minute. A license can set the limit names above, members.seats, and feature flags. Unknown names are rejected. Check Plans & Licensing for modules and delivery.

API request limits​

ItemValueNotes
List page size limit1 to 100, default 25Outside the range returns 400. Applies to audit, approvals, API keys, and other list endpoints that document it.
offset0 or greater, default 0Negative returns 400.
Decision metadata size8 KiB of serialized JSONLarger returns 400. See Policy Engine.
Known metadata string keys256 charactersprovider, model, operation, environment, actor, application.
Metadata and policy numeric precision128 significant decimal digitsFixed, not customer-configurable. Excess precision is rejected, never rounded.
Normalized numeric decimal exponent-308 through 308, inclusiveFixed, not customer-configurable. Out-of-range values are rejected. See exact numbers.
Numeric token length4,096 charactersIncludes sign, decimal point, and exponent; fixed, not customer-configurable.
Metadata / individual policy-value depth64Root depth 0; add one per property/array element, including scalar leaves. Fixed; not a whole-request or composite-policy-tree limit.
AI metadata countersIntegral values in the client/runtime rangeNative Go int, Python signed64, TypeScript safe integer; fractions, numeric strings, and overflow are rejected without rounding. No decision usage or upstream execution on invalid context.
metadata.ai.attachment_count64Maximum value.
operation_id1 to 128 characters of letters, digits, ., _, :, -Evaluate requires only non-empty; status, audit filter, and proxy challenge enforce the pattern.
traceparent request headerAt most 512 characters, lowercase hex, W3C layoutOptional on evaluate and proxy evaluate. Invalid, repeated or comma-joined values are ignored and start a new trace; they are not an error. Fixed. See Trace context.
Outcome execution_idLowercase UUIDv7Optional. A malformed or null value returns 400 invalid_request and stores nothing. Fixed.
Outcome attemptInteger 1 to 2147483647Optional. Out-of-range, fractional and non-integer values return 400 invalid_request. Fixed.
Outcome upstream_request_id1 to 128 characters of letters, digits, ., _, :, -Optional. Fixed.
Asset ai_inventoryAt most 2 KiB encoded; purpose at most 512 UTF-8 bytes; references at most 256 charactersOptional. Invalid, null, empty or unknown members return 400. Fixed. See AI inventory on assets.
API-key lifetimeUp to 365 days from creation or rotationA later expiry is refused. Keys must be rotated at least yearly.
Total request bodyNo documented limitKeep requests small. Not a guarantee of acceptance.

Approvals and grants​

ItemValueChangeable
Pending approval expiry24 hoursNo
Grant window after approval2 minutes (120 seconds)No
Proxy Retry-After30 secondsNo
Operation claim lease5 minutesNo
Outcome reports per operationFirst report winsNo

Details and retry behavior are in Approvals.

Enforcement controls​

ItemValueChangeable
Enforcement mode defaultpermissive for every organizationBy a super_admin
Mode overridesAt most 50 per organization, shared by the environment, asset type and risk tier dimensions; value 1 to 128 characters for environment and asset typeNo
Definition pin observationAt most 512 bytes; server_version at most 128 characters; at most 20 distinct observed digests recorded per asset and pinNo
Shadow report windowAt most 90 days (default 30); at most 250,000 events per request; 5 second query limitNo
Kill switch reason1 to 200 charactersNo
Active kill switchesOne for the organization, one per asset, at most 100 per-asset switchesNo
Break-glass duration1 to 240 minutesNo
Break-glass pending window60 minutes to decide a requestNo
Break-glass grantsAt most 5 active and 10 pending per organizationNo
Break-glass reason and note1 to 200 characters (reason), at most 200 (note)No

Details are in Enforcement Modes, Kill Switch and Break-Glass. These are enforced limits, not a throughput guarantee.

Sign-in and sessions​

ItemValue
Sign-in code lifetime5 minutes
Minimum wait between code requests30 seconds
Code request window and maximum5 requests per 10 minutes
Code verification attempts5
Session idle timeout30 minutes
Session maximum lifetime12 hours
Denied registration cooldown7 days

These are fixed.

Integration limits​

SDKs​

ItemGoPython and TypeScript
Request timeout5 seconds defaultSee SDK Manual
Webhook signature replay window5 minutes300 seconds
Webhook body size read by the verifier256 KiBSee SDK Manual

Approval wait and polling bounds are in the SDK Manual.

MCP stdio wrapper​

SettingDefaultRange and behavior
pdp_timeout5 secondsGo duration. Bounds each decision call and each outcome report attempt. On timeout the call is denied (pdp_unavailable).
Outcome report attempts4 attemptsWaits of 250 ms, 500 ms, then 1 s between attempts. A definitive 4xx other than 408 and 429 is not retried. Not configurable. Every attempt of one report carries the same optional execution_id, attempt and upstream_request_id.
Message size1 MiB per newline-delimited messageAn oversize message gets a JSON-RPC invalid-request error. Applies to the client and the child server's output.
Shutdown grace5 secondsFixed.
Principal token fileMode 0600, regular file, at most 64 KiBThe wrapper refuses to start otherwise.

Envoy authorization adapter​

SettingDefaultBehavior
OPK_AUTHZ_PDP_TIMEOUT2 secondsBounds the decision call for HTTP and gRPC routes. On timeout the adapter returns 503 pdp_unavailable and the upstream does not run.
MCP decision timeout5 seconds, fixedMCP routes ignore OPK_AUTHZ_PDP_TIMEOUT.
OPK_AUTHZ_LISTEN_ADDRESS:9191Listen address.
Request body buffer1 MiBUsed for payload binding and MCP tools/call. Larger MCP bodies return 413 payload_too_large; larger bodies on a payload-bound HTTP route are rejected as malformed.

MCP denials and protocol errors on the Envoy path are returned as HTTP 200 JSON-RPC bodies. GET and DELETE requests carrying a body are rejected with body_not_allowed.

Webhooks​

ItemValueNotes
Connect timeout10 secondsFixed.
Overall request timeout10 secondsFixed.
Redirects and proxiesNot followed or used
SuccessHTTP 2xxAnything else is a failure and is retried.
Default event typesapproval.pending, approval.approved, approval.rejected, approval.expired, approval.revokedUsed when you create an endpoint with no eventTypes.
Schemehttps in saas product mode; http also allowed in other modesSet by the deployment.
Destination policyPrivate, loopback, link-local, and reserved ranges refused; cloud metadata addresses always refusedSelf-hosted operators can allow ranges with OPK_WEBHOOK_ALLOWED_CIDRS.
SignatureX-OpenProdkt-Signature: v1=sha256=<hex> over timestamp + "." + bodyTimestamp is generated at delivery time.

See Approvals for retry semantics and On-Premises Webhooks for the CIDR setting.

Outbox dispatch (self-hosted)​

The API server dispatches outbox events (approval emails, webhooks, approval lifecycle records). Set these on the API server and restart it. Invalid, empty, or out-of-range values fall back silently to the default; check the effective value in your configuration management.

VariableDefaultRange
OPK_OUTBOX_DISPATCH_ENABLEDOff (unset is off)Boolean. Any value that is not a valid true value is off. Nothing is dispatched while off.
OPK_OUTBOX_DISPATCH_INTERVAL5sGo duration greater than zero.
OPK_OUTBOX_DISPATCH_BATCH_SIZE201 to 500. A larger value is capped at 500.
OPK_OUTBOX_DISPATCH_MAX_ATTEMPTS51 to 50. A larger value is capped at 50. After the last attempt the event is dead-lettered.
OPK_OUTBOX_DISPATCH_JITTER_RATIO0.200 to 1. A larger value is capped at 1.

Retry backoff starts at 1 minute, doubles, and is capped at 1 hour. It is not configurable.

Audit export and retention​

Set these on the worker and restart it. See Audit for what is exported.

VariableDefaultRange and behavior
OPK_AUDIT_EXPORT_LAG_SECONDS60 secondsMinimum age of a row before export. Unset, non-numeric, or zero or negative falls back to the default.
OPK_AUDIT_EXPORT_INTERVAL_SECONDS300 secondsTime between export cycles. Same fallback.
OPK_AUDIT_EXPORT_BATCH_SIZE500 eventsMaximum events per export object. Same fallback.
OPK_ARTIFACT_OBJECT_LOCK_MODECOMPLIANCECOMPLIANCE or GOVERNANCE.
OPK_ARTIFACT_RETENTION_DAYS2555 daysMinimum 2555. In deployment-retention builds, an explicitly empty, non-integer, zero, negative or lower value stops startup rather than silently selecting a default.
OPK_WORKER_DEDUPE_SIZE10,000 message IDsIn-memory duplicate filter. It is lost on restart, so duplicates are still possible.
OPK_WORKER_ARTIFACT_PREFIXDeployment defaultObject key prefix for approval records.
OPK_WORKER_QUEUE_TOPIC (or OPK_OUTBOX_QUEUE_TOPIC)RequiredQueue the worker reads.

The object-storage bucket must have Object Lock enabled when it is created. It cannot be turned on later for an existing bucket, and the worker checks at startup.

Deployment retention configuration​

Availability. Applies to builds containing deployment retention configuration and native storage drivers. Confirm the build with your account team; this does not announce a new release.

An operator sets one retention policy per installation, shared by every organization, approval record and exported audit object on that installation. There is no per-organization override or Console/API setting. Changes require a restart and affect new writes only; they never shorten already retained versions. The minimum remains 2555 days and operators may extend it.

The customer deployment configuration can supply the existing environment variables alongside other operational settings:

deploy:
runtime_env:
OPK_ARTIFACT_OBJECT_LOCK_MODE: COMPLIANCE
OPK_ARTIFACT_RETENTION_DAYS: "4000"

For installations loading a runtime YAML file through OPK_INFRA_CONFIG_FILE, the equivalent section is:

artifact_retention:
mode: COMPLIANCE
days: 4000

Environment variables take precedence over the runtime file; omitted fields use COMPLIANCE and 2555 days. Explicit invalid values fail startup. S3 startup validation requires any present bucket default to be COMPLIANCE and at least the configured deployment duration; an absent default remains allowed.

Native Azure Blob and Google Cloud Storage accept COMPLIANCE only; configuring GOVERNANCE with either native driver fails startup. Their lock-enabled startup check is not a full conformance test or a default-retention check. See storage providers and validation.

Outcome deadline monitoring​

Availability. These settings exist only in worker builds that include outcome deadline monitoring. Check the release notes of the build you run.

Monitoring is off by default. When it is off the worker does nothing for it: no checks are scheduled, no coverage events are stored, and the request path is unchanged. Set these on the worker and restart it; they are read once at startup. There is no Console or API setting for them.

VariableDefaultRange and behavior
OPK_OUTCOME_DEADLINE_SECONDSUnset, which is offWhole seconds. 0, empty or unset turns monitoring off. Any value from 300 upward turns it on; it is the time after an allow by which an outcome report is expected. Values from 1 to 299, negative values and non-numeric values are rejected and the worker stops at startup instead of falling back to a default.
OPK_OUTCOME_MONITOR_FROMNoneAn RFC 3339 timestamp, for example 2026-01-01T00:00:00Z. Required when monitoring is on; the worker stops at startup if it is missing or invalid. Only allows issued at or after this time are monitored. Earlier allows are never scanned or backfilled. Ignored while monitoring is off.

Behavior when on:

  • Scope. The deadline applies to every organization on the deployment and to every allowed operation after the cutover, regardless of asset or transport. It is not configurable per organization, asset or principal.
  • Result. At the deadline, if no outcome has been reported, the worker stores an execution.outcome.missing audit event. An allow that declared outcome_reporting: none gets an execution.outcome.not_reportable event without waiting for the deadline. See Coverage events.
  • Fixed once registered. An operation's deadline is set when the worker first registers it. Changing OPK_OUTCOME_DEADLINE_SECONDS later affects only operations registered afterwards, and restarting does not move an existing deadline.
  • Dependencies. Deadline checks are delivered to the worker through the same outbox dispatch and queue as other worker events. Outbox dispatch must be enabled (see Outbox dispatch) and the worker must be running for checks to complete. Checks follow the outbox retry rules. The coverage event is stored when a check is processed, which can be later than the deadline, and a check that is dead-lettered after its last attempt produces no coverage event.
  • No effect on results. Monitoring does not change the result of a decision or of an outcome report, and a late report is still accepted.

Other operator settings​

VariablePurpose
OPK_PRODUCT_MODEDeployment mode. Default saas, which requires https webhooks.
OPK_BREAKGLASS_EXPIRY_SWEEP_SECONDSSeconds between the worker's checks that record breakglass.expired events (see Break-Glass). Default 60; an invalid or non-positive value falls back to 60. Set on the worker. It never changes when a grant stops working.
OPK_WEBHOOK_ALLOWED_CIDRSComma-separated CIDRs allowed as webhook destinations. Set on the API and the worker.
OPK_CORS_ALLOWED_ORIGINSBrowser origins allowed to call the API.
OPK_CONSOLE_BASE_URLAbsolute http or https Console URL for email links. No query string or fragment.
OPK_QUEUE_PROVIDERQueue backend: SQS, NATS, or RabbitMQ.
OPK_DATABASE_PROVIDER, OPK_OBJECT_STORAGE_*, OPK_SECRETS_PROVIDERSupported self-hosted dependencies. See the customer example configuration shipped with your deployment package.

Known documentation gaps​

  • Whether the license limits users.max, assets.max, policies.max, api_keys.max, and projects.max are enforced by the API is not confirmed, so they are not listed.
  • No application-level cap on total request body size is documented. Deployment gateways and proxies may impose their own.
  • Plan names and prices are not stated here.