How to Use Claude Code on Bluehost VPS

Disclosure: This post contains affiliate links. If you sign up for Bluehost through one, we may earn a commission at no extra cost to you.

Close your laptop mid-task, and Claude Code’s progress goes with it — the refactor it was halfway through, the test it just kicked off, all of it interrupted the second your machine sleeps. That’s the exact frustration that pushes developers toward running Claude Code on Bluehost VPS instead of a local machine.

A persistent, always-on server keeps the session alive through reboots, sleep mode, and everything else that kills a local terminal loop.

In this guide, you’ll walk through picking the right VPS plan, connecting over SSH, installing Claude Code, and getting your Anthropic API key configured — a setup you can realistically finish in well under an hour once the VPS is provisioned.

All you need going in is an active Bluehost VPS and basic terminal comfort; no prior sysadmin background required. There’s also a security step most tutorials skip entirely, and it’s the one that matters most once Claude Code has root access to a live server.

Can I Run Claude Code on a Bluehost VPS?

Yes. Claude Code is a terminal-based coding agent built by Anthropic, and it runs on any Linux, macOS, or Windows machine that meets its system requirements — a Bluehost self-managed VPS running a supported Linux distribution qualifies.

Because a self-managed VPS gives you full root access, you can install Claude Code exactly the way Anthropic’s documentation describes for a standard Linux server, without any of the restrictions you’d hit on shared hosting.

The main practical difference from running it locally is that the session lives on the server instead of your laptop, so it keeps running after you disconnect — which is the whole point of putting it on a VPS in the first place.

What You Need Before Installing Claude Code on Bluehost VPS

Before you start, make sure you have:

• A Bluehost self-managed VPS plan with root SSH access (included by default on all Bluehost VPS and dedicated plans)
• An SSH client — Terminal on macOS/Linux, or PuTTY/Windows Terminal on Windows
• An Anthropic account with either a Claude subscription or an API key from console.anthropic.com
• Your VPS root credentials (server IP address and root password, found in your Bluehost account)
• About 15–20 minutes, most of which is waiting on install commands and DNS/SSH propagation, not active work

You do not need Node.js installed. Claude Code’s current recommended installation method is a native binary installer that has no Node.js dependency — that only matters if you deliberately choose the older npm-based install method, covered below.

How to Set Up Claude Code on Bluehost VPS

This is the core setup: pick a plan sized for the workloads you’ll run, get into the server, install Claude Code, and connect it to your Anthropic account.

Each step below assumes a fresh Bluehost self-managed VPS running Ubuntu or a similar Linux distribution.

Choose a Bluehost Self-Managed VPS Plan

1. Log in to your Bluehost account and go to the VPS hosting section.
2. Bluehost’s self-managed VPS plans are tiered by vCPU count (commonly labeled NVMe 2, NVMe 4, NVMe 8, and up), each running on AMD EPYC processors with DDR5 RAM and NVMe SSD storage.
3. At the configuration step, choose a Linux distribution (Ubuntu, Debian, or AlmaLinux are typically available) rather than an “OS with Panel” option — Claude Code doesn’t need cPanel, and skipping it keeps the server leaner.
4. Complete checkout and wait for Bluehost to provision the server; you’ll get a confirmation once it’s ready.

Exact plan names, specs, and pricing change fairly often — confirm current tiers and specs on Bluehost’s own VPS pricing page before you buy, rather than relying on any numbers quoted in this article.

Connect to Your VPS Using SSH

1. In your Bluehost account, open the Hosting section, find your VPS, and click View Details to reveal your server’s IP address.
2. If you haven’t set a root password yet, look for the Access Management (or equivalent password/credentials) section under your VPS’s hosting details and set one there.
3. Open your terminal (or PuTTY on Windows) and connect:

ssh root@your-server-ip

4. Accept the host key fingerprint prompt on first connection, then enter your root password when asked.

Common error: if the connection hangs or times out instead of prompting for a password, double-check that you’re using port 22 (the default for Bluehost VPS/dedicated servers, unlike port 2222 used on some shared hosting SSH setups) and that your local network or firewall isn’t blocking outbound SSH.

Bluehost’s exact account dashboard layout is updated periodically — verify the menu names above against your live account before publishing this as a step-by-step guide. [NEEDS: verify current Bluehost account panel labels]

Install Claude Code

Once you’re connected as root, install Claude Code using Anthropic’s native installer — no Node.js required:

curl -fsSL https://claude.ai/install.sh | bash

This downloads a self-contained binary for Linux and adds claude to your path. If you’d rather use the npm method instead — useful if you’re pinning versions for a CI setup — you’ll need Node.js 18+ installed first:

npm install -g @anthropic-ai/claude-code

Avoid running the npm install with sudo; if you hit permission errors, Anthropic’s installation troubleshooting docs cover the recommended fix rather than defaulting to sudo.

Configure Your Anthropic API Key

1. Grab your API key from console.anthropic.com if you’re authenticating with an API key rather than a Claude subscription login.
2. Run:

claude config

3. Follow the prompts to authenticate — either by logging into your Claude account or by pasting in your API key.
4. To avoid re-entering it every session, set it as an environment variable in your shell profile (~/.bashrc or ~/.zshrc):

export ANTHROPIC_API_KEY="your-key-here"

Common mistake: pasting the API key with a trailing space or newline from a copy-paste, which causes silent authentication failures. If claude reports an auth error right after setup, re-copy the key carefully and re-run claude config.

Verify That Claude Code Is Working

Confirm the install is healthy before you start working:

claude --version
which claude
claude doctor

claude doctor checks your installation type and flags common configuration issues — run it any time something feels off later, too.

At the time of writing, the current stable release is Claude Code v2.1.263; run claude --version on your own server to confirm what you actually have installed, since new versions ship frequently.

How to Access Claude Code Remotely on a Bluehost VPS

The whole reason to run Claude Code on a Bluehost VPS hosting instead of your laptop is so a session survives you closing your terminal.

SSH alone doesn’t do that — if your connection drops, whatever Claude Code was doing in that shell dies with it. Use a terminal multiplexer instead:

1. Install tmux if it isn’t already present: sudo apt install tmux (or yum install tmux on RHEL-based distros).
2. Start a named session: tmux new -s claude-session.
3. Run claude inside that session as normal.
4. Detach without killing it: press Ctrl+B, then D.
5. Reconnect from anywhere later with: ssh root@your-server-ip followed by tmux attach -t claude-session.

screen works the same way if you prefer it over tmux. Either tool is what actually makes the VPS setup “persistent” — without one, you’re just SSHing into a server and closing the same session-loss problem you had locally.

How to Use Claude Code for Development on a Bluehost VPS

Once it’s installed and authenticated, using Claude Code on a VPS works the same as using it anywhere else — you’re just doing it against a persistent, root-accessible Linux environment instead of a local machine.

Work With GitHub Repositories

1. Clone your project onto the VPS: git clone https://github.com/your-org/your-repo.git.
2. cd into the project directory and start Claude Code: claude.
3. Ask Claude Code to explore the repo, make changes, or open a pull request — it reads files, edits them, and runs shell commands directly in that working directory.
4. Commit and push as you normally would with Git once changes look right.

Keep your Git credentials (SSH key or a scoped personal access token) configured on the server the same way you would on any dev machine.

Run Tests, Builds, and Debugging Tasks

Because the VPS has full root access and persistent storage, Claude Code can install project dependencies, run your test suite, and iterate on failures in the same read-edit-run-verify loop it uses locally — but without your laptop’s RAM or battery being a factor.

This is the pattern that suits small-to-mid-sized projects best: a bug fix, a refactor, or a build failure where Claude Code needs to make a change, run a command, check the output, and adjust — repeatedly, without you babysitting every step.

Automate Long-Running Development Tasks

Combine the tmux setup above with a task you’d normally have to leave your laptop running for — a large refactor across many files, a long test suite, or an overnight dependency upgrade.

Start Claude Code inside a detached tmux session, hand it the task, and check back later rather than watching it work in real time. The VPS keeps running whether or not you’re connected, which is the main practical advantage over a local machine for this kind of task.

How to Secure Claude Code on a Bluehost VPS

Running an AI agent with root shell access on a public-facing server is worth locking down properly:

• Use SSH key authentication instead of a password, and disable password-based root login once your key is set up.
• Enable a firewall (ufw on Ubuntu) and only open the ports you actually need — SSH, and whatever else your project requires.
• Never hardcode your Anthropic API key in scripts or commit it to a repo; keep it in an environment variable or a .env file excluded via .gitignore.
• Create a non-root user for day-to-day work where practical, and reserve root access for tasks that genuinely need it.
• Keep the system updated (sudo apt update && sudo apt upgrade) so you’re not running Claude Code on a server with known unpatched vulnerabilities.

Bluehost VPS plans include network-level protections like a built-in firewall and DDoS mitigation, but those don’t replace the server-level hardening above — they operate at a different layer.

Which Bluehost VPS Plan Is Best for Claude Code?

Claude Code itself is lightweight — it’s a CLI tool, not a resource-hungry service — so the plan you need depends more on what your projects require (build tools, databases, containers) than on Claude Code specifically.

[NEEDS: current plan names, vCPU/RAM/storage specs, and pricing verified against Bluehost's live VPS pricing page before publishing]

As a rule of thumb: if your local machine currently handles the project comfortably, an entry- or mid-tier self-managed VPS will typically handle the same workload with Claude Code added on top, since Claude Code’s own footprint is small relative to a full dev toolchain.

Claude Code on Bluehost VPS: Pros and Cons

Pros

• Sessions persist through laptop sleep, restarts, and disconnects
• Full root access means no permission restrictions during install or use
• NVMe storage and dedicated resources keep file operations and dependency installs fast
• One consistent environment if multiple people or machines need to pick up the same project

Cons

• You’re responsible for security hardening yourself (self-managed means no one else patches it for you)
• Ongoing hosting cost, versus $0 marginal cost of running it on hardware you already own

Conclusion

Getting Claude Code running on a Bluehost VPS comes down to five things: picking a self-managed plan with root access, connecting over SSH, installing the native binary, authenticating with your Anthropic account, and wrapping the session in tmux or screen so it survives disconnects.

Once that’s done, you’ve solved the core problem that sends most people looking for this setup in the first place — a coding session that keeps running whether or not your laptop is open. From there, securing the server properly is the step that protects everything else you build on top of it.

Frequently Asked Questions