04 / Operations

Container Management

Start, stop, restart and inspect every container in the project.

In this feature

Start, stop, restart and remove any container
Live CPU and memory usage per container
Published URLs and exposed port mappings
Edit image, restart policy, ports and volumes
Declare container dependencies and network membership
Environment section with all variables for the project

// In the console

What it looks like

A full management panel per project: container cards with image, published URLs, CPU and memory usage, exposed ports, lifecycle controls, and an editor for names, images, restart policy, ports, volumes, dependencies and networks.

Container Management — Container Editor — cards per container with image, URLs, live CPU/memory, ports and lifecycle controls.

Container Management — detail — Container detail — name, image, restart policy, ports, volumes, dependencies and network membership.

Control

Lifecycle without the CLI

Every action an operator would run over SSH — restart, stop, recreate, remove — is one click, executed on the correct host with an audit entry.

Configuration

Structured, not free-text

Ports, volumes, dependencies and networks are edited as typed fields, so an invalid mapping is caught before it reaches the daemon.

Secrets

Environment handled carefully

Variables are grouped per project and can be delegated to a secrets backend, keeping credentials out of the compose file that lives in Git.

Included out of the box

Start, stop, restart and remove any container

Live CPU and memory usage per container

Published URLs and exposed port mappings

Edit image, restart policy, ports and volumes

Declare container dependencies and network membership

Environment section with all variables for the project

Next feature

Visual Container Designer

Continue

Get started

Run your containers from one console

Talk to the team