Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Preview: Remote Dev Environments Portal is in preview. Features may change as the product evolves.

​
Overview

The workspace management page gives admins a bird’s-eye view of every workspace in the organization, regardless of who created it. From here you can monitor workspace status, take lifecycle actions, and control resource usage across your team.

​
Viewing Workspaces

Navigate to Admin > Workspaces to see all workspaces in your organization. Each workspace entry shows:
FieldDescription
Workspace NameThe name the builder chose when creating the workspace
Owner EmailThe email address of the builder who owns the workspace
BlueprintThe blueprint template the workspace was created from
StatusCurrent state: Running, Stopped, Deploying, or Error
ClusterThe Kubernetes cluster where the workspace is running (visible when the organization has multiple clusters)
CreatedWhen the workspace was first created
You can filter workspaces by status or cluster, and search by workspace name or owner email to quickly find what you need.

​
Workspace Actions

Admins can perform the following actions on any workspace:

Start

Resume a stopped workspace. The environment redeploys and becomes accessible to the builder.

Stop

Pause a running workspace. All services are stopped but state is preserved. The builder’s work is retained and available when the workspace is started again.

Restart

Stop and start the workspace. This picks up the latest container image updates from the blueprint. Use this to roll out image-level changes to an existing workspace.

Delete

Permanently remove the workspace and its associated Qovery project. This action cannot be undone.

Upgrade

Redeploy the workspace with the latest blueprint configuration. Use this when structural changes have been made to the blueprint (new services, updated environment variables).
Deleting a workspace is irreversible. The workspace’s Qovery project, environment, all services, and any data within them are permanently destroyed. Make sure the builder has saved any important work before deleting.

​
Monitoring

The admin dashboard provides summary statistics at the top of the workspace management page:
  • Running - Number of workspaces currently active and consuming resources
  • Stopped - Number of paused workspaces (not consuming compute resources)
  • Error - Number of workspaces in an error state that may need attention
  • Total Blueprints - Number of registered blueprints in the organization
Use these stats to get a quick sense of resource utilization and identify workspaces that need attention.
Workspace statuses update reactively. During active transitions (deploying, restarting), the dashboard polls every 3 seconds. Once all workspaces reach a stable state, polling slows to every 15 seconds to reduce API load.

​
Infrastructure Overview

The admin dashboard includes an infrastructure topology graph that visualizes the relationship between clusters, blueprints, and workspaces across your organization. The graph displays:
  • Cluster nodes - Each Kubernetes cluster in your organization
  • Blueprint nodes - Blueprints connected to their target cluster, showing owner and status
  • Workspace nodes - Active workspaces connected to their source blueprint, showing status indicators
The graph auto-layouts using a hierarchical top-down arrangement. Use it to quickly understand how workspaces are distributed across your infrastructure and identify clusters or blueprints with high utilization.
The infrastructure graph updates in real time. Workspace status changes (deploying, running, stopped, error) are reflected automatically with adaptive polling - faster updates during active changes, slower polling when stable.

​
Workspace Limits

Admins can configure a maximum number of running workspaces per user. This prevents any single user from consuming too many resources. When a builder reaches their limit and tries to create a new workspace, they see a quota modal explaining that they must stop an existing workspace before creating a new one. To configure workspace limits:
1

Open Settings

Navigate to Admin > Settings.
2

Set the Limit

Find the Workspace Limits section and enter the maximum number of simultaneously running workspaces per user.
3

Save

Click Save. The limit takes effect immediately for all users.
Workspace limits apply to running workspaces only. Stopped workspaces do not count toward the limit. A user can have many stopped workspaces but only run a limited number concurrently.

​
Cost Control Tips

Check the admin dashboard frequently to see how many workspaces are actively running. A high running count directly translates to infrastructure costs on your cluster.
Configure per-user workspace limits to prevent any individual from spinning up more resources than necessary. Start with a conservative limit (e.g., 2-3 running workspaces) and adjust based on actual usage.
If you see workspaces that have been running for extended periods without activity, reach out to the owner or stop them directly. Idle workspaces consume compute resources unnecessarily.
Workspaces that haven’t been used in weeks are good candidates for deletion. Coordinate with the owner first to ensure no important work is lost.
Include TTL lifecycle jobs in your blueprint environments that automatically stop workspaces after a period of inactivity. This is the most effective way to control costs without manual intervention.

​
Next Steps

Blueprint Management

Register and configure blueprint templates.

Publish Approvals

Review and approve workspace deployment requests.

Member Management

Invite and manage team members.