smartcontractkit · ejacquier · Jul 23, 2026 · Jul 23, 2026 · Jul 27, 2026 · Jul 27, 2026
@@ -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 <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">app.chain.link/cre/request-access</a> 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
 

@@ -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 <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">Early Access</a> 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
 

@@ -24,7 +24,7 @@ Browser login stores **`~/.cre/cre.yaml`** (credentials) and **`~/.cre/context.y
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deploy access required">
-  API key authentication requires your account to have Early Access approval for deployment. To <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">request Early Access</a>, 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.
 </Aside>
 
 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.

@@ -53,7 +53,7 @@ Here are resources to help you go from simulation to production.
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deployment access required">
-  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank">app.chain.link/cre/request-access</a> 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.
 </Aside>
 
 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Required for the default onchain Workflow Registry. Not needed when using `deployment-registry: "private"`.

@@ -128,7 +128,7 @@ Here are resources to help you go from simulation to production.
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deployment access required">
-  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank">app.chain.link/cre/request-access</a> 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.
 </Aside>
 
 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Required for the default onchain Workflow Registry. Not needed when using `deployment-registry: "private"`.

@@ -18,8 +18,8 @@ import { Aside } from "@components"
 </Aside>
 
 {/* prettier-ignore */}
-<Aside type="note" title="Early Access required">
-  Workflow deployment is currently in Early Access. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">app.chain.link/cre/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+<Aside type="note" title="Deploy access required">
+  Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
 </Aside>
 
 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 */}
-<Aside type="caution" title="Early Access: Disclaimer">
-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 <a href="https://chain.link/terms" target="_blank" rel="noopener noreferrer">Terms of Service</a>, which provides important information and disclosures.
-</Aside>
-
 ### 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.

@@ -18,8 +18,8 @@ import { Aside } from "@components"
 </Aside>
 
 {/* prettier-ignore */}
-<Aside type="note" title="Early Access required">
-  Workflow deployment is currently in Early Access. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">app.chain.link/cre/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+<Aside type="note" title="Deploy access required">
+  Workflow deployment requires approval. Run `cre account access` to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
 </Aside>
 
 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 */}
-<Aside type="caution" title="Early Access: Disclaimer">
-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 <a href="https://chain.link/terms" target="_blank" rel="noopener noreferrer">Terms of Service</a>, which provides important information and disclosures.
-</Aside>
-
 ### 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.

@@ -11,8 +11,8 @@ metadata:
 import { Aside } from "@components"
 
 {/* prettier-ignore */}
-<Aside type="note" title="Early Access required">
-  Workflow deployment is currently in Early Access. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">app.chain.link/cre/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+<Aside type="note" title="Deploy access required">
+  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).
 

@@ -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 */}
-<Aside type="caution" title="Early Access: Disclaimer">
-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 <a href="https://chain.link/terms" target="_blank" rel="noopener noreferrer">Terms of Service</a>, which provides important information and disclosures.
+<Aside type="caution" title="Disclaimer">
+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 <a href="https://chain.link/terms" target="_blank" rel="noopener noreferrer">Terms of Service</a> which provides important information and disclosures. By using CRE, you expressly acknowledge and agree to accept these terms.
 </Aside>
 
-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 <a href="https://app.chain.link/cre/request-access" target="_blank">app.chain.link/cre/request-access</a>. 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 */}
+<Aside type="caution" title="Disclaimer">
+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 <a href="https://chain.link/terms" target="_blank" rel="noopener noreferrer">Terms of Service</a>, which provides important information and disclosures. By using this code, you acknowledge and agree to these terms.
+</Aside>