Environments overview
What an Environment is in the dashboard, how it relates to Applications, Services, and Worker Nodes, and where to go next.
Written By Zoro
Last updated 3 days ago
An Environment
is an isolation stage inside an Application, for example production, staging, or a custom name you define. Every Service you run belongs to exactly one Environment, and Worker Nodes (or managed compute) attach at the Environment layer so everything in that stage shares the same compute pool.
Start with the conceptual map in Environments under Core Concepts in the sidebar and How dFlow is structured under Core Concepts in the sidebar.
Where Environments appear in the dashboard
Open an Application from your organisation. Use the Environments tab to see Manage Environments: a table of Name, Status, Compute, and Services, plus Add Environment. Click a row to open that Environment’s detail view with tabs such as Overview, Services, Compute, and Settings.
Application-level settings (name, description, delete Application) live under the Application Settings tab. See Application settings under Applications in the sidebar. Environment name, default flag, and delete are under each Environment’s Settings tab.
What you do with Environments
- Add a stage: Create an environment (wizard: Environment → Compute → Activation).
- Attach or change compute: Attach compute to an environment and the Worker Nodes and Compute under Worker Nodes and Compute in the sidebar section.
- Understand draft vs active: Draft vs active environments.
- Adjust name or default Environment: Environment settings.
- Operate safely at scale: Environment best practices.
Compute and Worker Nodes
Services run on Worker Nodes you operate or on dFlow-managed capacity where your plan supports it. Adding a node, SSH onboarding, and provider-specific setup are documented under Worker Nodes and Compute under Worker Nodes and Compute in the sidebar (not only under Environments). After a node exists, you attach it to the Environment that should use it.
On dFlow Cloud, also read Choose compute / managed infrastructure under dFlow Cloud in the sidebar for how managed vs self-hosted nodes fit the model.
If something fails
- Compute and worker node issues under Troubleshooting in the sidebar
- Troubleshooting overview under Troubleshooting in the sidebar