Investigate. Don't waste time searching.
Your service isn't responding. You need logs, metrics and the right SSH connection — not another hunt through terminal history. Open your saved workspace and start investigating.
HostAxe TerminalYour terminal. Your servers. Your automation.Same commands. Different servers. Again and again. Why keep doing work you've already done? Turn repetitive operations into reusable scenarios. Keep your SSH connections, scripts and essential tools together — and focus on the problems that actually need your attention.SSH, local terminals and reusable commands in one workspace.

Your service isn't responding. You need logs, metrics and the right SSH connection — not another hunt through terminal history. Open your saved workspace and start investigating.
Unusual traffic? Repeated login failures? Open the relevant logs and run your prepared checks. Follow a consistent investigation process instead of rebuilding it every time.
When a deployment fails, the last thing you need is to remember every recovery command. Keep your rollback plan ready, verify each step and focus on making the right decisions.
Save the commands you already trust as one scenario. When production breaks again, open your checks and logs in one call. Focus on the cause.

ssh productioncd /srv/apidocker compose psdocker compose logs --tail=40 apidocker compose logs --tail=40 nginxFind the host, remember the path and type the checks again.
@inspect productionYour saved profile, path and commands open together in three terminal views.
@inspect productionRun the example to see the result
Run the example to see the result
Run the example to see the result
Illustrative output. No real server is connected.
Save this function in HostAxe, create your production SSH profile, and adapt /srv/api to your project. It opens read-only diagnostic views; it does not fix the server for you.
@inspect(server:text) = {
$$opennewtab id=services ssh=${server} {
cd /srv/api;
docker compose ps;
}
$$splittab id=api_logs ssh=${server} {
cd /srv/api;
docker compose logs --tail=40 api;
}
$$splittab id=web_logs ssh=${server} {
cd /srv/api;
docker compose logs --tail=40 nginx;
}
}Stop reconnecting, arranging terminal windows and typing the same checks. Combine your aliases with HostAxe terminal functions to launch a complete debugging or monitoring workspace in one call.

ssh production # terminal 1cd /srv/api && docker compose psssh production # terminal 2cd /srv/api && docker compose logs --tail=30 apissh production # terminal 3uptime && free -hOpen three sessions, connect each one, arrange the panes and enter every command yourself.
@debugWorkspace productionOne saved call opens the SSH sessions, splits the layout and runs your commands in separate panes.
@debugWorkspace productionRun the example to see the result
Run the example to see the result
Run the example to see the result
Illustrative output. No real server is connected.
Define this workspace scenario in HostAxe and use your SSH profile. Change the paths and read-only checks to match your infrastructure. The example demonstrates the layout, not a live connection.
@debugWorkspace(server:text) = {
$$opennewtab id=services ssh=${server} {
cd /srv/api;
docker compose ps;
}
$$splittab id=logs ssh=${server} {
cd /srv/api;
docker compose logs --tail=30 api;
}
$$splittab id=load ssh=${server} {
uptime;
free -h;
}
}You don't need to abandon the commands you already know. Keep using your shell, bring your SSH connections together and turn the operations you repeat into reusable workflows.
less switchingKeep SSH connections, split terminals, server metrics and essential utilities in one working environment.
your commands stay yoursUse your normal system shell locally and SSH remotely. Ordinary commands still work the way you expect.
automate the routineSave commands as aliases, combine them into scenarios and reuse them when the same task comes back.

Explore connections, scenarios and workspace settings. This interactive preview uses sample data.
Ubuntu 24.04 LTS · 192.0.2.10
ops@production /srv/app
$ systemctl status nginx
● nginx.service · active (running)
Main PID: 1842 (nginx)
Memory: 8.2M · Tasks: 3
Started nginx.service.
ops@production ~
$
~/workspace
you@local ~/hostaxe
$ git status --short
✓ working tree clean
$ npm run build
✓ build completed in 1.4s
you@local ~
$
Production, staging, another SSH session, another log. Sound familiar? Keep local terminals, SSH connections and server output side by side. Switch between hosts without rebuilding your workspace every time.
Inspect a service in one pane while checking its configuration in another. Keep the information you need visible.
@watchLogs() = {
$$splittab id=logs {
docker compose logs -f;
}
}@watchLogsStop rewriting the same command for different files. Save a function, pass the path and run it again whenever you need it.
@safeRights(file:path) = {
chmod 600 ${file};
}@safeRights ./config.envNeed one operation to finish before another begins? Define the sequence, wait for the result and get notified when the task completes.
@checkService() = {
$$splittab id=check {
systemctl is-active nginx;
}
$$join id=check timeout=30s;
$$notify message="Checked";
}@checkServicePorts, paths, recovery instructions and server-specific details. Keep them in encrypted local notes instead of searching old messages or terminal history. Try editing the example below.
API: 127.0.0.1:8000 .env: /srv/api/.env Recovery: /srv/api/releases/previous Health: /health
Before reload: nginx -t. After: check /health.
Generate a password for your next service. When needed, export it using AES-128/256-GCM encryption. No need to leave your terminal workflow for another utility.
Demo!7nK2@pQ8mL4xThese are demonstration values. Do not use them as real secrets.
Check your desktop environment and remote server requirements before installing. Your local computer and SSH hosts have different requirements.
Microsoft Edge WebView2 Runtime is required. If it is missing, the installer offers to download it using an internet connection. Your standard Windows account permissions apply.
Requires a graphical desktop with GTK 3, WebKitGTK 4.1, glibc 2.35+ and an unlocked Secret Service keyring over session D-Bus. Use your package manager to install the .deb and resolve dependencies. XWayland is recommended when running Wayland.
Works with Bash 4.4+, including Bash 5.0 on Ubuntu 20.04. No upgrade to Bash 5.1 is required. Shell integration uses base64 and stty inside the current session without modifying server profiles. Managed input and aliases do not currently support other shells.
File transfers require the relevant server utilities. SFTP needs an enabled SFTP subsystem. SCP needs the scp utility and standard Unix tools. Both use a saved SSH profile with host-key verification. Initial license activation and updates require an internet connection.
Install HostAxe, connect your servers and turn one repetitive task into your first reusable scenario. You have 7 days to see how much manual work you can leave behind.
Will HostAxe work with your setup?
NIST SP 800-207/53 SSDF practices guide threat analysis, code and dependency checks, security regression tests and controlled releases.

OWASP guidance shapes sensitive-data handling, input validation and safeguards against injection in application-managed operations.
We map access controls, secret handling and desktop isolation to specific published practices—not a blanket certification claim.
Zero Trust principles inform request authorization; access-control and at-rest protection guidance supports native checks and protected local storage.
Guidance for handling credentials, validating inputs and reducing command or argument injection within the application—not blocking commands you intentionally run.
WebView capabilities, scoped permissions and Content Security Policy help limit what the interface can access or execute.
Workspace and saved secrets use protection tied to your OS account.
Verify host fingerprints before connecting to unfamiliar servers.
Core operations check access; PIN locking guards the workspace.
Signed update information and integrity checks help reject altered packages.
Checking available versions…
Found a problem, need compatibility help or have an idea for a workflow? Talk directly to the Roxensoft developer. Real engineering problems help shape HostAxe.
When reporting an issue, include your HostAxe version, operating system and shell version. Remove passwords, private keys and other sensitive information from screenshots and logs.