> ## Documentation Index > Fetch the complete documentation index at: https://docs.blnkfinance.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploy the Blnk Production License > Deploy the Cloud Dashboard with a Production License, then connect your self-hosted Core. export const RelatedTopics = ({title = "Related topics", items = []}) => { if (!items.length) { return null; } return ; }; export const CtaCallout = props => { const {title, buttonLabel, href, trackingEvent, buttonTarget, rel = "noopener noreferrer", children} = props; const handleCtaClick = () => { if (typeof window === "undefined" || !trackingEvent) { return; } try { window.dispatchEvent(new CustomEvent("blnk:docs-cta", { detail: { name: trackingEvent, href } })); } catch {} try { window.posthog?.capture?.(trackingEvent, { href }); } catch {} const gaPayload = { cta_href: href }; try { window.gtag?.("event", trackingEvent, gaPayload); } catch {} try { window.dataLayer = window.dataLayer || []; window.dataLayer.push({ event: trackingEvent, ...gaPayload }); } catch {} }; const isExternal = typeof href === "string" && (/^https?:\/\//i).test(href); const target = buttonTarget ?? (isExternal ? "_blank" : undefined); const linkRel = isExternal ? rel : undefined; return
; }; The Production License lets you run the Cloud Dashboard in your own infrastructure. We recommend deploying [Blnk Core](/home/install) separately, then running the dashboard and [connecting your Core](/cloud/instances/create) to it. Built for teams that need stronger security controls, data residency support, custom tooling, or a closer operational partnership with Blnk. Get a Production License tailored to your deployment needs. *** ## Dashboard deployment guide Use this guide to deploy the Cloud Dashboard on AWS, GCP, Azure, or any cloud provider. When you purchase a Production License, you'll receive an email with your license key. Use the base64 value from the email as `ENTERPRISE_LICENSE_B64` in step 4. Create a managed Postgres instance in your environment. Use a recent supported Postgres version and enable TLS for production. Create one database for the Cloud Dashboard: ```sql theme={"system"} CREATE DATABASE "blnk-cloud"; ``` Save the connection URL for the instance. You will use it as `ENTERPRISE_POSTGRES_URL` in the next step. Pull the enterprise image from GitHub Container Registry: ```bash Docker theme={"system"} docker pull ghcr.io/blnkfinance/blnk-enterprise:0.1.23 ``` Using a custom image? Use the image name provided in your license email or onboarding instructions. Create an environment file, such as `.env` or `enterprise.env`. Add the following variables and replace the placeholder values with your Postgres URL and license key. ```dotenv .env wrap theme={"system"} HOSTNAME=127.0.0.1 ENTERPRISE_POSTGRES_URL=postgres://user:password@host:5432/postgres?sslmode=require ENTERPRISE_LICENSE_B64=your_base64_license_string ENTERPRISE_SKIP_CORE=true ``` | Environment variable | Description | | :------------------------ | :----------------------------------------------------------------------------------------------------------- | | `HOSTNAME` | Use `127.0.0.1` so health checks and internal services communicate through the container loopback interface. | | `ENTERPRISE_POSTGRES_URL` | Connection string for the Postgres instance that hosts the `blnk-cloud` database. | | `ENTERPRISE_LICENSE_B64` | Base64-encoded license key from step 1. | Add these variables to the same environment file. They configure how users access the Cloud Dashboard. ```dotenv .env wrap theme={"system"} ENTERPRISE_PUBLIC_PORT=8080 ENTERPRISE_PUBLIC_URL=https://ledger.yourdomain.com ``` | Environment variable | Description | | :----------------------- | :---------------------------------------------------------------------------------------------------------------------------------------- | | `ENTERPRISE_PUBLIC_PORT` | Port exposed by the enterprise launcher for the Cloud Dashboard. | | `ENTERPRISE_PUBLIC_URL` | Public URL where users access the Cloud Dashboard, including `https://`. Use this value when configuring `CORS_ORIGINS` in the next step. | Plane powers the Cloud Dashboard and stores its data in the `blnk-cloud` database. Add these variables to the same environment file you created in the previous step. ```dotenv .env wrap theme={"system"} CORS_ORIGINS=http://localhost:8080,http://localhost:3001,https://ledger.yourdomain.com BLNK_ENCRYPTION_KEY=0123456789abcdef0123456789abcdef JWT_SECRET=your_long_random_secret_here ``` | Environment variable | Description | | :-------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `CORS_ORIGINS` | Comma-separated list of browser origins allowed to access the Plane API. Do not include spaces. Make sure `ENTERPRISE_PUBLIC_URL` is included. | | `BLNK_ENCRYPTION_KEY` | A unique 32-character key used to encrypt sensitive data, such as instance connection keys. Do not change this value after deployment, or previously encrypted data may become unreadable. | | `JWT_SECRET` | A strong random secret used to sign and verify authentication tokens. | Start the dashboard with the image you pulled earlier. Map the host port to `ENTERPRISE_PUBLIC_PORT`, e.g. `8080` if you used the value from the public app config step. ```bash Docker theme={"system"} docker run -d \ --name blnk-enterprise \ -p 8080:8080 \ ghcr.io/blnkfinance/blnk-enterprise:0.1.23 ``` Confirm that your deployment is live: ```bash Check deployment status theme={"system"} docker ps ``` *** ## Connecting your Core Connect your Core instance to your dashboard with the Query Agent. Make sure you have a running Core instance. Follow [our Core deployment guide](/home/deploy) for setup, scaling, and production hardening. 1. Open `ENTERPRISE_PUBLIC_URL` in your browser, sign up, and create your workspace. 2. Click **Connect new instance** from the homepage. 3. Enter your Core URL and secret key, then submit the form. Instance creation form with instance name, Core URL, and secret key fields 4. Copy the **Connection key** from the instance details page. Instance details page showing where to find the connection key Run the Query Agent where it can reach your Core database, and set the connection URL to the WebSocket version of `ENTERPRISE_PUBLIC_URL` with path `/ws/agent`: | `ENTERPRISE_PUBLIC_URL` | `CONNECTION_URL` | | :------------------------------ | :------------------------------------- | | `https://ledger.yourdomain.com` | `wss://ledger.yourdomain.com/ws/agent` | | `http://localhost:8080` | `ws://localhost:8080/ws/agent` | ```bash Run Query Agent wrap theme={"system"} docker run -d \ -e DB_URL="postgres://username:password@host:5432/blnk?sslmode=require" \ -e CONNECTION_KEY="sk_live_..." \ -e CONNECTION_URL="wss://ledger.yourdomain.com/ws/agent" \ blnkfinance/query-agent:latest ``` | Parameter | Description | | :--------------- | :--------------------------------------------------------------------------------------------------------------- | | `DB_URL` | Postgres connection string for your Core database. Find it in the `database_url` field in your `blnk.json` file. | | `CONNECTION_KEY` | Connection key from the instance details page in the dashboard. | | `CONNECTION_URL` | WebSocket URL for your dashboard. | Go to **Settings > Instances** in the dashboard. Your instance should show as **Connected** with a green indicator. Instance connection status showing Connected with green indicator