Hosting·3 min read

Jailshell or admin rights: what Claude can and can't do on your hosting

The difference between hosting in a jail and your own server with admin rights: what Claude may do in each case, and why that difference matters so much.

Claude can work on our servers in two ways: as a user in a jail on shared web hosting, or with admin rights on your own server. A jailshell is an isolated environment that only shows your account: your files, your databases, your email, within your plan's memory and CPU limits, with no view of other customers or the server itself. With admin rights Claude works as the DirectAdmin administrator on a Claude Server and switches per site to that site's user through sudo, never as root: creating accounts, managing DNS and mailboxes and investigating outages across all sites then becomes possible. The difference sounds like a detail, but it determines what's possible, and how big the consequences of a mistake are.

What is a jail? Your account, nothing else

On shared web hosting your terminal runs in a jailshell. Technically that's an isolated environment that only shows a small part of the server:

  • your own home directory (your websites, email, files),
  • the programs in /usr (read-only): PHP, WP-CLI, Composer, Git, Node, Python,
  • a few settings needed to be able to work.

Other customers, system files and the server's log files simply don't exist inside the jail.

What Claude can do here: everything within your own account. Edit files, update WordPress, edit your sites' databases, make or restore a backup, connect a repository.

What it can't: root, sudo, installing software on the server, seeing other accounts, changing server settings. DNS, mailboxes and the PHP version per domain also go through the DirectAdmin panel.

Claude runs within your plan's limits (memory, processes, CPU). A heavy task affects your account, not someone else's.

What do admin rights mean? The whole server

On a Claude Server (your own VPS or dedicated server) Claude works as the DirectAdmin admin. That's a different level:

  • creating, suspending and removing accounts, with plans and limits,
  • managing every website on the server, via sudo to the right user per site (never as root on the sites themselves),
  • DNS for every domain, email for every account,
  • server-wide diagnosis: why is the server slow, which site uses the most resources,
  • migrations of dozens of sites at once.

We run this in production for a client with over 160 websites on one dedicated server. A single sentence like "launch client-x.com as a new site" means: create the account, DNS, SSL and deploy the code.

Why that difference is so big

Web hosting (jail) Claude Server (admin)
Scope one hosting account the whole server
Other accounts invisible manageable
Create accounts no yes
DNS and email via the panel, Claude explains Claude handles it
Root no no, but sudo per site
Impact of a mistake your account every site on the server
Fits one or a few websites many sites, agencies, your own server

More power also means more responsibility. That's why the safety nets on a server are stricter: suspend instead of delete, a backup before every drastic action, and a log of every action.

Which one fits you?

  • One or a few websites, no server management: web hosting with Claude. Safely isolated, and you don't pay for a server.
  • Many sites, clients of your own, or you want Claude to handle accounts, DNS and email too: a Claude Server.

Not sure? Read Web hosting or server? or get in touch.

MK
Maarten Keizer

Founder of Invoker. Over twenty years in hosting, system administration and web development; builds the Claude hosting himself and tests everything on our own servers first.

about maarten