Security
Your Claude account
Claude Code runs on your computer and talks to Anthropic directly. Your Claude login, conversations and subscription never pass through LoadShift. Machines only receive the shell commands Claude runs.
Isolation
- Each machine is a full virtual machine with its own kernel (KVM with Cloud Hypervisor), not a container.
- Machines sit on an isolated network bridge. They can reach the internet but not each other, the server itself, or private address ranges.
- Each machine has its own resource limits, so one can't starve the others.
Access
- SSH accepts only the owner's keys. sshd asks LoadShift for them on every login, so a key you remove in the dashboard stops working immediately, even on a running machine. Passwords and root login are disabled.
- Each machine reports its SSH host keys when it first boots, and loadshift pins them when it connects, so there's no trust-on-first-use prompt for an attacker to exploit.
- File sharing and forwarded ports travel inside your SSH connection. Nothing besides SSH is exposed on the internet.
Tokens
- API, machine and server tokens are stored only as SHA-256 hashes. They have recognisable prefixes (
ls_, oroff_for older API tokens,oma_,ohs_) so secret scanners can catch leaks. - CLI sign-in uses a one-time browser confirmation; the token is handed to the terminal once and never shown in the browser.
- Every sensitive action is written to an audit log.
What we can see
We run the servers, so we have the technical ability to access VM disks, as with any cloud provider. We don't look without your request or a legal obligation.
Reporting a vulnerability
Email security@loadshift.ai. We reply within two working days.