It's a quarter past eleven at night and you're in a hotel room in Lisbon. Monitoring says your server is responding slowly. Your laptop is at home. You pick up your phone, open the Claude app, tap the session named after your server and type: "the server is slow, find out which site is causing it". Two minutes later you know that one web shop is being hammered by a crawler requesting every single cart URL, and there is a proposal waiting to block that bot. You read it, tap approve and go to sleep.
No VPN, no SSH app with a tiny keyboard, no fiddling with a password vault on a six-inch screen. One question, in plain language, to an assistant that was already waiting on your server.
That is Claude Remote Control as a service on a Claude Server. We wrote about the web hosting variant earlier in Manage your hosting from the beach. This piece is about its big brother: not one website, but your whole server.
What does Remote Control "as a service" mean?
Remote Control is a feature of Claude Code, Anthropic's assistant that works on a computer. You start Claude Code on a machine, and from then on you drive that session from your phone, your tablet or a browser. Anyone can try that at home, and you run into the limitation straight away: the session lives as long as that machine is on and the program is running. Close your laptop and your assistant is gone. Reboot the computer and you first have to sit down at a keyboard somewhere to start it again. Exactly when you need it, it isn't there.
On a server you solve that by treating Remote Control the way you treat a web server or a database: as a service. It starts when the server boots. If it falls over, it is back on its feet moments later. It survives a reboot, an update and our maintenance. You don't have to think about any of it. There is always a session ready, right where your work lives, and all you need is the device that is in your pocket anyway.
That sounds like a detail. In practice it is the difference between a neat trick and a tool you rely on.
What do you ask a session on your server?
You use a session like this in two ways, and both are worth more than you expect.
Asking questions. A server knows everything about itself, you just need to know where to look. The assistant knows, and it is standing right next to it. Questions that change nothing are answered straight away, with nothing for you to approve.
- "How full is the disk, and who uses the most?"
- "Did this afternoon's email from the bakery reach their accountant?"
- "Which certificates expire this month?"
- "Which sites still run an old PHP version?"
- "What happened at three last night? The site was unreachable for ten minutes."
That last one would cost you half an hour of scrolling through log files. Now you get an answer in plain words, with the log lines attached if you want to see them.
Changing things. On your own server, Claude works as the DirectAdmin administrator. That is a different level from web hosting, where it stays inside one account. On your server it handles accounts, DNS and email for every domain, and every site on the machine.
- "Create an account for the new client, add the domain, request a certificate, create the mailbox info@."
- "Block that crawler on the web shop and switch on caching for visitors."
- "Update WordPress on all of this agency's sites, one by one, with a backup first."
- "Roll the hairdresser's site back to last night's backup."
- "Point the new domain at the existing site and set up the redirect."
You see every change first. The assistant shows what it is about to do, you approve it on your phone, and only then does it happen.
Why does this pay off more on a server than on your laptop?
An assistant on your laptop works with a copy of reality: a folder of code, a test database, maybe a tunnel to the outside. An assistant on your server works with reality itself. The real log files, the real mail queue, the real load at this very moment. It doesn't have to guess why something is slow, it can measure it.
The second advantage is that the context stays put. The session knows your server, the sites on it and how we set up the management: how to update a plugin safely, where the backups live, how to suspend an account instead of deleting it. You don't have to explain anything. You start at the question.
The third advantage only shows after a few weeks: the threshold disappears. Things you put off because you "needed to sit down for it" now happen in the queue at the supermarket. Adding a redirect. Checking whether that one mailbox is nearly full. Answering a client with facts instead of "I'll look into it tonight".
How safe is an assistant with admin rights?
The more an assistant may do, the more the boundaries matter. These are the boundaries.
- Never root on your sites. Claude works as the DirectAdmin administrator and switches to the site's own user for each site. A mistake in one site can't leak into another. We explain the difference between the two levels here.
- Every change needs your approval. Reading and investigating just happens. Anything that changes something first shows up on your screen as a proposal.
- Reversible by default. An account gets suspended, not deleted. A backup comes before every big action. Everything that happens is logged, and you can read it back.
- No open doors. The session connects outward by itself, the same way the Claude app on your phone does. No port is opened and no extra login is added. Anyone who isn't signed in to your Claude account doesn't see the session.
- Your own subscription, your own conversations. The session runs on the Claude subscription you link. If you work as a team, each team member has their own Claude account and their own environment on the same server.
- One switch. You can turn it off at any moment. The service stops, and stays off until you turn it back on.
It is a single-tenant server: there are no neighbours. What the assistant can see is yours.
This is how we work ourselves
This isn't a product we dreamed up. Since June, our own work server has been running exactly this kind of session as a service: always on, starts with the server, comes back by itself after a reboot. A large part of our daily operations now starts as a message from a phone. Investigating an outage from the back seat. Keeping an eye on a migration during dinner. Checking whether this afternoon's fix is still holding, without opening the laptop.
What we learned from that is built into the service you get. That the session has to heal itself, because otherwise you're without it at exactly the wrong moment. That approving on a phone only works when the proposal is short and readable. And that the assistant has to know how the server is set up, because you don't feel like explaining that on the go.
Where the limits are
- Big builds belong on a big screen. Having a complete site built from your phone works, but it is nicer with the preview next to it. That is what the assistant in DirectAdmin is for.
- Approving means reading. At server level a yes has more consequences than inside a single website. The approval card exists to be read.
- Claude only. Remote Control is a Claude feature. With Codex you work through the assistant in DirectAdmin.
- Sometimes the session hangs. If Remote Control says Ready but shows Capacity 0/32, a file points to a session that no longer exists. Here is the fix.
- Not a bare VPS. A Claude Server is a managed server: we take care of updates, security, monitoring and backups. If you want an empty machine to set up yourself, this isn't your product.
What does it cost and how do you start?
Remote Control comes standard on every Claude Server: Solo from €99 per month, Multi from €199, Dedicated from €399, excluding VAT. You also need your own Claude subscription with Anthropic.
- Link your Claude subscription in Invoker Link, in DirectAdmin.
- Switch on Remote Control. The guide is in the knowledge base.
- Open the Claude app on your phone. Your session is in the list. Type your first question.
Start with something harmless, like "how is the server doing?". The answer tells you more than the dashboard you've been staring at for years. Everything about Remote Control is here, and the servers are here.