VPS and Termux

Run the company process from a dedicated server.

A VPS gives Drax persistence. Termux gives you mobile access. Together they make the agentic company reachable from any device without moving the operating floor.

Server baseline

Start with a Linux VPS you control. Keep SSH key-based access, a non-root user, updates, firewall rules, and a clear project directory.

Use a named SSH alias so you do not paste credentials into docs or prompts.
Keep repositories under a predictable path such as `~/work/`.
Run agent sessions inside `tmux` or another persistent terminal manager.
Back up artifacts before destructive infrastructure changes.

# VPS shell
sudo apt update
sudo apt install -y git curl tmux nodejs npm
mkdir -p ~/work
cd ~/work

# Keep long-running sessions recoverable
tmux new -s linort

Termux access

Use Termux as the mobile control surface. The server does the work; the phone only opens the tunnel and terminal.

# Android Termux
pkg update
pkg install openssh -y

# Replace linort-vps with your SSH alias.
ssh linort-vps

# Local preview tunnel for a site running on the VPS at port 4321.
ssh -N -L 4321:127.0.0.1:4321 linort-vps
termux-open-url http://127.0.0.1:4321

Operating rule

Do not put secrets, private keys, or production credentials into prompts. Reference connection names, keep approvals explicit, and let the server hold the long-running company process.

Your phone is the cockpit. The VPS is the company floor.

Install Drax