Shared Environment Variables

All shared environment variables for the Integratewise platform are configured in Vercel and automatically deployed across Production, Preview, and Development environments.

Configuration Management

Environment variables are managed through:

• Vercel Project: integratewise-live-desktop (prj_9qtr2VovM5PieoUaSGJX2CwzQMal)
• Team: spine-workspace-2a626284
• Scope: team_KvVZddhjBYdibkqW29AY1JGp

Public Application Configuration (NEXTPUBLIC*)

These variables are visible to the client and configure platform behavior:

Version & API Configuration

Variable	Value	Purpose
NEXT_PUBLIC_APP_VERSION	1.0.0	Application semantic version
NEXT_PUBLIC_API_BASE_URL	https://api.integratewise.ai	Base URL for API requests
NEXT_PUBLIC_GATEWAY_ENDPOINT	https://api.integratewise.ai/api/v1	Gateway service endpoint
NEXT_PUBLIC_GATEWAY_TIMEOUT	30000	HTTP request timeout in milliseconds
NEXT_PUBLIC_GATEWAY_RETRIES	3	Number of retry attempts on failure

Spine Network Configuration

Variable	Value	Purpose
NEXT_PUBLIC_SPINE_ENDPOINT	https://api.integratewise.ai/api/v1/spine	Spine network service endpoint
NEXT_PUBLIC_SPINE_PROVIDER	gateway-proxy	Spine provider implementation (gateway-proxy, direct, etc.)
NEXT_PUBLIC_SPINE_NETWORK_ID	spn_0xA1B	Unique identifier for the Spine network

Workspace & Tenant Configuration

Variable	Value	Purpose
NEXT_PUBLIC_WORKSPACE_ID	ws_core	Primary workspace identifier
NEXT_PUBLIC_TENANT_ID	iw-customer-zero	Tenant/organization identifier
NEXT_PUBLIC_DEFAULT_PROFILE	operator	Default user profile for unauthenticated users
NEXT_PUBLIC_SESSION_TIMEOUT	3600000	Session timeout in milliseconds (1 hour)

Connector & Integration Configuration

Variable	Value	Purpose
NEXT_PUBLIC_ENABLED_CONNECTORS	salesforce,hubspot,github,linear,slack,notion,google-drive,stripe	Comma-separated list of enabled integrations
NEXT_PUBLIC_NANGO_HOST	https://api.nango.dev	Nango API platform for OAuth management

Feature Flags

Variable	Value	Purpose
NEXT_PUBLIC_FEATURE_WORKBENCH	true	Enable Workbench UI (connectors, MCP, execution)
NEXT_PUBLIC_FEATURE_MARKETPLACE	true	Enable Marketplace for discovering integrations
NEXT_PUBLIC_FEATURE_GOVERNANCE	true	Enable Governance policies and audit logs
NEXT_PUBLIC_FEATURE_TWIN_AGENT	true	Enable Twin Agent for autonomous operations
NEXT_PUBLIC_FEATURE_MCP	true	Enable Model Context Protocol support

Debugging & Observability

Variable	Value	Purpose
NEXT_PUBLIC_LOG_LEVEL	info	Logging level (debug, info, warn, error)
NEXT_PUBLIC_DEBUG	false	Enable debug mode (verbose logging, DevTools)

Loading Environment Variables

The application uses the centralized lib/env.ts module:

const config = getConfig();
console.log(config.api.baseUrl); // https://api.integratewise.ai
console.log(config.features.workbench); // true

Profile-Aware Configuration

User access is controlled by profile:

Profile	Default Route	Accessible Features
operator	/my-work	Workbench, connectors, MCP
integrator	/marketplace	Marketplace, custom connectors, integrations
admin	/admin	All features, governance, configuration
analyst	/analytics	Read-only analytics, reports
guest	/	Public marketplace only

Connector-Aware Routing

The ConnectorConfigurationManager filters connectors by:

• Enable/disable status (via NEXT_PUBLIC_ENABLED_CONNECTORS)
• User profile (profile must have connector access)
• Origin (CRM, Engineering, Communication, Knowledge, Storage, Payments)
• Auth type (OAuth 2.0, API Key)

Deployment

All variables are automatically:

1. Created in Vercel via the vercel env add CLI
2. Available in .env.development.local during local development
3. Injected at build time into production bundles
4. Redeployed when git push triggers Vercel build

Local Development

To pull variables locally:

cd apps/platform
vercel env pull .env.development.local --scope team_KvVZddhjBYdibkqW29AY1JGp

To update a variable in Vercel:

vercel env add NEXT_PUBLIC_LOG_LEVEL production,preview,development --value debug --scope team_KvVZddhjBYdibkqW29AY1JGp

Adding New Variables

When adding environment variables:

1. Update .env.example with the new key and description
2. Add to lib/env.ts in the appropriate configuration section
3. Create in Vercel:

   vercel env add NEW_VAR_NAME --scope team_KvVZddhjBYdibkqW29AY1JGp
   

4. Commit both .env.example and lib/env.ts changes
5. Reference in code via getConfig() helper

References

• Vercel Environment Variables
• lib/env.ts - Configuration schema
• lib/connector-manager.ts - Connector routing
• .env.example - Variable documentation