Roxensoft
HostAxe TerminalYour terminal. Your servers. Your automation.

Still typing every command manually?across all your servers?

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.

HostAxe Terminal combines SSH connections, reusable workflows and server tools in one workspace
PRODUCTION IS DOWN

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.

SOMETHING LOOKS SUSPICIOUS

Your security checks shouldn't start from memory.

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.

THE RELEASE WENT WRONG

This is why you prepared a rollback.

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.

YOUR OWN TOOLKIT. READY TO RUN.

Stop setting up the same investigation.

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.

HostAxe custom commands and arguments editor
Build your own commands and workflows
What you usually type5 commands to enter
  1. ssh production
  2. cd /srv/api
  3. docker compose ps
  4. docker compose logs --tail=40 api
  5. docker compose logs --tail=40 nginx

Find the host, remember the path and type the checks again.

With HostAxeOne saved call
@inspect production

Your saved profile, path and commands open together in three terminal views.

HostAxeInteractive preview
production@inspect production
Services

Run the example to see the result

API logs

Run the example to see the result

Nginx logs

Run the example to see the result

Interactive previewSSH · UTF-8Graphite

Illustrative output. No real server is connected.

  • 5 commands → 1 call
  • Saved paths and server profiles
  • Results side by side
See the saved scenario

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;
  }
}
ALIASES + TERMINAL AUTOMATION

One command. Your entire workspace.

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.

HostAxe prepares multiple terminal panes with one saved workflow
Prepare your working environment with one saved workflow.
What you usually type6 commands to enter
  1. ssh production # terminal 1
  2. cd /srv/api && docker compose ps
  3. ssh production # terminal 2
  4. cd /srv/api && docker compose logs --tail=30 api
  5. ssh production # terminal 3
  6. uptime && free -h

Open three sessions, connect each one, arrange the panes and enter every command yourself.

With HostAxeOne saved call
@debugWorkspace production

One saved call opens the SSH sessions, splits the layout and runs your commands in separate panes.

HostAxeInteractive preview
production@debugWorkspace production
Services

Run the example to see the result

API logs

Run the example to see the result

System load

Run the example to see the result

Interactive previewSSH · UTF-8Graphite

Illustrative output. No real server is connected.

  • Three terminal views from one call
  • SSH profiles, aliases and layout work together
  • Less setup. More time to investigate.
See the saved scenario

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;
  }
}
KEEP YOUR SHELL. LOSE THE EXTRA WORK.

Your familiar terminal. A better way to organize the work.

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 switching

Stop juggling terminal windows.

Keep SSH connections, split terminals, server metrics and essential utilities in one working environment.

your commands stay yours

No need to relearn your terminal.

Use your normal system shell locally and SSH remotely. Ordinary commands still work the way you expect.

automate the routine

Stop rebuilding the same workflow.

Save commands as aliases, combine them into scenarios and reuse them when the same task comes back.

Windows Terminal, PuTTY, Termius and Tabby each have their strengths. This comparison focuses on manual operations versus a saved HostAxe workspace. Other terminals can also be extended with scripts and plugins.
Different themes for the HostAxe Terminal workspace
Make your terminal your own
LESS SEARCHING. LESS REPETITION.

Explore connections, scenarios and workspace settings. This interactive preview uses sample data.

HostAxeInteractive preview
production · SSH

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 ~

$

systemctl daemon-reloadCommand suggestions
Local · bash

~/workspace

you@local ~/hostaxe

$ git status --short

✓ working tree clean

$ npm run build

✓ build completed in 1.4s

you@local ~

$

CPU 12%RAM 2.4 / 8 GBDISK 36%
ConnectedSSH · UTF-8Graphite
01

Five servers. One place to work.

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.

ONE LESS THING TO DO MANUALLY

You know the commands. Why keep repeating them?

Logs here. Configuration there. No switching.

Inspect a service in one pane while checking its configuration in another. Keep the information you need visible.

See the saved scenario
@watchLogs() = {
  $$splittab id=logs {
    docker compose logs -f;
  }
}
@watchLogs

Write it once. Use it with any path.

Stop rewriting the same command for different files. Save a function, pass the path and run it again whenever you need it.

See the saved scenario
@safeRights(file:path) = {
  chmod 600 ${file};
}
@safeRights ./config.env

Let the next step wait for the right moment.

Need one operation to finish before another begins? Define the sequence, wait for the result and get notified when the task completes.

See the saved scenario
@checkService() = {
  $$splittab id=check {
    systemctl is-active nginx;
  }
  $$join id=check timeout=30s;
  $$notify message="Checked";
}
@checkService
YOUR WORKING CONTEXT. ALWAYS CLOSE.

Why scatter your tools across five windows?

That port you always forget? Save it.

Ports, 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.

Server notesInteractive preview
production / api

What I need to remember

API: 127.0.0.1:8000
.env: /srv/api/.env
Recovery: /srv/api/releases/previous
Health: /health

Before reload: nginx -t. After: check /health.

Need a password? Generate it and move on.

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.

Password generatorInteractive preview
New database userDemo!7nK2@pQ8mL4xThese are demonstration values. Do not use them as real secrets.
HostAxe local security controls with PIN and encrypted vault
Local protection for your workspace
CHECK BEFORE INSTALLING

Will HostAxe work with your setup?

Check your desktop environment and remote server requirements before installing. Your local computer and SSH hosts have different requirements.

Windows desktop

Windows 10 / 11 · x64

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.

Linux desktop

Ubuntu 22.04+ / Debian 12+ · amd64

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.

Remote Linux servers

Interactive Bash 4.4+ · UTF-8 locale

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.

YOUR NEXT WORKFLOW STARTS HERE

Stop repeating yourself. Start automating.

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 logo
SECURE ENGINEERING · NIST SSDF

Secure development and release integrity with NIST

NIST SP 800-207/53 SSDF practices guide threat analysis, code and dependency checks, security regression tests and controlled releases.

OWASP logo
DATA PROTECTION · OWASP

Protecting secrets and command boundaries with OWASP

OWASP guidance shapes sensitive-data handling, input validation and safeguards against injection in application-managed operations.

ADDITIONAL SECURITY PRACTICES

Specific safeguards, grounded in established guidance

We map access controls, secret handling and desktop isolation to specific published practices—not a blanket certification claim.

Authorization and least privilege

Zero Trust principles inform request authorization; access-control and at-rest protection guidance supports native checks and protected local storage.

Secrets and injection defenses

Guidance for handling credentials, validating inputs and reducing command or argument injection within the application—not blocking commands you intentionally run.

Tauri 2 native boundaries

WebView capabilities, scoped permissions and Content Security Policy help limit what the interface can access or execute.

  • Local encrypted data

    Workspace and saved secrets use protection tied to your OS account.

  • Verified SSH hosts

    Verify host fingerprints before connecting to unfamiliar servers.

  • Native access controls

    Core operations check access; PIN locking guards the workspace.

  • Authenticated releases

    Signed update information and integrity checks help reject altered packages.

Your familiar terminal, with tools for automation. SSH profiles, passwords, notes and aliases are encrypted on your device and are not uploaded to Roxensoft.

Local tools work offline. Activation, license checks and updates need internet; SSH needs access to your server. Licensing sends device identity and app version, not workspace contents.

References describe applied engineering guidance, not certification, full standards compliance or endorsement by NIST, OWASP, MITRE or Tauri. No protection is absolute on a compromised OS; review the commands you execute. Read the Security Policy · HostAxe EULA · HostAxe Privacy · Refund and Cancellation Policy · Website Terms

Checking available versions…

Already have a license? Open HostAxe Terminal and select Activate license.Get Your License
BUILT BY DEVELOPERS. IMPROVED WITH DEVELOPERS.

Your workflow is different? Let's talk.

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.