# Service Quotas Source: https://docs.chain.link/cre/service-quotas Last Updated: 2026-05-26 > For the complete documentation index, see [llms.txt](/llms.txt). This page documents the service quotas for Chainlink Runtime Environment (CRE) workflows. > **NOTE: Subject to change** > > The quotas documented on this page are subject to change. Check back regularly for updates. ## Per-organization quotas These quotas apply at the organization level. ### Organization membership | Quota | Description | Value | | ------------- | ------------------------------------------------ | ----- | | Maximum users | Maximum number of user accounts per organization | 40 | This limit can be increased. [Contact us](/cre/support-feedback) to request a higher user cap for your organization. ### Registry quotas | Registry | Quota | Value | | --------------------------------------------------------------------------- | ------------------------------------ | ----- | | Private registry (`deployment-registry: "private"`) | Maximum workflows per organization | 3 | | Public onchain registry (`deployment-registry: "onchain:ethereum-mainnet"`) | Maximum linked keys per organization | 1 | | Public onchain registry (`deployment-registry: "onchain:ethereum-mainnet"`) | Maximum workflows per linked key | 3 | > **NOTE: Subject to change** > > Registry quotas are being actively tuned ahead of general availability. Values may increase. Run `cre registry list` to confirm your organization's access. ## Per-owner quotas These quotas apply to each workflow owner (user account) within an organization. | Quota Key | Description | Value | | --------- | ----------------------------------------------------------- | ----- | | | Maximum number of workflows that can execute simultaneously | 5 | | | Maximum number of secrets that can be stored per owner | 100 | > **NOTE: Quota enforcement** > > When workflow executions exceed the quotas defined above, they are queued and automatically retried for up to 10 > minutes. If an execution cannot be completed within this 10-minute window, it will be dropped and will not run. ## Per-workflow quotas These quotas apply to each individual workflow. ### Workflow deployment quotas | Quota Key | Description | Value | | --------- | ------------------------------------------ | ------ | | | Maximum size of the compiled WASM binary | 100 MB | | | Maximum size of the compressed WASM binary | 20 MB | | | Maximum size of the workflow configuration | 50 KB | ### Trigger quotas | Quota Key | Description | Value | | --------- | ---------------------------------------------------------------------- | ----- | | | Maximum number of triggers that can be registered to a single workflow | 10 | ### Execution quotas | Quota Key | Description | Value | | --------- | --------------------------------------------------------------- | --------- | | | Maximum number of concurrent executions for a specific workflow | 10 | | | Maximum total execution time for a single workflow run | 5 minutes | | | Maximum memory allocated to a workflow | 100 MB | | | Maximum size of the data a workflow can return | 100 KB | ### General capability quotas | Quota Key | Description | Value | | --------- | ------------------------------------------------------------------------------------------------------ | --------- | | | Maximum concurrent capability calls (HTTP, EVM read/write, secrets) that can execute within a workflow | 30 | | | Maximum time a single capability call can take to complete | 3 minutes | ### Secrets quotas | Quota Key | Description | Value | | --------- | -------------------------------------------------------------------------------------------------------------------------------- | ----- | | | Maximum total size of secrets accessible to a workflow | 27 KB | | | Maximum number of secrets that can be fetched concurrently. [Learn how to fetch multiple secrets](/cre/guides/workflow/secrets). | 5 | | | Maximum number of secrets fetch calls per workflow execution | 5 | | | Maximum size of a single encrypted secret value | 2 KB | ### Consensus quotas | Quota Key | Description | Value | | --------- | ---------------------------------------------------------------- | ----- | | | Maximum size of data that can be passed to consensus aggregation | 25 KB | | | Maximum number of consensus calls per workflow execution | 20 | ### Logging quotas | Quota Key | Description | Value | | --------- | --------------------------------------------------- | ----- | | | Maximum size of a single log line | 1 KB | | | Maximum number of log events per workflow execution | 1,000 | ## Trigger-specific quotas ### Cron trigger | Quota Key | Description | Value | | --------- | ------------------------------------------- | ---------- | | | Minimum interval between cron trigger fires | 30 seconds | > **NOTE: Minimum cron schedule** > > While the rate quota allows firing once per 30 seconds, you should consider the [Concurrent Workflow > Instances](#execution-quotas) quota when setting your cron schedule to avoid overlapping executions. ### HTTP trigger | Quota Key | Description | Value | | --------- | ---------------------------------------------- | -------------------------------- | | | Maximum rate at which an HTTP trigger can fire | Rate: 1 per 60 seconds Burst: 1 | ### EVM log trigger | Quota Key | Description | Value | | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | | Maximum rate at which log events can be processed | Rate: 10 per 6 seconds Burst: 10 | | | Maximum number of contract addresses that can be monitored | 5 | | | Maximum number of topic values that can be specified within a single topic position (Topics\[0], Topics\[1], Topics\[2], or Topics\[3]). [Learn about topic filtering](/cre/guides/workflow/using-triggers/evm-log-trigger). | 10 | | | Maximum size of a single log event | 5 KB | ## Capability-specific quotas ### EVM write capability | Quota Key | Description | Value | | --------- | --------------------------------------------------------- | --------- | | | Maximum number of destination chains for write operations | 10 | | | Maximum size of a report payload | 5 KB | | | Gas quota per EVM transaction | 5,000,000 | ### EVM read capability | Quota Key | Description | Value | | --------- | ---------------------------------------------------------------- | ----- | | | Maximum number of EVM read calls per workflow execution | 15 | | | Maximum number of blocks that can be queried for historical logs | 100 | | | Maximum size of an EVM read request payload | 5 KB | ### HTTP capability | Quota Key | Description | Value | | --------- | ------------------------------------------------------ | ---------- | | | Maximum number of HTTP requests per workflow execution | 5 | | | Maximum size of an HTTP response | 100 KB | | | Maximum time to establish an HTTP connection | 10 seconds | | | Maximum size of an HTTP request payload | 10 KB | | | Maximum time HTTP responses can be cached | 10 minutes | ### Confidential HTTP capability | Quota Key | Description | Value | | --------- | ------------------------------------------------------------------- | ---------- | | | Maximum number of confidential HTTP requests per workflow execution | 5 | | | Maximum size of a confidential HTTP request payload | 10 KB | | | Maximum size of a confidential HTTP response | 100 KB | | | Maximum time for a confidential HTTP request to complete | 10 seconds | ## Quota increases [Contact us](/cre/support-feedback) to discuss quota increases. > **TIP: Test limits locally before deploying** > > You can enforce these production quotas during local simulation using the `--limits` flag. Export, customize, and > validate limits before deploying. See [Testing Production Limits](/cre/guides/operations/understanding-limits) for > details.