Status Panel is the server-side runtime and control surface that helps teams observe and manage deployed stacks after launch.
In the current TryDirect model, Status Panel is not just a tiny Docker dashboard. It is the operational layer that can report health, fetch logs, expose metrics, and execute validated actions on the target server.
A simple way to think about it: Stacker helps define and dispatch the stack workflow, while Status Panel helps observe and act on the running system.
How to try Status Panel
If you want to try Status Panel yourself, the quickest path is the install script.
curl -sSfL https://raw.githubusercontent.com/trydirect/status/master/install.sh | shGitHub repository and installation steps
If you prefer Docker, you can also pull the image directly:
docker pull trydirect/status:latestWhat Status Panel does
- reports container and app health
- retrieves logs for targeted troubleshooting
- shows server metrics such as CPU, memory, and disk usage
- supports restart and other validated operational actions
- runs as a CLI tool, daemon, API server, or API plus UI
Why it matters
Many teams can deploy a stack. The harder problem starts later: understanding what failed, which service needs attention, and how to respond without turning every incident into an SSH-only exercise.
That is where Status Panel becomes valuable. It shortens the distance between “something is wrong” and “we know which component is wrong.”
How it fits into TryDirect and Stacker
For more technical users, Status Panel works alongside Stacker as the runtime side of the stack workflow.
- Stacker helps define, deploy, and update the stack
- Status Panel runs on the target server and executes runtime actions
- together they reduce dependence on ad hoc shell access for routine operations
Who should read the source?
If you want a deeper technical understanding, the official GitHub repository is the best place to inspect the current code, README, install flow, and supported command surface.
Good next reads
If you want the practical operator flow, read the live stack debugging guide. If you want the narrower runtime definition, read the Status Panel Agent explainer too.