Server-side flags

Long-running Node services (API, loyalty, business, identity, notifications) evaluate flags via the Edge Proxy inside the Container App Environment. No API gateway, no browser.

Service → http://feye-flagsmith-edge-proxy-{env}-ca/api/v1 → Edge Proxy → Flagsmith Core

The web app is not covered here — see client-side.

Environment variables

Variable	Value
FLAGSMITH_API_URL	http://feye-flagsmith-edge-proxy-{env}-ca/api/v1
FLAGSMITH_ENVIRONMENT_KEY	From Key Vault / service .env

Each service has a feature-flags.ts module that exposes a shared client. Import flags from @repo/feature-flags and call isEnabled on that client.

Caching

Services cache flags in memory and refresh periodically. After a toggle in the admin UI, expect up to ~40 seconds before a running service sees the change.

If the proxy is unreachable, the registry defaultValue is used.

Local development

Backend containers use FLAGSMITH_API_URL=http://flagsmith-edge-proxy:8000/api/v1. Set FLAGSMITH_ENVIRONMENT_KEY in each service’s .env — see Docker Compose.

Related

• Overview
• Client-side