Skip to main content
When Self-Hosting, you configure Corgtex using environment variables (typically stored in a .env file).

​
Core Application Settings

The variables defined here are strictly required to start the web and worker processes successfully.
VariableDescription
DATABASE_URLThe PostgreSQL connection string. Must include credentials and the database name. Example: postgresql://postgres:pass@localhost:5432/corgtex
APP_URLThe fully qualified base URL where this runtime is hosted (for example, https://app.corgtex.com for the dogfood product app, https://ops.corgtex.com for Ops, or a customer runtime domain). Used for OAuth redirects and webhook signing.
SESSION_COOKIE_SECRETA 32+ character random string used for signing secure cookies. Never expose this.

​
Initial Seeding Settings

When you launch a fresh Corgtex instance, the database must be seeded with an initial workspace and an administrative user.
VariableDescription
WORKSPACE_NAMEThe display name of the initial workspace (e.g., “Acme Corp”).
WORKSPACE_SLUGThe URL-friendly identifier for the workspace (e.g., “acme-corp”).
ADMIN_EMAILThe email address for the initial bootstrap admin user.
ADMIN_PASSWORDThe password for the initial bootstrap admin user.
CONTROL_PLANE_TESTER_EMAILOptional separate global operator email for auditable Control Plane production testing. Must differ from ADMIN_EMAIL.
CONTROL_PLANE_TESTER_PASSWORDPassword for the optional Control Plane tester account. Required when CONTROL_PLANE_TESTER_EMAIL creates the account, or when SEED_RESET_PASSWORDS=true.
CONTROL_PLANE_TESTER_DISPLAY_NAMEOptional display name for the Control Plane tester account. Defaults to “Control Plane Test Operator”.
SEED_SCRIPTSOptional comma-separated list of extra Node seed scripts to run after the base seed at web startup. Use only for public-safe or deployment-specific fixtures.
CORGTEX_AUTO_SEED_JNJ_DEMOSet to true only on shared demo/trial runtimes that should refresh the public J&J demo workspace on each deploy. This runs scripts/seed-jnj-demo.mjs after the base seed.

​
Model Provider Settings

By default, the platform relies on external Large Language Models to power the Organization Brain and agents. While these are optional at startup, they are recommended for full functionality.
VariableDescription
MODEL_PROVIDERDefines which LLM gateway to use. Valid options: openrouter, openai.
MODEL_API_KEYYour API key for the chosen provider.
MODEL_CHAT_DEFAULTThe specific model string to use for conversational features (e.g., google/gemma-4-31b-it).
MODEL_EMBEDDING_DEFAULTThe specific model string to use for vector embeddings (e.g., text-embedding-3-small).
Setting MODEL_PROVIDER allows Corgtex’s internal abstractions to handle the LLM routing without baking a specific vendor dependency into your infrastructure.

​
Performance and Session Coordination

Production and client instances should use Redis for shared short-lived state. Postgres remains the permanent source of truth.
VariableDescription
REDIS_URLRedis connection string used for shared rate limiting, short-lived Brain retrieval cache, and session heartbeat throttling. Required for scaled production/client deployments.
REDIS_KEY_PREFIXPrefix for Redis keys. Use a deployment-specific value such as corgtex-prod or crina-prod so environments do not collide.
SESSION_LAST_SEEN_WRITE_INTERVAL_MSOptional session heartbeat throttle. Defaults to 300000 (5 minutes).
On Railway, add a Redis service in the same project and environment as the app, then set REDIS_URL on every runtime service that handles requests or jobs, normally web and worker. Use Railway reference variables, for example: 
REDIS_URL="${{Redis.REDIS_URL}}"
REDIS_KEY_PREFIX="client-slug-prod"

​
Intercom Support Settings

These variables enable Intercom Messenger and Fin support on hosted Corgtex site/app surfaces. Leave them unset for customer-owned or self-managed runtimes unless that customer explicitly wants Intercom enabled.
VariableDescription
NEXT_PUBLIC_INTERCOM_APP_IDIntercom Messenger app ID for the shared Corgtex support workspace. This is safe to expose to the browser.
NEXT_PUBLIC_INTERCOM_API_BASEMessenger API base for the Intercom workspace region. Defaults to https://api-iam.intercom.io.
INTERCOM_MESSENGER_SECRETServer-only Messenger JWT secret from Intercom’s Messenger Security settings. Required for authenticated app users and must never be exposed to browser code, logs, PRs, or support messages.

​
Corgtex Connector Settings

These variables configure the remote MCP connector used by ChatGPT, Claude, Cursor, and other MCP clients.
VariableDescription
MCP_PUBLIC_URLPublic connector URL shown in the UI and used as the OAuth resource audience. Defaults to ${APP_URL}/mcp. For the central connector, use a stable URL such as https://mcp.corgtex.com/mcp.
MCP_DEFAULT_INSTANCE_SLUGOptional instance slug for this deployment. If omitted, Corgtex uses WORKSPACE_SLUG or infers crina from a Crina host name.
MCP_INSTANCE_REGISTRYOptional JSON array of registered connector instances. Each entry supports slug, displayName, baseUrl, workspaceIds, workspaceSlugs, and status. Unknown workspaces are rejected when a registry is configured.

​
Google Workspace Integration

These variables enable Google Calendar sync and selected-file Google Drive ingestion.
VariableDescription
GOOGLE_CLIENT_IDOAuth web client ID from Google Auth Platform. Register ${APP_URL}/api/integrations/google/callback as an authorized redirect URI and ${APP_URL} as an authorized JavaScript origin.
GOOGLE_CLIENT_SECRETOAuth web client secret. Store only as a server-side deployment secret.
NEXT_PUBLIC_GOOGLE_PICKER_API_KEYBrowser-safe Google Picker API key, restricted in Google Cloud to the production app origin such as https://app.corgtex.com.
NEXT_PUBLIC_GOOGLE_CLOUD_PROJECT_NUMBERGoogle Cloud project number used as the Picker app ID. This is not a secret.
Corgtex requests https://www.googleapis.com/auth/calendar.readonly for calendar sync and https://www.googleapis.com/auth/drive.file for selected Drive files. Do not add broad Drive scopes unless a separate product requirement and Google verification justification are approved.

​
Object Storage

File uploads and Brain source downloads use an S3-compatible storage backend. Client instances that allow uploads must configure this for every runtime service that touches uploads, normally web and worker.
VariableDescription
S3_ENDPOINTS3-compatible endpoint. For Railway buckets this is the bucket credential endpoint.
S3_BUCKET_NAMEBucket name used by the app.
AWS_S3_BUCKET_NAMECompatibility alias for bucket name. Set to the same value as S3_BUCKET_NAME.
S3_REGIONStorage region. Railway buckets commonly use auto.
S3_ACCESS_KEY_IDS3-compatible access key ID.
S3_SECRET_ACCESS_KEYS3-compatible secret access key.
S3_ACCESS_KEYCompatibility alias for access key ID. Set to the same value as S3_ACCESS_KEY_ID.
S3_SECRET_KEYCompatibility alias for secret access key. Set to the same value as S3_SECRET_ACCESS_KEY.
On Railway, create or reuse a project bucket, read its S3-compatible credentials with the Railway dashboard or CLI, and set the variables above on web and worker. Do not print access keys or secret keys in logs, PRs, tickets, or support messages.

​
Hosted Control Plane Settings

These variables are only needed by the dedicated Corgtex Ops control plane or by product/customer runtimes that need to link back to it. The canonical public Ops host is https://ops.corgtex.com; raw Railway service URLs are implementation URLs only.
VariableDescription
RAILWAY_API_TOKENRailway API token used by the internal control plane to provision customer projects and services. Store only as a deployment secret.
RAILWAY_GRAPHQL_ENDPOINTOptional override for Railway’s GraphQL endpoint. Leave unset unless Railway support directs otherwise.
CONTROL_PLANE_MODESet to true only for the dedicated Ops deployment. Operators landing on / are sent to /control-plane, and control-plane UI/API routes are active only in this mode.
CONTROL_PLANE_URLCanonical Ops origin used by non-Ops deployments when linking or redirecting to the control plane. Production product and customer runtimes should set this to https://ops.corgtex.com. Local development can leave it unset to keep links relative.
CONTROL_PLANE_AGENT_API_KEYBearer secret for control-plane CLI/MCP automation. Requests use Authorization: Bearer cp-<value>. Store only as a deployment secret.
CONTROL_PLANE_AGENT_SCOPESOptional comma- or space-separated scopes for control-plane CLI/MCP automation. Omit for read-only access; include only the mutation scopes needed by the operator workflow.
CORGTEX_CUSTOMER_DEPLOYMENT_BOOTSTRAP_TOKEN_HASHSHA-256 hash of the one-time bearer token accepted by a customer runtime’s internal bootstrap endpoint. Prefer this over storing the raw token.
CORGTEX_CUSTOMER_DEPLOYMENT_BOOTSTRAP_TOKENLegacy raw-token fallback for bootstrap endpoints. Use only while rotating to CORGTEX_CUSTOMER_DEPLOYMENT_BOOTSTRAP_TOKEN_HASH.
CORGTEX_RELEASE_VERSIONRelease version reported by /api/health for fleet drift checks.
CORGTEX_RELEASE_IMAGE_TAGImmutable image tag reported by /api/health and used by the control plane for customer deployments.
The dedicated Ops control plane exposes operator-only routes for automation. These routes return unavailable outside CONTROL_PLANE_MODE=true, even if the code is deployed on app.corgtex.com or a customer runtime:
RoutePurpose
GET /api/admin/customer-deploymentsList managed customer deployments and their operational status.
POST /api/admin/customer-deploymentsProvision a dedicated customer project from pinned release images and private bundle metadata.
POST /api/admin/customer-deployments/:deploymentId/healthProbe the customer runtime health endpoint and record release drift.
POST /api/admin/customer-deployments/:deploymentId/bootstrapTrigger one-time private bundle bootstrap on the customer runtime.
POST /api/admin/customer-deployments/:deploymentId/upgradeUpdate pinned release images and redeploy web and worker services.
POST /api/admin/customer-deployments/:deploymentId/suspendMark a customer deployment suspended in the control plane.
GET /api/control-plane/deploymentsList customer deployments for operator dashboards or automation.
POST /api/control-plane/deployments/:deploymentId/support-connectorStore or rotate an encrypted support connector credential for a customer deployment.
POST /api/control-plane/deployments/:deploymentId/snapshotPull a live support snapshot through the customer support connector.
POST /api/control-plane/deployments/:deploymentId/operationsRun an audited support operation through the support connector.
POST /api/control-plane/mcpMCP-style control-plane automation endpoint for agents and CLI support workflows.
Old UI links under /control-plane/customers/:deploymentId are kept as compatibility redirects only. New operator links must use /control-plane/deployments/:deploymentId.

​
Example .env File

# Database
DATABASE_URL="postgresql://postgres:postgres@postgres:5432/corgtex"

# Core App
APP_URL="http://localhost:3000"
SESSION_COOKIE_SECRET="<replace-with-32-character-random-secret>"

# Seed Data (First Workspace)
WORKSPACE_NAME="Acme Demo"
WORKSPACE_SLUG="acme-demo"
ADMIN_EMAIL="admin@acme.com"
ADMIN_PASSWORD="<replace-with-bootstrap-admin-password>"
CONTROL_PLANE_TESTER_EMAIL="control-plane-qa@acme.com"
CONTROL_PLANE_TESTER_PASSWORD="<replace-with-separate-control-plane-test-password>"

# LLM Config (Optional)
MODEL_PROVIDER="openrouter"
MODEL_API_KEY="<replace-with-provider-api-key>"
MODEL_CHAT_DEFAULT="anthropic/claude-3.5-sonnet"
MODEL_EMBEDDING_DEFAULT="openai/text-embedding-3-small"

# Redis (Production / Client Instances)
REDIS_URL="redis://redis:6379"
REDIS_KEY_PREFIX="corgtex-local"

# Google Workspace OAuth and Picker
GOOGLE_CLIENT_ID="..."
GOOGLE_CLIENT_SECRET="..."
NEXT_PUBLIC_GOOGLE_PICKER_API_KEY="..."
NEXT_PUBLIC_GOOGLE_CLOUD_PROJECT_NUMBER="..."

# S3-Compatible Storage
S3_ENDPOINT="https://storage.example.com"
S3_BUCKET_NAME="corgtex"
AWS_S3_BUCKET_NAME="corgtex"
S3_REGION="auto"
S3_ACCESS_KEY_ID="..."
S3_SECRET_ACCESS_KEY="..."
S3_ACCESS_KEY="..."
S3_SECRET_KEY="..."