diff --git a/src/content/cre/account/deploy-access.mdx b/src/content/cre/account/deploy-access.mdx
index f241a4e176d..30da14d9336 100644
--- a/src/content/cre/account/deploy-access.mdx
+++ b/src/content/cre/account/deploy-access.mdx
@@ -3,17 +3,14 @@ section: cre
date: Last Modified
title: "Requesting Deploy Access"
metadata:
- description: "Learn how to check your deployment access status and request Early Access to deploy CRE workflows using the CLI or web UI."
+ description: "Learn how to check your deployment access status and request access to deploy CRE workflows using the CLI."
datePublished: "2026-02-26"
lastModified: "2026-02-26"
---
import { Aside } from "@components"
-Deploying workflows to a Chainlink DON requires Early Access approval. You can request access in two ways:
-
-- **From the CLI** — Run `cre account access` to check your status or submit a request directly from your terminal
-- **From the web** — Visit app.chain.link/cre/request-access to fill out the request form
+Deploying workflows to a Chainlink DON requires approval. Run `cre account access` to check your status or submit a request directly from your terminal.
## Check your access status
diff --git a/src/content/cre/account/index.mdx b/src/content/cre/account/index.mdx
index 5fd56eaf347..632b5878cba 100644
--- a/src/content/cre/account/index.mdx
+++ b/src/content/cre/account/index.mdx
@@ -13,7 +13,7 @@ import { Aside } from "@components"
Your CRE account is required to use the CRE CLI. You must be authenticated to run CLI commands, including simulating workflows, deploying workflows, and managing deployed workflows. You can authenticate using the browser-based `cre login` flow or an [API key](/cre/reference/cli/authentication#api-key-authentication) for CI/CD and headless environments(\*). This section covers everything you need to know about creating and managing your account.
-(\*) API key authentication requires your account to have Early Access approval.
+(\*) API key authentication requires your account to have deploy access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
## What you'll need
@@ -28,7 +28,7 @@ To use CRE, you need:
- **[Creating Your Account](/cre/account/creating-account)** - Step-by-step guide to creating a new CRE account through the CRE UI
- **[Logging in with the CLI](/cre/account/cli-login)** - Authenticate your CLI with your CRE account to run commands
- **[Managing Authentication](/cre/account/managing-auth)** - Check your login status, handle session expiration, and log out
-- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for Early Access
+- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for deploy access
## Security features
diff --git a/src/content/cre/account/managing-auth.mdx b/src/content/cre/account/managing-auth.mdx
index e97fa41f550..fcbc375af20 100644
--- a/src/content/cre/account/managing-auth.mdx
+++ b/src/content/cre/account/managing-auth.mdx
@@ -24,7 +24,7 @@ Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.y
{/* prettier-ignore */}
- API key authentication requires your account to have Early Access approval for deployment. To request Early Access , please share details about your project and use case—this helps us provide better support as you build with CRE.
+ API key authentication requires your account to have deploy access approval. Run `cre account access` to request access—this helps us provide better support as you build with CRE.
For CI/CD pipelines or headless environments where a browser is not available, you can authenticate using the `CRE_API_KEY` environment variable. When set, the CLI uses the API key automatically — no `cre login` required.
diff --git a/src/content/cre/getting-started/before-you-build-go.mdx b/src/content/cre/getting-started/before-you-build-go.mdx
index 2114f1009f7..95e876ce507 100644
--- a/src/content/cre/getting-started/before-you-build-go.mdx
+++ b/src/content/cre/getting-started/before-you-build-go.mdx
@@ -53,7 +53,7 @@ Here are resources to help you go from simulation to production.
{/* prettier-ignore */}
- Deploying requires Early Access approval. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
+ Deploying requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Required for the default onchain Workflow Registry. Not needed when using `deployment-registry: "private"`.
diff --git a/src/content/cre/getting-started/before-you-build-ts.mdx b/src/content/cre/getting-started/before-you-build-ts.mdx
index 8e8f5bc0268..326ecc48a74 100644
--- a/src/content/cre/getting-started/before-you-build-ts.mdx
+++ b/src/content/cre/getting-started/before-you-build-ts.mdx
@@ -128,7 +128,7 @@ Here are resources to help you go from simulation to production.
{/* prettier-ignore */}
- Deploying requires Early Access approval. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
+ Deploying requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Required for the default onchain Workflow Registry. Not needed when using `deployment-registry: "private"`.
diff --git a/src/content/cre/guides/operations/deploying-to-onchain-registry-go.mdx b/src/content/cre/guides/operations/deploying-to-onchain-registry-go.mdx
index c6c37701d1f..d4578325399 100644
--- a/src/content/cre/guides/operations/deploying-to-onchain-registry-go.mdx
+++ b/src/content/cre/guides/operations/deploying-to-onchain-registry-go.mdx
@@ -18,8 +18,8 @@ import { Aside } from "@components"
{/* prettier-ignore */}
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
The **public onchain registry** is the Workflow Registry contract on Ethereum Mainnet. Deploying to it records your workflow onchain — your linked wallet address becomes the workflow owner and every lifecycle operation (deploy, activate, pause, update, delete) submits a transaction to that contract.
@@ -30,7 +30,7 @@ For a lower-friction alternative that requires no wallet or gas for registry man
Before deploying to the onchain registry, ensure you have:
-- **Early Access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+- **Deploy access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
- **[Authenticated](/cre/reference/cli/authentication)**: Logged in via `cre login` or using an [API key](/cre/reference/cli/authentication#api-key-authentication) (`CRE_API_KEY`). To verify, run `cre whoami`.
- **[Linked your key](/cre/organization/linking-keys)**: Linked your EOA or multi-sig wallet to your CRE organization by running `cre account link-key`. See [Linking Wallet Keys](/cre/organization/linking-keys) for instructions.
- **A funded wallet**: The account you are deploying from must hold ETH on Ethereum Mainnet to pay gas for the registration transaction.
@@ -46,11 +46,6 @@ The `cre workflow deploy` command handles the entire end-to-end process:
1. **Uploads** the compiled binary and any associated configuration files to the CRE Storage Service.
1. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on Ethereum Mainnet. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet`. The transaction contains the workflow's name, owner, and artifact URLs.
-{/* prettier-ignore */}
-
-Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
-
-
### Step 1: Ensure your configuration is correct
Before deploying, ensure your `workflow.yaml` file is correctly configured. The `workflow-name` field is required under the `user-workflow` section for your target environment.
diff --git a/src/content/cre/guides/operations/deploying-to-onchain-registry-ts.mdx b/src/content/cre/guides/operations/deploying-to-onchain-registry-ts.mdx
index 6d366110a50..10e879acda5 100644
--- a/src/content/cre/guides/operations/deploying-to-onchain-registry-ts.mdx
+++ b/src/content/cre/guides/operations/deploying-to-onchain-registry-ts.mdx
@@ -18,8 +18,8 @@ import { Aside } from "@components"
{/* prettier-ignore */}
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
The **public onchain registry** is the Workflow Registry contract on Ethereum Mainnet. Deploying to it records your workflow onchain — your linked wallet address becomes the workflow owner and every lifecycle operation (deploy, activate, pause, update, delete) submits a transaction to that contract.
@@ -30,7 +30,7 @@ For a lower-friction alternative that requires no wallet or gas for registry man
Before deploying to the onchain registry, ensure you have:
-- **Early Access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+- **Deploy access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
- **[Authenticated](/cre/reference/cli/authentication)**: Logged in via `cre login` or using an [API key](/cre/reference/cli/authentication#api-key-authentication) (`CRE_API_KEY`). To verify, run `cre whoami`.
- **[Linked your key](/cre/organization/linking-keys)**: Linked your EOA or multi-sig wallet to your CRE organization by running `cre account link-key`. See [Linking Wallet Keys](/cre/organization/linking-keys) for instructions.
- **A funded wallet**: The account you are deploying from must hold ETH on Ethereum Mainnet to pay gas for the registration transaction.
@@ -46,11 +46,6 @@ The `cre workflow deploy` command handles the entire end-to-end process:
1. **Uploads** the compiled binary and any associated configuration files to the CRE Storage Service.
1. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on Ethereum Mainnet. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet`. The transaction contains the workflow's name, owner, and artifact URLs.
-{/* prettier-ignore */}
-
-Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
-
-
### Step 1: Ensure your configuration is correct
Before deploying, ensure your `workflow.yaml` file is correctly configured. The `workflow-name` field is required under the `user-workflow` section for your target environment.
diff --git a/src/content/cre/guides/operations/deploying-workflows.mdx b/src/content/cre/guides/operations/deploying-workflows.mdx
index 035a214214d..2ce11936c7e 100644
--- a/src/content/cre/guides/operations/deploying-workflows.mdx
+++ b/src/content/cre/guides/operations/deploying-workflows.mdx
@@ -11,8 +11,8 @@ metadata:
import { Aside } from "@components"
{/* prettier-ignore */}
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
**While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
diff --git a/src/content/cre/index.mdx b/src/content/cre/index.mdx
index 7f7432d5c44..b8ae2ad0cc4 100644
--- a/src/content/cre/index.mdx
+++ b/src/content/cre/index.mdx
@@ -36,20 +36,20 @@ You can start building and [simulating](/cre/guides/operations/simulating-workfl
Simulation compiles your workflows into [WebAssembly (WASM)](https://webassembly.org/) and runs them on your machine—but makes **real calls** to live APIs and public EVM blockchains. This gives you confidence your workflow will work as expected when deployed to a DON.
-### Deploy your workflows (Early Access)
+### Deploy your workflows
{/* prettier-ignore */}
-
-Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
+
+Chainlink CRE is provided on an "as is" basis without any representations, warranties, covenants, or conditions of any kind. Use at your own risk. Users remain fully responsible for deployments and that the operation and performance of workflows matches expectations. Please review the Chainlink Foundation Terms of Service which provides important information and disclosures. By using CRE, you expressly acknowledge and agree to accept these terms.
-Early Access to workflow deployment includes:
+Deploying workflows requires approval. Workflow deployment includes:
- **Deploy and run workflows** on a Chainlink DON
- **Workflow lifecycle management**: Deploy, activate, pause, update, and delete workflows through the CLI
- **Monitoring and debugging**: Access detailed logs, events, and performance metrics in the CRE UI
-To request Early Access, run `cre account access` from the CLI or visit app.chain.link/cre/request-access . See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+To request deploy access, run `cre account access` from the CLI. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
## How CRE runs your workflows
@@ -156,3 +156,8 @@ Jump to what you need:
- **[Workflow Guides](/cre/guides/workflow/using-triggers/overview)** - Learn how to use triggers, make API calls, and interact with blockchains
- **[Workflow Operations](/cre/guides/operations/simulating-workflows)** - Simulate, deploy, and manage your workflows
- **[SDK Reference](/cre/reference/sdk)** - Detailed API documentation for Go and TypeScript SDKs
+
+{/* prettier-ignore */}
+
+This code represents an example of using a Chainlink product or service. It is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may omit checks or error handling. Each party intending to use this reference implementation must perform its own audits, security and code review, and testing before any production deployment and ensure the operation and performance of such code matches expectations. Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for outcomes due to errors in this example or how it is deployed or operated. Use of the Chainlink Network is subject to the Chainlink Foundation Terms of Service , which provides important information and disclosures. By using this code, you acknowledge and agree to these terms.
+
diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt
index 32ee8215927..36a00433803 100644
--- a/src/content/cre/llms-full-go.txt
+++ b/src/content/cre/llms-full-go.txt
@@ -26,20 +26,20 @@ You can start building and [simulating](/cre/guides/operations/simulating-workfl
Simulation compiles your workflows into [WebAssembly (WASM)](https://webassembly.org/) and runs them on your machine—but makes **real calls** to live APIs and public EVM blockchains. This gives you confidence your workflow will work as expected when deployed to a DON.
-### Deploy your workflows (Early Access)
+### Deploy your workflows
-
- Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
+
+ Chainlink CRE is provided on an "as is" basis without any representations, warranties, covenants, or conditions of any kind. Use at your own risk. Users remain fully responsible for deployments and that the operation and performance of workflows matches expectations. Please review the Chainlink Foundation Terms of Service which provides important information and disclosures. By using CRE, you expressly acknowledge and agree to accept these terms.
-Early Access to workflow deployment includes:
+Deploying workflows requires approval. Workflow deployment includes:
- **Deploy and run workflows** on a Chainlink DON
- **Workflow lifecycle management**: Deploy, activate, pause, update, and delete workflows through the CLI
- **Monitoring and debugging**: Access detailed logs, events, and performance metrics in the CRE UI
-To request Early Access, run `cre account access` from the CLI or visit app.chain.link/cre/request-access . See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+To request deploy access, run `cre account access` from the CLI. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
## How CRE runs your workflows
@@ -146,6 +146,11 @@ Jump to what you need:
- **[Workflow Operations](/cre/guides/operations/simulating-workflows)** - Simulate, deploy, and manage your workflows
- **[SDK Reference](/cre/reference/sdk)** - Detailed API documentation for Go and TypeScript SDKs
+
+
+ This code represents an example of using a Chainlink product or service. It is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may omit checks or error handling. Each party intending to use this reference implementation must perform its own audits, security and code review, and testing before any production deployment and ensure the operation and performance of such code matches expectations. Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for outcomes due to errors in this example or how it is deployed or operated. Use of the Chainlink Network is subject to the Chainlink Foundation Terms of Service , which provides important information and disclosures. By using this code, you acknowledge and agree to these terms.
+
+
---
# Key Terms and Concepts
@@ -5943,8 +5948,8 @@ If your workflow requires higher limits than the defaults, you can request a lim
Source: https://docs.chain.link/cre/guides/operations/deploying-workflows
Last Updated: 2026-05-12
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
**While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
@@ -6953,7 +6958,7 @@ Last Updated: 2026-02-12
Your CRE account is required to use the CRE CLI. You must be authenticated to run CLI commands, including simulating workflows, deploying workflows, and managing deployed workflows. You can authenticate using the browser-based `cre login` flow or an [API key](/cre/reference/cli/authentication#api-key-authentication) for CI/CD and headless environments(\*). This section covers everything you need to know about creating and managing your account.
-(\*) API key authentication requires your account to have Early Access approval.
+(\*) API key authentication requires your account to have deploy access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
## What you'll need
@@ -6968,7 +6973,7 @@ To use CRE, you need:
- **[Creating Your Account](/cre/account/creating-account)** - Step-by-step guide to creating a new CRE account through the CRE UI
- **[Logging in with the CLI](/cre/account/cli-login)** - Authenticate your CLI with your CRE account to run commands
- **[Managing Authentication](/cre/account/managing-auth)** - Check your login status, handle session expiration, and log out
-- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for Early Access
+- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for deploy access
## Security features
@@ -7203,7 +7208,7 @@ Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.y
- API key authentication requires your account to have Early Access approval for deployment. To request Early Access , please share details about your project and use case—this helps us provide better support as you build with CRE.
+ API key authentication requires your account to have deploy access approval. Run `cre account access` to request access—this helps us provide better support as you build with CRE.
For CI/CD pipelines or headless environments where a browser is not available, you can authenticate using the `CRE_API_KEY` environment variable. When set, the CLI uses the API key automatically — no `cre login` required.
@@ -7265,10 +7270,7 @@ After logging out, you'll need to run `cre login` again to authenticate future C
Source: https://docs.chain.link/cre/account/deploy-access
Last Updated: 2026-02-26
-Deploying workflows to a Chainlink DON requires Early Access approval. You can request access in two ways:
-
-- **From the CLI** — Run `cre account access` to check your status or submit a request directly from your terminal
-- **From the web** — Visit app.chain.link/cre/request-access to fill out the request form
+Deploying workflows to a Chainlink DON requires approval. Run `cre account access` to check your status or submit a request directly from your terminal.
## Check your access status
@@ -8391,7 +8393,7 @@ Initialize projects and generate contract bindings (Go only).
Manage your linked public key addresses and deployment access.
-- **`cre account access`** — Check deployment access status or submit an Early Access request
+- **`cre account access`** — Check deployment access status or submit a deploy access request
- **`cre account link-key`** — Link a public key address to your account
- **`cre account list-key`** — List workflow owners linked to your organization
- **`cre account unlink-key`** — Unlink a public key address from your account
@@ -8560,7 +8562,7 @@ cre whoami
- API key authentication requires your account to have Early Access approval for deployment. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+ API key authentication requires your account to have deploy access approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
For CI/CD pipelines, automated scripts, or any environment where a browser is not available, you can authenticate using an API key. When the `CRE_API_KEY` environment variable is set, the CLI uses it automatically — no `cre login` required.
@@ -8630,7 +8632,7 @@ PRODUCTION:
| `cre login` | Local development | Opens a browser for interactive login with 2FA |
| `CRE_API_KEY` | CI/CD, scripts, headless environments | Set the environment variable — no browser needed(\*) |
-(\*) API key authentication requires your account to have Early Access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
+(\*) API key authentication requires your account to have deploy access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
## Learn more
@@ -8660,9 +8662,9 @@ The `cre account` commands manage linked public key addresses for public onchain
in with the CLI](/cre/account/cli-login) for further details.
-Checks your organization's deployment access status and lets you submit a request for Early Access directly from the CLI.
+Checks your organization's deployment access status and lets you submit a request for deploy access directly from the CLI.
-For a full walkthrough including the interactive flow and web UI option, see [Requesting Deploy Access](/cre/account/deploy-access).
+For a full walkthrough of the interactive flow, see [Requesting Deploy Access](/cre/account/deploy-access).
**Usage:**
@@ -9064,7 +9066,7 @@ The chain list is tenant-specific and may vary between organizations. Run the co
- Deploying workflows requires Early Access approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+ Deploying workflows requires approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
**While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
@@ -10649,7 +10651,7 @@ Here are resources to help you go from simulation to production.
- Deploying requires Early Access approval. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
+ Deploying requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Required for the default onchain Workflow Registry. Not needed when using `deployment-registry: "private"`.
@@ -12103,8 +12105,8 @@ Last Updated: 2026-05-12
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
The **public onchain registry** is the Workflow Registry contract on Ethereum Mainnet. Deploying to it records your workflow onchain — your linked wallet address becomes the workflow owner and every lifecycle operation (deploy, activate, pause, update, delete) submits a transaction to that contract.
@@ -12115,7 +12117,7 @@ For a lower-friction alternative that requires no wallet or gas for registry man
Before deploying to the onchain registry, ensure you have:
-- **Early Access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+- **Deploy access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
- **[Authenticated](/cre/reference/cli/authentication)**: Logged in via `cre login` or using an [API key](/cre/reference/cli/authentication#api-key-authentication) (`CRE_API_KEY`). To verify, run `cre whoami`.
- **[Linked your key](/cre/organization/linking-keys)**: Linked your EOA or multi-sig wallet to your CRE organization by running `cre account link-key`. See [Linking Wallet Keys](/cre/organization/linking-keys) for instructions.
- **A funded wallet**: The account you are deploying from must hold ETH on Ethereum Mainnet to pay gas for the registration transaction.
@@ -12131,11 +12133,6 @@ The `cre workflow deploy` command handles the entire end-to-end process:
2. **Uploads** the compiled binary and any associated configuration files to the CRE Storage Service.
3. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on Ethereum Mainnet. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet`. The transaction contains the workflow's name, owner, and artifact URLs.
-
-
- Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
-
-
### Step 1: Ensure your configuration is correct
Before deploying, ensure your `workflow.yaml` file is correctly configured. The `workflow-name` field is required under the `user-workflow` section for your target environment.
@@ -19545,7 +19542,7 @@ See the [Monitoring & Debugging guide](/cre/guides/operations/monitoring-workflo
## Pricing
-CRE is currently in Early Access. For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
+For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
## Get started
diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt
index a7eaaa2ce15..2b3e54fa77e 100644
--- a/src/content/cre/llms-full-ts.txt
+++ b/src/content/cre/llms-full-ts.txt
@@ -26,20 +26,20 @@ You can start building and [simulating](/cre/guides/operations/simulating-workfl
Simulation compiles your workflows into [WebAssembly (WASM)](https://webassembly.org/) and runs them on your machine—but makes **real calls** to live APIs and public EVM blockchains. This gives you confidence your workflow will work as expected when deployed to a DON.
-### Deploy your workflows (Early Access)
+### Deploy your workflows
-
- Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
+
+ Chainlink CRE is provided on an "as is" basis without any representations, warranties, covenants, or conditions of any kind. Use at your own risk. Users remain fully responsible for deployments and that the operation and performance of workflows matches expectations. Please review the Chainlink Foundation Terms of Service which provides important information and disclosures. By using CRE, you expressly acknowledge and agree to accept these terms.
-Early Access to workflow deployment includes:
+Deploying workflows requires approval. Workflow deployment includes:
- **Deploy and run workflows** on a Chainlink DON
- **Workflow lifecycle management**: Deploy, activate, pause, update, and delete workflows through the CLI
- **Monitoring and debugging**: Access detailed logs, events, and performance metrics in the CRE UI
-To request Early Access, run `cre account access` from the CLI or visit app.chain.link/cre/request-access . See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+To request deploy access, run `cre account access` from the CLI. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
## How CRE runs your workflows
@@ -146,6 +146,11 @@ Jump to what you need:
- **[Workflow Operations](/cre/guides/operations/simulating-workflows)** - Simulate, deploy, and manage your workflows
- **[SDK Reference](/cre/reference/sdk)** - Detailed API documentation for Go and TypeScript SDKs
+
+
+ This code represents an example of using a Chainlink product or service. It is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, has not been audited, and may omit checks or error handling. Each party intending to use this reference implementation must perform its own audits, security and code review, and testing before any production deployment and ensure the operation and performance of such code matches expectations. Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for outcomes due to errors in this example or how it is deployed or operated. Use of the Chainlink Network is subject to the Chainlink Foundation Terms of Service , which provides important information and disclosures. By using this code, you acknowledge and agree to these terms.
+
+
---
# Key Terms and Concepts
@@ -5252,8 +5257,8 @@ If your workflow requires higher limits than the defaults, you can request a lim
Source: https://docs.chain.link/cre/guides/operations/deploying-workflows
Last Updated: 2026-05-12
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
**While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
@@ -6715,7 +6720,7 @@ Last Updated: 2026-02-12
Your CRE account is required to use the CRE CLI. You must be authenticated to run CLI commands, including simulating workflows, deploying workflows, and managing deployed workflows. You can authenticate using the browser-based `cre login` flow or an [API key](/cre/reference/cli/authentication#api-key-authentication) for CI/CD and headless environments(\*). This section covers everything you need to know about creating and managing your account.
-(\*) API key authentication requires your account to have Early Access approval.
+(\*) API key authentication requires your account to have deploy access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
## What you'll need
@@ -6730,7 +6735,7 @@ To use CRE, you need:
- **[Creating Your Account](/cre/account/creating-account)** - Step-by-step guide to creating a new CRE account through the CRE UI
- **[Logging in with the CLI](/cre/account/cli-login)** - Authenticate your CLI with your CRE account to run commands
- **[Managing Authentication](/cre/account/managing-auth)** - Check your login status, handle session expiration, and log out
-- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for Early Access
+- **[Requesting Deploy Access](/cre/account/deploy-access)** - Check your deployment access status or submit a request for deploy access
## Security features
@@ -6965,7 +6970,7 @@ Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.y
- API key authentication requires your account to have Early Access approval for deployment. To request Early Access , please share details about your project and use case—this helps us provide better support as you build with CRE.
+ API key authentication requires your account to have deploy access approval. Run `cre account access` to request access—this helps us provide better support as you build with CRE.
For CI/CD pipelines or headless environments where a browser is not available, you can authenticate using the `CRE_API_KEY` environment variable. When set, the CLI uses the API key automatically — no `cre login` required.
@@ -7027,10 +7032,7 @@ After logging out, you'll need to run `cre login` again to authenticate future C
Source: https://docs.chain.link/cre/account/deploy-access
Last Updated: 2026-02-26
-Deploying workflows to a Chainlink DON requires Early Access approval. You can request access in two ways:
-
-- **From the CLI** — Run `cre account access` to check your status or submit a request directly from your terminal
-- **From the web** — Visit app.chain.link/cre/request-access to fill out the request form
+Deploying workflows to a Chainlink DON requires approval. Run `cre account access` to check your status or submit a request directly from your terminal.
## Check your access status
@@ -8214,7 +8216,7 @@ Initialize projects and generate contract bindings (Go only).
Manage your linked public key addresses and deployment access.
-- **`cre account access`** — Check deployment access status or submit an Early Access request
+- **`cre account access`** — Check deployment access status or submit a deploy access request
- **`cre account link-key`** — Link a public key address to your account
- **`cre account list-key`** — List workflow owners linked to your organization
- **`cre account unlink-key`** — Unlink a public key address from your account
@@ -8383,7 +8385,7 @@ cre whoami
- API key authentication requires your account to have Early Access approval for deployment. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+ API key authentication requires your account to have deploy access approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
For CI/CD pipelines, automated scripts, or any environment where a browser is not available, you can authenticate using an API key. When the `CRE_API_KEY` environment variable is set, the CLI uses it automatically — no `cre login` required.
@@ -8453,7 +8455,7 @@ PRODUCTION:
| `cre login` | Local development | Opens a browser for interactive login with 2FA |
| `CRE_API_KEY` | CI/CD, scripts, headless environments | Set the environment variable — no browser needed(\*) |
-(\*) API key authentication requires your account to have Early Access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
+(\*) API key authentication requires your account to have deploy access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
## Learn more
@@ -8483,9 +8485,9 @@ The `cre account` commands manage linked public key addresses for public onchain
in with the CLI](/cre/account/cli-login) for further details.
-Checks your organization's deployment access status and lets you submit a request for Early Access directly from the CLI.
+Checks your organization's deployment access status and lets you submit a request for deploy access directly from the CLI.
-For a full walkthrough including the interactive flow and web UI option, see [Requesting Deploy Access](/cre/account/deploy-access).
+For a full walkthrough of the interactive flow, see [Requesting Deploy Access](/cre/account/deploy-access).
**Usage:**
@@ -8887,7 +8889,7 @@ The chain list is tenant-specific and may vary between organizations. Run the co
- Deploying workflows requires Early Access approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+ Deploying workflows requires approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
**While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
@@ -10773,7 +10775,7 @@ Here are resources to help you go from simulation to production.
- Deploying requires Early Access approval. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
+ Deploying requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Required for the default onchain Workflow Registry. Not needed when using `deployment-registry: "private"`.
@@ -12283,8 +12285,8 @@ Last Updated: 2026-05-12
-
- Workflow deployment is currently in Early Access. Run `cre account access` or visit app.chain.link/cre/request-access to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+
+ Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
The **public onchain registry** is the Workflow Registry contract on Ethereum Mainnet. Deploying to it records your workflow onchain — your linked wallet address becomes the workflow owner and every lifecycle operation (deploy, activate, pause, update, delete) submits a transaction to that contract.
@@ -12295,7 +12297,7 @@ For a lower-friction alternative that requires no wallet or gas for registry man
Before deploying to the onchain registry, ensure you have:
-- **Early Access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+- **Deploy access approval**: Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
- **[Authenticated](/cre/reference/cli/authentication)**: Logged in via `cre login` or using an [API key](/cre/reference/cli/authentication#api-key-authentication) (`CRE_API_KEY`). To verify, run `cre whoami`.
- **[Linked your key](/cre/organization/linking-keys)**: Linked your EOA or multi-sig wallet to your CRE organization by running `cre account link-key`. See [Linking Wallet Keys](/cre/organization/linking-keys) for instructions.
- **A funded wallet**: The account you are deploying from must hold ETH on Ethereum Mainnet to pay gas for the registration transaction.
@@ -12311,11 +12313,6 @@ The `cre workflow deploy` command handles the entire end-to-end process:
2. **Uploads** the compiled binary and any associated configuration files to the CRE Storage Service.
3. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on Ethereum Mainnet. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet`. The transaction contains the workflow's name, owner, and artifact URLs.
-
-
- Chainlink Runtime Environment (CRE) deployment is in the "Early Access" stage of development, which means that CRE currently has functionality which is under development and may be changed in later versions. By using CRE, you expressly acknowledge and agree to accept the Chainlink Terms of Service , which provides important information and disclosures.
-
-
### Step 1: Ensure your configuration is correct
Before deploying, ensure your `workflow.yaml` file is correctly configured. The `workflow-name` field is required under the `user-workflow` section for your target environment.
@@ -19515,7 +19512,7 @@ See the [Monitoring & Debugging guide](/cre/guides/operations/monitoring-workflo
## Pricing
-CRE is currently in Early Access. For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
+For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
## Get started
diff --git a/src/content/cre/reference/cli/account.mdx b/src/content/cre/reference/cli/account.mdx
index 726da746610..84df149390b 100644
--- a/src/content/cre/reference/cli/account.mdx
+++ b/src/content/cre/reference/cli/account.mdx
@@ -25,9 +25,9 @@ The `cre account` commands manage linked public key addresses for public onchain
in with the CLI](/cre/account/cli-login) for further details.
-Checks your organization's deployment access status and lets you submit a request for Early Access directly from the CLI.
+Checks your organization's deployment access status and lets you submit a request for deploy access directly from the CLI.
-For a full walkthrough including the interactive flow and web UI option, see [Requesting Deploy Access](/cre/account/deploy-access).
+For a full walkthrough of the interactive flow, see [Requesting Deploy Access](/cre/account/deploy-access).
**Usage:**
diff --git a/src/content/cre/reference/cli/authentication.mdx b/src/content/cre/reference/cli/authentication.mdx
index 2c63999a62f..a35c9fd64c3 100644
--- a/src/content/cre/reference/cli/authentication.mdx
+++ b/src/content/cre/reference/cli/authentication.mdx
@@ -68,7 +68,7 @@ cre whoami
{/* prettier-ignore */}
- API key authentication requires your account to have Early Access approval for deployment. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+ API key authentication requires your account to have deploy access approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
For CI/CD pipelines, automated scripts, or any environment where a browser is not available, you can authenticate using an API key. When the `CRE_API_KEY` environment variable is set, the CLI uses it automatically — no `cre login` required.
@@ -138,7 +138,7 @@ PRODUCTION:
| `cre login` | Local development | Opens a browser for interactive login with 2FA |
| `CRE_API_KEY` | CI/CD, scripts, headless environments | Set the environment variable — no browser needed(\*) |
-(\*) API key authentication requires your account to have Early Access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
+(\*) API key authentication requires your account to have deploy access approval. See [Requesting Deploy Access](/cre/account/deploy-access).
## Learn more
diff --git a/src/content/cre/reference/cli/index.mdx b/src/content/cre/reference/cli/index.mdx
index 359f63d10f4..01816ad0112 100644
--- a/src/content/cre/reference/cli/index.mdx
+++ b/src/content/cre/reference/cli/index.mdx
@@ -72,7 +72,7 @@ Initialize projects and generate contract bindings (Go only).
Manage your linked public key addresses and deployment access.
-- **`cre account access`** — Check deployment access status or submit an Early Access request
+- **`cre account access`** — Check deployment access status or submit a deploy access request
- **`cre account link-key`** — Link a public key address to your account
- **`cre account list-key`** — List workflow owners linked to your organization
- **`cre account unlink-key`** — Unlink a public key address from your account
diff --git a/src/content/cre/reference/cli/workflow.mdx b/src/content/cre/reference/cli/workflow.mdx
index e1bc514f7db..ecdf270b166 100644
--- a/src/content/cre/reference/cli/workflow.mdx
+++ b/src/content/cre/reference/cli/workflow.mdx
@@ -219,7 +219,7 @@ The chain list is tenant-specific and may vary between organizations. Run the co
{/* prettier-ignore */}
- Deploying workflows requires Early Access approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
+ Deploying workflows requires approval. Run `cre account access` to check your status or submit a request. See [Requesting Deploy Access](/cre/account/deploy-access).
**While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
diff --git a/src/content/cre/reference/gelato-migration-go.mdx b/src/content/cre/reference/gelato-migration-go.mdx
index b90d54dcbd1..883b4c6ffce 100644
--- a/src/content/cre/reference/gelato-migration-go.mdx
+++ b/src/content/cre/reference/gelato-migration-go.mdx
@@ -176,7 +176,7 @@ See the [Monitoring & Debugging guide](/cre/guides/operations/monitoring-workflo
## Pricing
-CRE is currently in Early Access. For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
+For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
## Get started
diff --git a/src/content/cre/reference/gelato-migration-ts.mdx b/src/content/cre/reference/gelato-migration-ts.mdx
index 92a6fd43633..6057d6af021 100644
--- a/src/content/cre/reference/gelato-migration-ts.mdx
+++ b/src/content/cre/reference/gelato-migration-ts.mdx
@@ -189,7 +189,7 @@ See the [Monitoring & Debugging guide](/cre/guides/operations/monitoring-workflo
## Pricing
-CRE is currently in Early Access. For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
+For pricing details, reach out via the in-app support on the CRE platform at app.chain.link/cre/discover .
## Get started