Enterprise customers can deploy CoopAI on their own infrastructure with full control over data residency and LLM routing.

Deployment options

Option	Best for
Hosted Coop (`api.coop-ai.dev`)	Fastest start; Coop manages infrastructure
Self-hosted (Railway)	Single-tenant on Railway with your env vars
Self-hosted (Docker)	Full control on your VPC

Contact hello@coop-ai.dev for Enterprise licensing and deployment support.

Core components

Service	Purpose
API	Chat, completions, webhooks, integrations
Postgres	Orgs, users, API keys, integration tokens
Redis (optional)	Job queue, caching
Admin portal	Org admin UI (`admin.coop-ai.dev` or self-hosted)

Required environment variables

Copy .env.backend.example to .env.backend on your API host:

Category	Variables
Core	`DATABASE_URL`, `CREDENTIALS_ENCRYPTION_KEY`, `COOP_PUBLIC_BASE_URL`
LLM	`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, etc.
GitHub	`GITHUB_APP_ID`, `GITHUB_APP_PRIVATE_KEY`, `GITHUB_APP_SLUG`
Slack	`SLACK_APP_CLIENT_ID`, `SLACK_APP_CLIENT_SECRET`
Atlassian	`ATLASSIAN_APP_CLIENT_ID`, `ATLASSIAN_APP_CLIENT_SECRET`
Notion	`NOTION_APP_CLIENT_ID`, `NOTION_APP_CLIENT_SECRET`
Google	`GOOGLE_DOCS_APP_CLIENT_ID`, `GOOGLE_DOCS_APP_CLIENT_SECRET`

Deploy with Docker

docker compose up -d --build api

Verify: curl https://your-api-host/health returns "ok": true.

OAuth callback URLs

Provider	Callback
GitHub	`https://your-api-host/v1/github/app/callback`
Slack	`https://your-api-host/v1/slack/app/callback`
Atlassian	`https://your-api-host/v1/atlassian/app/callback`
Notion	`https://your-api-host/v1/notion/app/callback`
Google Docs	`https://your-api-host/v1/google-docs/app/callback`

Lightning Mode (Pro/Enterprise)

Lightning Mode indexes repos on Coop cloud infrastructure for faster symbol-graph retrieval. Self-hosted Enterprise can enable managed indexing or run index jobs locally.

Webhooks

Configure GitHub/GitLab webhooks pointing to:

https://your-api-host/webhooks/github

Coop processes push and PR events to update the code graph.

Admin portal

API server — set COOP_ADMIN_PORTAL_URL to your admin portal origin (used in emails and redirects).
Admin Next.js deploy — set NEXT_PUBLIC_ADMIN_PORTAL_URL to the same origin (client-side links).

Developers and admins use the portal for org configuration.

SAML SSO (Enterprise)

Enterprise orgs can enable SAML 2.0 for admin portal and extension sign-in. Full walkthrough: Single Sign On (SSO).

Org admins configure SSO in the admin portal (Settings → Single sign-on). End users sign in via the admin portal or VS Code extension only — they never edit server environment variables.

Required: public API base URL (operators only)

COOP_PUBLIC_BASE_URL is a server-side environment variable on the API host. It must be the public HTTPS origin your IdP can reach (e.g. https://api.coop-ai.dev). SAML service provider URLs are derived from this value — if it is missing or wrong, ACS callbacks and metadata will fail and the admin portal shows Service provider URLs unavailable.

Set it in .env.backend, then restart the API after changing it. Org admins copy the resulting SP values from the admin portal.

Service provider URLs

With COOP_PUBLIC_BASE_URL=https://your-api-host:

Value	Pattern
Entity ID	`https://your-api-host/v1/auth/saml/metadata` (default; override with `COOP_SSO_SP_ENTITY_ID`)
ACS URL	`https://your-api-host/v1/auth/saml/callback`
Metadata URL	`https://your-api-host/v1/auth/saml/metadata` (Enterprise admin bearer)
SSO start	`https://your-api-host/v1/auth/saml/start?org={orgName}` (public; org name is case-insensitive)

Org admins copy these from Settings → Single sign-on in the admin portal, or download SP metadata from that page.

Optional SSO env vars

Variable	Purpose
`COOP_SSO_SP_ENTITY_ID`	Override default SP Entity ID (defaults to metadata URL)
`COOP_SSO_SESSION_TTL_MS`	SSO session lifetime in ms (default `43200000` — 12 hours)

See .env.backend.example for names and defaults.

Post-deploy validation (operators only)

After the API is running with COOP_PUBLIC_BASE_URL set, Coop operators can run an automated SSO smoke test from the deployment repo:

npm run smoke:sso

This verifies /v1/sso/config, SAML start redirect, and prints portal credentials for a browser Test connection. Org admins configure production IdP settings in the admin portal — see Single Sign On (SSO).

Enterprise deployment