About Tiller
Hand-on tools for hand-on operators.
Tiller began as a private tool. The original problem was simple — keeping a handful of small VPSes running for a logistics company in Tbilisi, on a flaky train Wi-Fi, while juggling SSH terminals, file managers, and a Telegram bot's logs. Three browser tabs became six. Six became "where did I put that command?" And one too many lost contexts later, the answer became: build the workspace I actually want.
What we believe
Web is the right surface for SSH
Browsers are universal. They survive laptop reboots, work on a phone in a pinch, share state through a single login, and don't make you re-configure your local machine for every box. The terminal is the right metaphor. The browser is the right runtime.
Default to "no agent on your boxes"
Most server tools want you to install a client first. We don't. Plain SSH covers the majority of what Tiller does. The optional speed-boost agent is opt-in, ~150 lines of Node, and uninstallable in one command.
AI lives in the seat next to you
Claude, Aider, Gemini, and Ollama all run inside a tmux session on whatever server you opened them on. They see what you see. They run where you run. We don't pipe your code through anything we operate.
Where we are
Tiller is in private beta — currently used by a handful of operators around small fleets of servers (logistics, e-commerce, indie SaaS). We're polishing rough edges, adding direct-WSS for sub-50ms terminals, and building the public pricing.
If you want to be among the first ten people to use Tiller seriously, drop us a line. Tell us about your servers and what you spend most of your terminal time on — that's the most useful thing you can send.