Deploy the Blnk Production License

The Production License lets you run the Cloud Dashboard in your own infrastructure. We recommend deploying Blnk Core separately, then running the dashboard and connecting your Core to it. Built for teams that need stronger security controls, data residency support, custom tooling, or a closer operational partnership with Blnk.

Dashboard deployment guide

Use this guide to deploy the Cloud Dashboard on AWS, GCP, Azure, or any cloud provider.

Get your Production License

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.

Prepare your database

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:

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 Docker image

Pull the enterprise image from GitHub Container Registry:

Docker

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.

Add primary environment variables

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.

.env

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.

Set up public app config

Add these variables to the same environment file. They configure how users access the Cloud Dashboard.

.env

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.

Set up Plane environment variables

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.

.env

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.

Run the enterprise image

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.

Docker

docker run -d \
  --name blnk-enterprise \
  -p 8080:8080 \
  ghcr.io/blnkfinance/blnk-enterprise:0.1.23

Confirm that your deployment is live:

Check deployment status

docker ps

Connecting your Core

Connect your Core instance to your dashboard with the Query Agent.

Deploy Blnk Core

Make sure you have a running Core instance.Follow our Core deployment guide for setup, scaling, and production hardening.

Create an instance on the dashboard

Open ENTERPRISE_PUBLIC_URL in your browser, sign up, and create your workspace.
Click Connect new instance from the homepage.
Enter your Core URL and secret key, then submit the form.
Copy the Connection key from the instance details page.

Run the Query Agent

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`

Run Query Agent

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.

Verify connection

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

Start Here

Instances

Ledgers

Balances

Transactions

Identities

Reconciliation

Filters & Views

Alerts

Insights

Settings

Integrations

Deploy the Blnk Production License

Dashboard deployment guide

Connecting your Core

​Dashboard deployment guide

​Connecting your Core

Dashboard deployment guide

Connecting your Core