No. Command generation is plain JavaScript in your browser. Hostnames, IPs, paths and ports never leave your machine.
Stop hand-writing error-prone commands. Pick a task, fill in a few fields, and get exact copy-paste commands for SSH keys & tunnels, rsync transfers, cron jobs, vhosts, systemd units, fail2ban jails, UFW rules and OpenSSL inspection — built entirely in your browser.
Most server mistakes happen in the 30 seconds before you press Enter: a mistyped rsync path that wipes a directory, a cron schedule that fires every minute, an SSH tunnel with the wrong port order. The Linux Command Builder generates the command for you from a short form, so typos never reach your shell.
Every command is produced by JavaScript in your browser — hostnames, IPs and paths you type are never sent to any server.
Choose from seven tabs: SSH, file transfer, cron, vhosts, systemd, firewall & fail2ban, and OpenSSL inspection.
Hostnames, ports, paths and options. Sensible production defaults are pre-selected.
Ready-to-paste commands with the exact flags, quoting and port order the man page demands.
Review once, paste into your terminal. Nothing is uploaded, logged or stored anywhere.
Cron expression: 30 2 * * *
This tab generates inspection commands only — we never generate private keys here. To create a CSR or decode a certificate, use the SSL Checker / Decoder / CSR Generator.
Everything above runs in JavaScript in your browser. Hostnames, IPs, paths and ports you enter are never uploaded — making this safe to use against production infrastructure.
| Tab | Covers | Typical use |
|---|---|---|
| SSH | ssh-keygen, ~/.ssh/config blocks, local & remote forwards, SOCKS5 proxy | Key rollout, jump access, tunnelling a database or admin UI |
| rsync / scp / tar | Push & pull transfers with dry-run, --delete, compression, progress; portable tar archives | Deployments, migrations, backups |
| cron | Schedule builder with live expression preview and install commands | Backups, renewals, maintenance scripts |
| Nginx / Apache | Production vhost: www redirect, gzip, caching, PHP-FPM, SSL + HTTP→HTTPS redirect | New site bring-up, config review |
| systemd | Hardened unit file + enable/start/log commands | Running your app as a proper service |
| UFW / fail2ban | Safe initial firewall, port rules, IP denies, fail2ban SSH jails | Locking down a fresh VPS |
| OpenSSL | Cert/CSR/key inspection, live chain checks, match verification | TLS troubleshooting (no key generation) |
No. Command generation is plain JavaScript in your browser. Hostnames, IPs, paths and ports never leave your machine.
A dry-run (-n) lists what would change without touching anything. Combined with --delete it can reveal files you did not expect to lose. Always dry-run before your first real sync against production.
No — by design. Private keys should never be generated by a web page. Use the OpenSSL tab for inspection commands, and our SSL Checker / Decoder / CSR Generator for CSRs and certificate decoding.
Debian and Ubuntu primarily (apt paths, package names), but the generated commands work on any systemd-based Linux. Package-install lines note the RHEL/CentOS equivalents where they differ.
The cron tab outputs a one-liner you can run manually, plus grep CRON /var/log/syslog to confirm the job fired. Set a short interval, verify, then switch to the real schedule.
Default deny incoming, allow outgoing, permit SSH (rate-limited), 80 and 443 — which is exactly what the "Initial UFW setup" task generates. Then add fail2ban for SSH to stop brute-force attempts automatically.