Environments

Every SignaKit project has two environments: Development and Production. Environments let you change flag states, run experiments, and test targeting rules without affecting what your users see in production. A flag can be fully enabled in Development and completely off in Production — at the same time.

How environments work

Each environment is an isolated configuration space. Flag states, targeting rules, percentage rollouts, and experiment assignments are all stored and evaluated independently. Changing a flag in Development has no effect on Production.

The workflow is intentional: turn a flag on in Development, validate the behavior, then flip it in Production when you're confident.

SDK keys

Each environment has its own SDK key. The key determines which environment's flag configuration the SDK fetches. A key scoped to Development will never return Production flag states, and vice versa.

SDK keys follow this format:

sk_dev_yourOrgId_yourProjectId_randomString   # Development
sk_prod_yourOrgId_yourProjectId_randomString  # Production

To find your SDK keys, open the SignaKit dashboard, select your project, and navigate to Settings → SDK Keys.

Configuring your SDK key

Store the key in an environment variable and let your deployment environment supply the correct value.

SIGNAKIT_SDK_KEY=sk_dev_xxxx

SIGNAKIT_SDK_KEY=sk_prod_xxxx

Your application code reads the same variable in both environments:

import { createInstance } from '@signakit/flags-node'

const client = createInstance({
  sdkKey: process.env.SIGNAKIT_SDK_KEY!,
})

No code changes are needed when going to production — only the environment variable value changes.

Flag states are independent per environment

A flag's enabled/disabled state, targeting rules, rollout percentage, and experiment configuration are stored separately for each environment. There is no automatic sync between Development and Production.

Some common scenarios:

Select the environment from the top navigation in the dashboard, then configure the flag — every change applies only to the selected environment.

Related

• Feature Flags — how flag config is fetched and decisions are evaluated
• SDK Architecture — how the SDK fetches and caches flag config
• Node.js SDK — initializing the SDK with an SDK key