Hivra

Claude Code on the web vs Hivra: a session or a computer?

The real choice

Claude Code on the web and Hivra can both keep Claude Code working after you close your laptop, so the difference is not whether it runs somewhere else. It is what that somewhere else is. Anthropic describes a cloud session as a Claude Code session that runs on cloud infrastructure instead of on your machine: you start it against a GitHub repository, it works, and you check on it or steer it from a browser, the Claude app or your terminal. Hivra gives the same official Claude Code command line tool a computer of its own, one you open, look around in and come back to.

That makes this less a contest between two products than a choice between two shapes of the same work. A session is a task with a repository attached, owned and run by Anthropic. A computer is a place where your files, logins, tools and history stay between tasks, and where Claude Code can sit next to other things you run. Hivra is an independent service. It is not affiliated with, sponsored by or endorsed by Anthropic, and it runs Anthropic's own Claude Code CLI, which you sign in to with your own Claude account or run on Hivra credits.

If your work is GitHub pull requests and you already pay for Claude, the session is hard to beat on simplicity, and this page says so. If you want a machine that is yours to open, or you want Claude Code beside other agents, read on.

What you are actually paying for

With Claude Code on the web you pay for a Claude subscription, not for compute. Anthropic's documentation says a cloud session counts toward your plan's usage limits alongside the rest of your Claude and Claude Code usage, and that there is no separate charge for the cloud VM. As of November 2026, Anthropic's pricing page lists Claude Pro at $20 a month billed monthly or $17 a month billed annually ($200 up front), Max at $100 a month, Ultra at $200 a month, Team seats at $20 a month on annual billing or $25 monthly for Standard and $100 annual or $125 monthly for Premium, and Enterprise at $20 a seat a month billed annually with a 20-seat minimum and usage billed at API rates on top. Anthropic says its Free level does not include Claude Code, and that cloud sessions are available on Pro, Max and Team, and for Enterprise users with premium seats or Chat + Claude Code seats.

What the subscription buys is a share of usage limits, not a fixed amount of work. Anthropic says cloud sessions share rate limits with all your other Claude and Claude Code usage, and that running several tasks in parallel uses more of the allowance in proportion. Its support pages describe a five-hour session limit and a weekly limit on Pro and Max, a weekly limit only on verified Ultra accounts, and Anthropic says it may apply additional caps at its discretion. Anthropic's pages give these as multiples of Pro rather than as numbers of messages or hours, so how much a given task costs you is something you learn by using it.

Hivra charges for the computer and leaves the model separate. $9.99 a month for 2 vCPU and 4 GB of RAM, and every computer Hivra Cloud runs needs a paid plan. A Hivra account itself costs nothing, and a free account works with a server you connect yourself. The plan does not include AI usage. Bring your own account or key where the agent supports it, or pay with Hivra credits. For Claude Code that usually means signing in with your own Claude account inside the CLI, in which case your limits follow your Anthropic account wherever the work runs. So if you already pay Anthropic, Hivra is an added computer bill on top of a model bill you already have, while Claude Code on the web adds no bill beyond the subscription.

That is the honest cost picture. If all you need is the session, the web product is the cheaper way to get it. You pay for the Hivra computer because you want the computer.

Where Hivra fits

Hivra runs the official Claude Code CLI on a computer of its own, with chat, a terminal and files as tabs you open from anywhere, and a browser tab where the computer has one. A paid Hivra Cloud computer stays on and is not paused for inactivity. Files, repositories, logins and the CLI's own session history stay on that computer between tasks, so the second task starts where the first left off rather than from a fresh checkout.

It also holds more than Claude Code. The same computer model runs the other agents Hivra supports, so Claude Code can share a machine, a filesystem and a browser with the rest of your setup. The repository does not have to be on GitHub: you bring it however you like and work in the terminal and Git tabs, and nothing about the remote is special. And because it is a computer rather than a session, you can open the terminal yourself and look at what the agent is doing.

What Hivra does not do is match Anthropic's own integrations. It has no built-in pull request watching, it does not set up the Claude GitHub App for you, and it is not part of a Claude subscription. At the entry size it is a smaller computer than Anthropic's ceilings for a session. Hivra also has a larger size, $19.99 a month for 4 vCPU and 8 GB of RAM, which is still below Anthropic's RAM ceiling.

When the alternative is worth choosing

Choose Claude Code on the web when your work is repositories on GitHub and you already have a Claude subscription that includes it. It adds no compute bill, it starts from the browser or the Claude app, and Anthropic's own integrations are there: the Claude GitHub App can watch a pull request and respond to CI failures and review comments, sessions can be grouped into projects, and the same cloud sessions back Claude in Slack. Hivra has none of that built in.

Choose it too when you need what Anthropic documents for its hosted product and Hivra does not claim: every operation in a cloud session is logged for compliance and audit, GitHub credentials stay encrypted on Anthropic's servers and never enter the VM, and Anthropic's security overview points to its Trust Center for its SOC 2 Type 2 report and ISO 27001 certificate; confirm what each covers with Anthropic. Hivra does not claim an attestation of that kind. For a team with an audit requirement, that usually decides it, subject to one check first: make sure your organization is not on Zero Data Retention, the HIPAA configuration, customer-managed keys or an IP allowlist. Anthropic says cloud sessions do not work with the first three and fail on the last unless Anthropic support exempts them.

Anthropic's sessions also run on a bigger machine than Hivra's entry size, though Hivra's larger size narrows the gap. Its cloud environments page gives approximate ceilings of 4 vCPUs, 16 GB of RAM and 30 GB of disk, which may change. And if you do not want to pay for a machine that sits there between tasks, a session that pauses when idle is a sensible way to avoid it.

Teams that want sessions in their own network can ask about Anthropic's self-hosted environments, a public beta on Team and Enterprise where repository checkouts and secrets stay on your machines but the conversation still goes to Anthropic.

At a glance

CriterionHivraAlternative
Price model
A fixed monthly computer. Every computer Hivra Cloud runs needs a paid plan
No separate compute charge. Included with Claude Pro, Max and Team plans, and Enterprise premium or Chat + Claude Code seats
Entry price
$9.99/month, 2 vCPU and 4 GB RAM, plus your Claude account or Hivra credits for the model
Claude Pro at $20/month billed monthly or $17/month billed annually
What you get
A computer of its own with chat, terminal and files to open, and a browser where the computer has one
A cloud session started against a GitHub repository, steered from browser, phone or terminal
What stays on
A paid Hivra Cloud computer stays on and is not paused for inactivity.
Pauses after a few idle minutes with files saved. The reclaim period is not stated
Persistence
Files, repos, logins and CLI session history stay on the computer
Files kept while paused. After a reclaim, conversation history returns on a fresh VM
Supported agents
Hermes, OpenClaw, Agent Zero, Claude Code, Codex, Aeon (dashboard only), DeepSeek Harness (alpha)
Claude Code only
Models and AI cost
Your own account or key where the agent supports it, or Hivra credits
Claude models, counted against your subscription's usage limits
Access method
Browser tabs for chat, terminal and files, plus a browser tab where the computer has one; Telegram on Claude Code
claude.ai/code, the Claude app, the terminal with claude --cloud, scheduled tasks
Setup effort
Launch the computer, sign in to Claude, bring your repository
Sign in, connect GitHub, choose an environment
Who maintains it
Hivra runs the computer. The CLI is Anthropic's own
Anthropic runs and manages the infrastructure
Data and security
A private computer for you. With your own Claude account, prompts go to Anthropic; no audit attestation claimed
Isolated VM, logged operations, credentials kept outside it. Retention depends on your plan
Limits
The size of the computer. Claude usage follows your Anthropic account
Shared Claude usage limits, and Anthropic may apply additional caps at its discretion. About 4 vCPUs, 16 GB RAM, 30 GB disk, subject to change
Repositories
Any, through the terminal and Git tabs
GitHub (including GitHub Enterprise Server on Team and Enterprise) for clone and pull requests. Other hosts only as a bundle, with no push back
Refund
Payments are non-refundable except where the Consumer Terms or law provide. A 14-day refund in the EEA and UK
Exit and portability
Your files are on a computer you can open and copy from
Pull a session into your terminal with --teleport; delete sessions at any time
Best for
A persistent environment, other agents, any Git host
GitHub work on an existing Claude subscription, and audit needs

Who should pick which

Priya, a backend developer on a Claude Pro subscription: Her work is pull requests against a GitHub repository, and she wants Claude Code to fix failing tests while she is away from her desk. Claude Code on the web. It adds no compute bill, and the GitHub integration is already there.

Tom, who runs Claude Code beside other agents: He wants his logins, tools, projects and session history to be there each morning, and a second agent on the same machine. A Hivra computer, which stays on and keeps them.

Dana, an engineering lead on Team seats with an audit requirement: She needs logged operations, an isolated VM per session and a vendor with published attestations. Claude Code on the web, after checking that her organization is not on Zero Data Retention, the HIPAA configuration, customer-managed keys or an IP allowlist: Anthropic says cloud sessions do not work with the first three and fail on the last unless Anthropic support exempts them. Hivra does not claim an attestation of that kind.

Marcus, an indie developer whose code is on GitLab: Anthropic's pages say a cloud session cannot push results back to a GitLab or Bitbucket remote when the repository is sent as a bundle. Marcus wants a computer he can push from. Hivra, where the Git tab and terminal work against any remote.

Lena, an open-source maintainer who already pays for Claude: She does one-off fixes on public repositories and does not want a monthly line item beyond her subscription. Claude Code on the web. For occasional one-off fixes, a computer that stays on would cost more than the work needs.

Sam, who builds web apps and wants a real browser next to the repository: He wants the agent to open and test the running app in a browser on the same machine. Hivra, on a computer that has a browser tab beside the terminal and files.

Ravi, who has no Claude subscription yet: Anthropic's pages say cloud sessions need Pro, Max or Team, or an Enterprise seat that includes Claude Code. Ravi can launch Claude Code on a Hivra computer and pay for model use with Hivra credits instead. Hivra credits run Claude Code on Claude models served through Hivra, not through an Anthropic subscription, so it is not identical to a subscription setup. Hivra, if he wants to start without a Claude subscription.

How to try both

  1. Pick one small, real task. A bug fix or a small refactor in a repository you know, with tests you can run. Use the same task for both so the comparison means something.

  2. Run it as a cloud session. Open claude.ai/code, or run claude --cloud from the terminal, against the repository. Cloud sessions need a Claude plan that includes them, and a GitHub repository for a normal clone and pull request.

  3. Run it on a Hivra computer. Launch Claude Code from the agents page on a paid Hivra Cloud computer, sign in with your own Claude account, and bring the repository in through the terminal or Git tab. Hivra is independent of Anthropic and runs Anthropic's own CLI.

  4. Walk away from both. Close the laptop, then come back later. For the Hivra run, start Claude Code inside tmux in the computer's Terminal tab, so it keeps going. Note what is still there when you return, and what you had to set up again.

  5. Check your usage. If you signed in to Hivra with the same Claude account, both runs drew on the same usage limits. Look at how much of your window each used before deciding.

  6. Add up a month. Count the subscription on one side. On the other, count the Hivra computer plus any model usage you pay outside your subscription. Pick the cheaper option unless the persistence or non-GitHub needs from the scenarios above apply to you.

You can also keep both. Use cloud sessions for GitHub pull requests and keep a Hivra computer for work that needs files, tools and other agents to stay put.

What survives, and for how long

On Anthropic's side, the answer depends on how long the session has been idle. Its cloud environments documentation says that after a few idle minutes a session's VM pauses with its files saved, and your next message restores the same VM and starts Claude Code again. A paused VM can later be reclaimed, and Anthropic's pages do not state how long that takes. If the paused VM has been reclaimed, reopening the session provisions a fresh VM instead. After a reclaim, conversation history is restored, but running shell commands, subagents and session-scoped scheduled tasks are not. Anthropic stores the session transcript so you can return to it.

A setup script's result is cached for later sessions, so installed packages and written files carry over. Running processes and started databases do not, and packages Claude installs in the middle of a session are not carried into other sessions. A foreground command waits 2 minutes by default and up to 10; one that times out moves to the background and can run up to 30 more minutes, and an environment can raise these. Anthropic's pages do not state a longest session, or how many sessions can run at once.

On Hivra's side, the computer is the persistent thing. On a paid Hivra plan the computer stays on and keeps your files, sessions and login. A Claude Code or Codex run you start inside tmux in the computer's Terminal tab keeps going after you close the laptop. On Claude Code, work you send through Telegram, connected in the agent's Telegram tab, runs on the computer, not in your browser. Files, repositories, logins and CLI session history stay on the computer, whether or not a browser tab is open. Hivra does not promise backups, so copy out anything you cannot afford to lose, as you would on any machine.

Retention is a separate question from persistence, and the two products answer it differently. Anthropic's data usage page says that for Free, Pro and Max accounts, retention is five years if data use for model improvement is allowed and 30 days if not, and that Team, Enterprise and API use standard 30-day retention. If you sign in to Claude on a Hivra computer, your prompts go to Anthropic under the same terms, while the files on the computer are yours to keep or delete there.

Things a comparison chart cannot tell you

Prices, feature availability, introductory offers and refund policies can all change. The vendor figures and documentation on this page were collected from each provider's published pages in November 2026. Some of them may have changed since, so confirm any quoted vendor price, hardware size, compliance status or security statement against the provider's current documentation before you buy.

Security claims also need context. A managed host can take infrastructure upkeep off your hands, but it cannot make an unrestricted AI agent safe. Review secrets, account permissions, approvals and backups wherever you run it.

Where these numbers come from

Anthropic's figures on this page come from the pages below, as of . Anthropic changes plans and limits, so check them before you pay.

Anthropic's pricing page shows its prices without a sign-in and labels none of them as promotional. It says prices and plans are subject to change, and it does not mention Claude Code on the web by name.

Self-hosted environments, where cloud sessions run on runners in a customer's own network, are a public beta on Team and Enterprise, off by default. The conversation still goes to Anthropic, which stores the transcript.

Claude Managed Agents, Anthropic's beta hosted agent APIs billed on tokens plus a per-session-hour rate, are a separate product and are not compared here.

Anthropic's pages do not state data residency for cloud session VMs, the longest a session can run, or how many can run at once.

Common questions

Is Claude Code on the web free?

Not on its own. Anthropic says cloud sessions are available on Pro, Max and Team, and for Enterprise users with premium seats or Chat + Claude Code seats, and that there is no separate charge for the cloud VM. The session counts toward your plan's usage limits. Anthropic's pricing page lists its Free level without Claude Code.

How much does Hivra cost compared with Claude Code on the web?

Hivra is $9.99 a month for 2 vCPU and 4 GB of RAM, and every computer Hivra Cloud runs needs a paid plan. A Hivra account itself costs nothing. The plan does not include AI usage, so Claude Code on Hivra is paid for with your own Claude account or Hivra credits. Claude Code on the web has no compute charge but needs a Claude subscription, which Anthropic lists from $20 a month billed monthly, as of November 2026.

Can I use Claude Code on the web and Hivra together?

Yes. They are separate. If you sign in to Claude on a Hivra computer with the same account, both draw on the same Claude usage limits, and Anthropic says cloud sessions share limits with your other Claude and Claude Code usage. Many people use cloud sessions for GitHub pull requests and a Hivra computer for work that needs persistent files and tools.

Will Claude Code keep running when I close my laptop?

On Anthropic's side, yes: its documentation says a cloud session keeps running after you close your laptop. Anthropic says a session's VM pauses with its files saved after a few idle minutes; a paused VM can later be reclaimed, and its pages do not state how long that takes. Running shell commands are not restored after a reclaim. On Hivra, a paid computer stays on and is not paused for inactivity. A Claude Code run you start inside tmux in the computer's Terminal tab keeps going after you close the laptop.

Does Claude Code on the web work with GitLab or Bitbucket?

Only partly. Anthropic's pages say repository cloning and pull requests need GitHub, including self-hosted GitHub Enterprise Server on Team and Enterprise plans. A GitLab or Bitbucket repository can be sent to a session as a local bundle, but the session cannot push results back to that remote. On a Hivra computer you work in a terminal and Git tab, so any remote you can reach from it works.

Where does my code and data go?

With Claude Code on the web, the session runs in an Anthropic-managed VM, and Anthropic says its operations are logged and that sessions can be deleted at any time. Retention depends on your plan and on whether data use for model improvement is allowed. On Hivra, your files sit on a computer of your own. If you sign in with your own Claude account, your prompts still go to Anthropic under the same terms. Its pages do not state a data region for cloud session VMs.

Which is better for a team with security or audit needs?

Claude Code on the web, if you need what Anthropic documents: logged operations, credentials kept outside the VM, and a security overview pointing to a Trust Center for its SOC 2 Type 2 report and ISO 27001 certificate. Hivra does not claim an attestation of that kind. Confirm what each report covers with Anthropic, and check first that your organization is not on Zero Data Retention, the HIPAA configuration, customer-managed keys or an IP allowlist: Anthropic says cloud sessions do not work with the first three and fail on the last unless Anthropic support exempts them.

Is Hivra affiliated with Anthropic?

No. Hivra is an independent service. It runs Anthropic's own Claude Code CLI on a computer you control, and you sign in with your own Claude account or use Hivra credits. It is not affiliated with, sponsored by or endorsed by Anthropic.

Ready to give your agent a computer?

If you want a persistent environment without administering the server yourself, take a look at Hivra's plans and supported agents. If you want root access and prefer doing things yourself, a VPS may genuinely be the better fit.