v0.4.0GitHub

Self-hosting

Enterprise deployment

Private tenant, MDM extension rollout, and MCP fleet configuration.

View as Markdown

Private tenant

Set PLASMO_PUBLIC_BLEKLINE_APP_ORIGIN for the browser extension so agents talk to your tenant first.

Control plane URL examples:

  • SaaS: https://app.blekline.com
  • Private: https://app.customer.com

MCP fleet rollout

  1. Build packages once in CI: pnpm build:packages
  2. Generate configs: pnpm generate:mcp-configs
  3. Distribute generated configs from your organization's repository:
    • .cursor/mcp.json (Cursor)
    • config/claude-desktop.generated.json (Claude Desktop merge)
    • .codex/config.toml (Codex)
  4. Subscribe sidecars to GET /api/workspace/policy-stream (SSE) for live policy updates.

MDM / forced extension

Chrome/Edge enterprise policies can pin the Blekline extension ID and allowlist app.blekline.com (or private tenant origin).

Remote MCP (SSE)

For k8s or VPC deployments without stdio:

BLEKLINE_MCP_TRANSPORT=sse BLEKLINE_MCP_PORT=3200 node packages/mcp-server/dist/index.js

Health: GET http://127.0.0.1:3200/health
Connect: GET http://127.0.0.1:3200/sse

Regions

Default SaaS primary processing runs in the EEA (see Subprocessors): Vercel Frankfurt (fra1), Supabase Ireland (eu-west-1), Azure Germany West Central.

US-primary hosting: contact enterprise sales with dataResidency=US on the lead form (/api/enterprise/lead) or at enterprise@blekline.com.


Next steps: AI Enablement Stack · Architecture · SSO & deployment · Open workspace · Report issue