ironflow env

Manage environments.

ironflow env <subcommand> [flags]

Environments provide logical isolation within a single Ironflow instance. All data (functions, events, runs, streams, projections) is scoped to the environment that created it. API keys are managed separately via ironflow apikey — see API Keys.

Ironflow creates one default environment on first boot:

Name	ID
default	env_default

ironflow env list

List all environments as a table with the columns ID, NAME and CREATED.

ironflow env list [--server URL]

ironflow env create

Create a new environment.

ironflow env create <name> [--server URL] [--project PROJECT_ID]

Flag	Type	Default	Description
--project	string		Project ID to associate with the environment. When omitted, the server uses the project of your credentials; with none, it answers 400

Creates an isolated namespace within your Ironflow instance. The new environment starts empty — no functions, events, or runs. The server builds the environment ID as env_<project-slug>_<name>. If another project, for example a same-named project in another organization, already holds that ID, the server adds a short hash: env_<project-slug>-<hash>_<name>. Use the ID that ironflow env list prints.

ironflow env delete

Delete an environment by ID.

ironflow env delete <id> [--server URL]

Deletes the environment. The default environment (env_default) cannot be deleted.

All env subcommands accept --server / -s to override the server URL.

Examples:

# List environments
ironflow env list

# Create a new environment for a specific app
ironflow env create my-app

# Delete a custom environment (ID as printed by `env list`)
ironflow env delete env_default_my-app

---