A terminal in your browser that never closes on its own
Each terminal is a tmux session living inside your VPS, not in the browser. If your internet drops, you close the tab or your laptop dies, the process that was running is still there and you reattach exactly where you left off. That's the difference between a web SSH client and a real terminal: nothing closes it on its own, only you do.
- Persistent sessions
- Named tabs
- Nothing to install
See plans · Create a free account
Here's what it looks like in the panel
SSH without a client, and without the fear of losing work
For that long build, that migration or that log you want to keep an eye on.
- Persistent for real: The session lives on the VPS, not in the tab. It survives connection drops, closing the browser, backend restarts and agent updates.
- Come back whenever: Reattach to the same session as many times as you want, from another computer or from your phone. The scrollback is still there.
- Named tabs: Up to 5 terminals per user per VPS, each with its own name: one for logs, one for the database, one for the deploy.
- Pick the Linux user: Administrators choose which user the terminal opens as, root included. Everyone gets in with the permissions that belong to them.
- Reboot notice: tmux doesn't survive a VPS reboot. If one takes a terminal with it, the panel tells you instead of letting you believe the process is still running.
- Comfortable to use: bash with a colored prompt, Tab completion, history, and copy and paste with the mouse like on any web page.
- Private per member: Each Company member sees only their own terminals. The administrator sees all of the VPS's.
- Nothing to install: No SSH client, no key to generate, no PuTTY to configure. You open it from the panel and it works the same on Windows, macOS, Linux or a tablet.
- It doesn't replace classic SSH: Root access over SSH is still there and untouched. The web terminal is a shortcut, not a substitute and not a cage.
- It gets logged: Opening a terminal goes into the VPS history: who opened it, as which user and when.
How to open one
- Open the VPS in the panel: And go to the terminal tab. Nothing to install and no key to generate.
- Create a terminal: You give it a name and pick the Linux user. If you're an administrator you can open it directly as root.
- Work as usual: It's a real bash inside your VPS: apt, docker, psql, journalctl, whatever you need. Copy and paste work with the mouse.
- Leave something running and close it: A long build, a migration, a tail -f. You can close the browser: the process keeps going.
- Come back and reattach: Open the same terminal and pick up where you were, with the output produced while you were away.
How it works underneath, and what it doesn't do
- Each terminal is a tmux session inside the VPS. What persists is that session, not an open connection: that's why it survives your network or your browser going down.
- The panel connects over WebSocket to the VPS agent, which bridges to tmux. There's no SSH client in the browser and no private key traveling.
- It needs systemd running inside the VPS and a Debian or Ubuntu base. It's verified in production on Ubuntu 22.04 and compatible with 18.04, 20.04, 24.04 and 26.04.
- It doesn't work on Ubuntu 16.04, and that isn't something we're going to fix: systemd 229 won't start on a host running cgroup v2 — which is how every parent host is set up — and it sits there as PID 1 without answering. It's Ubuntu bug LP #1962332.
- A maximum of 5 terminals per user per VPS. The limit is there so a forgotten tab doesn't leave processes hanging around eating the plan's memory.
- Company members are pinned to their own Linux user. Choosing the user, root included, is for administrators.
- Rebooting the VPS ends every tmux session. If you had something long running, it's lost: for that, leave it as a systemd service or a scheduled task.
- It doesn't replace SSH access: root over SSH is still available and works exactly the same, with your usual client.
- Copy and paste use the browser clipboard, so they depend on the permissions you give the site. Some browsers ask you to allow it the first time.
- Real root over SSH: the panel is a shortcut, not a cage. Anything it does with a button, you can also do by hand.
Or just ask Claude, ChatGPT or Cursor
Everything you see in the panel, your AI agent can do through the ArduMaker MCP server: with your authorization, within the scope you grant, and with every action audited. See what the MCP does
Frequently asked questions
If I close the browser, do I lose what was running?
No. The tmux session lives inside the VPS, not in the tab: the process keeps running, and when you come back you reattach with all the output produced while you were away.
Do I need to install an SSH client or generate a key?
No. You open it from the panel and it works the same on Windows, macOS, Linux or a tablet. If you'd rather use your usual client, root access over SSH is still there and untouched.
How is it different from ttyd or Wetty?
The session is persistent by design. Web terminals that put a shell straight on the connection die with it: if the network drops, so does the process. Here each terminal is a tmux session inside the VPS, so the connection can go down without taking the work with it.
What happens if I reboot the VPS?
Every session ends, because tmux doesn't survive a reboot. The panel tells you when it happened instead of letting you believe your process is still alive. For things that have to survive reboots, leave them as a systemd service.
How many terminals can I have open?
Up to 5 per user per VPS, each with its own name. The limit exists so a forgotten tab doesn't leave processes eating the plan's memory.
Can I open a terminal as root?
Yes, if you're a Company administrator. Members are pinned to their own Linux user, which is what makes the permissions mean something.
Can other team members see my terminals?
No. Each member sees only their own. The VPS administrator sees all of them, and opening one is recorded in the history with who it was, as which user and when.
Does it work on any Ubuntu version?
It's verified in production on Ubuntu 22.04 and compatible with 18.04, 20.04, 24.04 and 26.04. Not on 16.04: systemd 229 won't start on a host running cgroup v2 and sits there as PID 1 without answering (Ubuntu bug LP #1962332).
Can I copy and paste with the mouse?
Yes, like on any web page. It uses the browser clipboard, so it may ask you for permission the first time.
Is it safe to leave it open?
The connection goes over WebSocket on HTTPS to the VPS agent: there's no private key traveling and no extra SSH port open to the internet. Access depends on your panel session and your role in the Company.
Services that go well together
- Services and scheduled tasks: Create systemd services for your app and cron-style scheduled tasks with logs, without writing systemctl.
- GitHub deploys: Link a repo and every push to your chosen branch updates your app on the VPS, with build and restart scripts.
- Docker: Enable Docker in one click and manage images, containers, logs, volumes and networks from the panel.
Your server, from any browser The web terminal comes with every VPS, with nothing to configure. See plans