Manage Your Servers
Without Leaving DeployHQ
Run an ad-hoc command, schedule a cron job, or open an in-browser console — straight from the project that owns the server. No local SSH client, no copy-pasting credentials, no separate console tab.
Last updated on 29th May 2026
Server Management is a project-level surface that lets you operate the servers you've already connected to DeployHQ. Run a quick command, schedule recurring jobs, and open a full interactive console — all backed by the same credentials your deployments already use. No new connection strings, no separate access path to audit.
Three Things, One Place
Everything you'd otherwise reach for an SSH client or cron config for.
Ad-Hoc Commands
Run one-shot commands across one server, several, or a whole group. Output streams back to your browser with stdout, stderr, and exit code captured for the audit log.
Scheduled Cron Jobs
Add and edit cron entries through the UI. DeployHQ writes the crontab on the server, keeps history of every run, and shows you when jobs last succeeded or failed.
In-Browser Console
An interactive terminal in your browser, attached to the server through the same authenticated path your deploys use. Useful when "let me just SSH in real quick" turns into half an hour of debugging.
Why It's In DeployHQ Specifically
The project that knows your servers is the right place to operate them.
No SSH Client Setup
Onboarding a new engineer means adding them to the project. They get console and command access without an SSH key handoff or a VPN tunnel walk-through.
One Audit Trail
Every command and every console session is tied to a user account and a project. Operations and deploys end up in the same activity feed instead of two disconnected logs.
Works on Servers You Already Have
Any SSH-reachable server you've added to DeployHQ works — your VPS, a managed host, an instance behind the Network Agent, or a Managed VPS provisioned through DeployHQ.
Schedule Without Touching the Crontab
Add, edit, pause, and remove cron entries from the dashboard instead of editing crontab files in vim across half a dozen boxes.
When It Pays Off
Common moments where the dashboard saves the SSH session.
After-deploy housekeeping
Run migrations, clear caches, or warm a queue — without provisioning long-lived SSH access to the engineer who needs to do it once.
Scheduled maintenance
Nightly backups, log rotation, queue draining. Define them as cron entries in DeployHQ and version the schedule alongside the project that depends on them.
On-call debugging
When a deploy looks healthy but the app isn't, open the console and check the running process — without firing up a separate terminal and digging out the right key.
Enable Server Management
Turn beta features on
Server Management is currently in beta. Toggle beta features on in your account to see it appear in the project sidebar.
Open Server Management on your project
Pick the project whose server you want to act on, open the new Server Management section, and pick Commands, Cron, or Console.
Run, schedule, or attach
Run an ad-hoc command, add a cron entry, or attach the in-browser console. Output and history land in the same project feed alongside your deploys.
Frequently Asked Questions
Which servers does this work on?
Any SSH-reachable server you've already added to the project — your own VPS or shared host, instances behind the DeployHQ Network Agent, or Managed VPS provisioned through DeployHQ. There is no separate connection to configure.
Is there an audit log?
Yes. Every command, console session, and cron run is recorded against the user who initiated it (or the schedule that triggered it). The history shows up alongside the deployment history for the same project.
Can my whole team use this?
Access is governed by the same project-level permissions you use for deployments. Add team members to the project with the right role and they get the same Server Management capabilities — no separate SSH onboarding.
How is the in-browser console different from SSH?
Functionally it is an interactive terminal — the same shell experience you would get from ssh. The difference is the access path: the session is authenticated through DeployHQ using the project's existing credentials, with the activity recorded against your user.
How do I enable Server Management?
It is currently in beta. Enable beta features on your account, and a 'Server Management' entry appears in the project sidebar.
Operate the servers you deploy to
Run a command, schedule a job, open a console — from the project that already knows the server.
10-day free trial • No setup fees • Cancel anytime
Explore More Features
Discover all the tools that make DeployHQ the easiest way to deploy your code.
Zero Downtime Deployments
→One-Click Rollback
→Turbo Deployments
→Build Pipelines
→Docker Builds
→Deployment Checks
→Deployment Targets
→Automatic Deployment
→Deployment Templates
→Deploy Behind Firewalls
→SSH Deployment
→Deployment Zones
→Team & Permissions
→Single Sign-On
→Custom Actions
→Server Management
→Static Sites & S3
→CLI & Agents
→Powerful Integrations
→Get started today for just $9/month
That's unlimited deployments and 3 projects.