Netclode is live · free · last verified 25 Oct 2026 · viability monitor
Netclode
Netclode is a self-hosted remote coding agent that runs Claude Code, Codex, OpenCode and Copilot in per-session microVM sandboxes.
Pick Netclode if you already run Kubernetes and Tailscale and want agent sessions on hardware you control. The microVM-per-session design is what makes the rest possible — sudo and Docker inside the sandbox, zero-compute pause/resume via JuiceFS, whole-state snapshots, keys kept out of the sandbox by a proxy. Pass if you need a managed service, team features or a commercial licence; the CC BY-NC-SA 4.0 terms rule out paid client work.
Verdict generatedVerified 6d ago · liveness 66/100 · cite: rightaichoice.com/tools/netclode
- Developers already running k3s or comfortable with single-node Kubernetes
- Homelab operators with a VPS and a Tailscale tailnet
- Privacy-focused developers who want code and API keys on their own hardware
- Solo developers who want to drive an agent from an iPhone or Mac
- Teams needing shared sessions, roles or an audit trail
- Anyone who wants a managed service with a vendor on call
- Commercial or client work — the licence is CC BY-NC-SA 4.0 (non-commercial)
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Netclode if you want a managed agent you can hand to a team tomorrow, because you will be the one operating k3s, Tailscale, JuiceFS and the agent service, and the CC BY-NC-SA 4.0 licence bars commercial use.
Pausing a session drops compute to zero, but the JuiceFS volume on S3 keeps accruing object-storage charges for as long as you keep the session around.
Netclode itself is free software under a non-commercial licence, so the comparison that matters is not licence price but total cost of ownership. Against hosted agents that bundle inference and infrastructure into a subscription, Netclode shifts spend to a VPS plus your own provider accounts, which is cheaper at high usage and more expensive at low usage. The non-commercial licence makes it a poor fit for anyone billing clients.
In short
Netclode — Netclode is a self-hosted remote coding agent that runs Claude Code, Codex, OpenCode and Copilot in per-session microVM sandboxes. Best for Developers already running k3s or comfortable with single-node Kubernetes, Homelab operators with a VPS and a Tailscale tailnet, Privacy-focused developers who want code and API keys on their own hardware. Free to use.
What is Netclode?
Netclode — Netclode is a self-hosted remote coding agent that runs Claude Code, Codex, OpenCode and Copilot in per-session microVM sandboxes. Best for Developers already running k3s or comfortable with single-node Kubernetes, Homelab operators with a VPS and a Tailscale tailnet, Privacy-focused developers who want code and API keys on their own hardware. Free to use.
Netclode is a self-hosted remote coding agent for developers who want cloud-agent convenience without handing a vendor their repo and API keys. You provision a Linux VPS with the included Ansible playbook, which stands up a single-node k3s cluster running Kata Containers and Cloud Hypervisor, so every agent session gets its own microVM. Isolation at the VM level lets the agent inside the sandbox hold full sudo access and a running Docker daemon — it can install packages, run builds and start servers without exposing your host. The harnesses are the real products, not reimplementations: Claude Code, Codex, OpenCode and GitHub Copilot all run behind a single interface. A GitHub integration clones a repo at session start and can be granted write access so the agent pushes changes, while the SwiftUI app gives you a git diff view to review what landed. Sessions sit on a JuiceFS persistent volume backed by S3, so you can pause a session, spend zero compute, and resume with filesystem and conversation state intact. Turn-based snapshots restore the entire session state to an earlier point rather than just the git tree. A secret proxy keeps your coding SDK API keys out of the sandbox, Redis Streams sync session state in real time, and the Tailscale operator gates the control plane to your tailnet. Sandbox ports can be exported into the tailnet for private web previews, and if you have NVIDIA GPUs, Ollama can serve inference locally. It is a single-user project built for one developer's own workflow: no team roles or audit trail, and the iOS app is early. Against Claude Code on the web, Copilot Agent and Codex web, the pitch is control — their agents run root in shared cloud sandboxes, and Netclode's microVM model gives you the isolation, pause/resume and key handling they leave out.
Key features
- Self-hosted remote coding agent you run on your own Linux VPS
- Per-session microVM sandbox via Kata Containers and Cloud Hypervisor
- Full sudo access and a running Docker daemon inside the sandbox
- Runs Claude Code, Codex, OpenCode and GitHub Copilot harnesses
- Secret proxy keeps coding SDK API keys out of the sandbox
- GitHub integration clones a repo at session start with optional push access
- JuiceFS persistent volume backed by S3 object storage
- Pause and resume sessions at zero compute cost
- Turn-based snapshots restore entire session state, not just git
- Redis Streams for real-time session state sync
- Tailscale Operator gates the control plane to your tailnet
- Export sandbox ports into the tailnet for private web previews
- Native SwiftUI app for iOS 26 and macOS with streaming markdown and voice input
- Git diff view and live terminal inside the app
- Go CLI shell for debugging, plus optional Ollama local inference on NVIDIA GPUs
Behind the verdict
The appeal here is not the agent, it is the plumbing. Claude Code web is a better front end out of the box — the author says so himself — but it runs your agent as root in a sandbox you do not own, with pre-installed languages and no pause button. Netclode swaps that for a single-node k3s cluster on your VPS where each session is a Kata Containers microVM. That is the design decision everything else hangs off: once you are isolated at the VM level, you can hand the agent sudo and a Docker daemon without worry. In practice the features that earn their keep are pause/resume and snapshots. JuiceFS on S3 means a paused session costs nothing while state stays put, which matters if you brainstorm agent work from a phone between other things. Turn-based snapshots that restore whole session state, not just git, are the safety net most hosted agents never give you. And the secret proxy keeping SDK keys out of the sandbox is a small architectural detail with an outsized effect on how comfortable you are letting the agent run wild. We would reach for this when the repo is private, the keys are yours, and the machine can be yours too. If you already run a tailnet and have touched k3s, the Ansible playbook gets you a working server in one go. If you have not, budget real time: single-node Kubernetes, Kata and Cloud Hypervisor, JuiceFS, a Tailscale operator, Connect RPC and a Go CLI are all things you may end up debugging. Where it bites: no team layer. No shared sessions, no roles, no audit trail. One operator, by design. The licence is CC BY-NC-SA 4.0, so client work is off the table, and the SwiftUI client is early-stage. Compared to alternatives, Claude Code on the web is the one to beat on polish, and GitHub Copilot Agent is the one to beat on repo integration — though
Models under the hood
as of 2026-10-23
Limitations
- Netclode is a personal, self-hosted project rather than a product: you provision and operate the Kubernetes/k3s cluster, Tailscale operator, JuiceFS, Redis and agent service yourself.
- It is single-user and the client is a native SwiftUI app for iOS and macOS rather than a web console.
- Local inference via Ollama requires NVIDIA GPUs and a separate GPU Operator setup.
- The blog documents real rough edges, including a Tailscale h2c problem and an abandoned Nix experiment.
as of 2026-10-08
Researching Netclode? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Netclode still active?
Netclode is live · free · last verified 25 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is Netclode? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What do users say about Netclode?
What people actually say about Netclode — is it worth it?
We scanned public community sources for Netclode on Sep 9, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Only 3 of the posts we fetched could be positively tied to Netclode. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
How we verified this
Every listed fact about Netclode — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 25 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Netclode 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed SSL certificate, who it suits, features, summary, our verdict, pricing tiers, who should skip it, description
- — changed limitations, models, platforms
- — changed features, who it suits, description, our verdict, hidden costs, integrations, limitations, switching in, switching out, who should skip it, pricing tiers, pricing fit, setup time, summary, use cases
- — changed limitations
- — changed limitations, switching in, description, who it suits, switching out, models, use cases, who should skip it, summary, pricing fit, setup time, features, hidden costs, our verdict, pricing tiers, integrations
- — changed domain expiry
Showing the 6 most recent of 10 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Netclode cost in 2026?
Netclode: Free to use. Pricing last verified 25 Oct 2026.
Plans compared
Every published Netclode tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Free | Free | — | Developers and homelab operators running personal, non-commercial projects on their own VPS, who are comfortable provisioning k3s, Tailscale and JuiceFS themselves.Adds: Starting tier: the software is free under CC BY-NC-SA 4.0, with costs shifting to your own VPS, S3 storage and coding-SDK provider accounts rather than a licence fee. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Netclode's pricing actually pencils out — and where peers do it cheaper.
Netclode itself is free software under a non-commercial licence, so the comparison that matters is not licence price but total cost of ownership. Against hosted agents that bundle inference and infrastructure into a subscription, Netclode shifts spend to a VPS plus your own provider accounts, which is cheaper at high usage and more expensive at low usage. The non-commercial licence makes it a poor fit for anyone billing clients.
Has Netclode's pricing changed?
No plan price for Netclode has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Netclode?
Pick Netclode if you are Developers already running k3s or comfortable with single-node Kubernetes, Homelab operators with a VPS and a Tailscale tailnet, Privacy-focused developers who want code and API keys on their own hardware, Solo developers who want to drive an agent from an iPhone or Mac.
Look elsewhere if you are Teams needing shared sessions, roles or an audit trail, Anyone who wants a managed service with a vendor on call, Commercial or client work — the licence is CC BY-NC-SA 4.0 (non-commercial), Non-technical users without Kubernetes and networking experience.
Skip it if Skip Netclode if you want a managed agent you can hand to a team tomorrow, because you will be the one operating k3s, Tailscale, JuiceFS and the agent service, and the CC BY-NC-SA 4.0 licence bars commercial use.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Netclode actually fits — and what changes day-one when you adopt it.
Runs the Ansible playbook against a fresh Linux VPS, which installs k3s, the Tailscale operator, JuiceFS and the agent service, then joins the Netclode control plane from the iOS app over the tailnet.
Outcome: A private coding agent reachable from a phone within an evening, with repo access scoped through the GitHub integration and API keys held by the secret proxy rather than on the sandbox.
Starts a Claude Code session on a repository from the iPhone app, lets it run, then opens the git diff view to read the changes and the live terminal to check a test run.
Outcome: A review pass on real agent work without opening a laptop, with the option to pause the session afterwards so it stops consuming compute.
Installs the NVIDIA GPU Operator, points the agent service at a local Ollama instance, and runs a session end to end with no external inference provider.
Outcome: Coding-agent assistance where neither the code nor the prompts leave the machine, at the cost of a narrower model selection than the hosted SDKs.
Use cases
- Kick off a Claude Code session on a repo from your phone while commuting, then read the diff on the train home
- Run an agent that installs dependencies and boots a database without risking your laptop or your production host
- Pause a long-running session overnight so it costs nothing, then resume with the filesystem and conversation intact
- Roll a session back to the turn before the agent broke the build
- Keep provider API keys off the sandbox entirely so a prompt-injected session cannot leak them
- Serve inference locally with Ollama for a coding agent that never sends code to a third party
- Preview a web server the agent started inside the sandbox through your Tailnet
Setup time & first value
How long it actually takes to get something useful out of Netclode — broken out by persona, not the marketing-page minute.
For someone already fluent in k3s and Tailscale, the Ansible playbook gets a server provisioned in a single run, though bringing up JuiceFS, Redis, the GPU Operator and the first working session realistically takes an afternoon and some debugging. Without Kubernetes experience, expect days rather than hours — the write-up itself covers a Tailscale h2c problem and an abandoned Nix approach. The
Switching to or from Netclode
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Claude Code web: run the same harness inside a Netclode microVM sandbox, keeping your prompts and workflow while moving execution onto your own host.
- →From GitHub Copilot Agent: point the Netclode agent at the repository through the GitHub integration with write access instead of accepting an automatic PR per session.
- →From a self-managed Docker dev container: replace the container with a Kata microVM sandbox so the agent can have sudo and a Docker daemon safely.
- →From running coding agents directly on your laptop: move them to a remote sandbox and drive them from the iOS app or the Go CLI client.
- ↗To Claude Code web or another managed agent: move session work off your own cluster if operating k3s stops being worth the effort.
- ↗To GitHub Copilot Agent: a hosted path if you want PR-per-session behaviour and no infrastructure to run.
- ↗To a plain SSH plus tmux workflow: if the microVM and snapshot layer is more machinery than your use case needs.
- ↗To local-only CLI agents: if you decide you do not need remote or mobile access at all.
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Netclode”, and we withheld 6: 6 could not be judged, because “Netclode” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Netclode.
Official links
What are the best Netclode alternatives?
The closest alternatives to Netclode we list are Paseo, Sandboxed.Sh and Replicas. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Paseo | Free | Free | — |
| Sandboxed.Sh | Freemium | Pricing not published | — |
| Replicas | Freemium | Pricing not published | — |
Alternatives to Netclode
View all
Paseo
Paseo is a self-hosted control plane for orchestrating Claude Code, Codex, Copilot and 30+ coding agents from desktop, phone or browser.
Sandboxed.Sh
Orchestrate Claude Code, Codex, Antigravity, OpenCode and Grok from one self-hosted control plane for AI coding agents.
Tools that pair well with Netclode
Common stack mates teams adopt alongside Netclode, with the specific reason each pairing earns its keep.
Paseo
Paseo is a self-hosted control plane for orchestrating Claude Code, Codex, Copilot and 30+ coding agents from desktop, phone or browser.
Sandboxed.Sh
Orchestrate Claude Code, Codex, Antigravity, OpenCode and Grok from one self-hosted control plane for AI coding agents.
Replicas
Replicas runs Claude Code, Codex, Cursor, and OpenCode coding agents in isolated cloud VMs and hands back pull requests.
Netclode vs its closest rival
Netclode's closest head-to-head is with Spider Cloud — Choose Netclode if you're a developer comfortable with Kubernetes who wants to self-host coding agents with strong sandbox isolation and a mobile app. Choose Spider Cloud if you need a reliable, low-cost web scraping API for AI agents and RAG, with a rich set of developer integrations and recent features like Browser AI commands. Verdict generated
Head-to-head comparisons
Netclode vs Spider Cloud
Choose Netclode if you're a developer comfortable with Kubernetes who wants to self-host coding agents with strong sandbox isolation and a mobile app. Choose Spider Cloud if you need a reliable, low-cost web scraping API for AI agents and RAG, with a rich set of developer integrations and recent features like Browser AI commands.
GeneratedNetclode vs Temporal Ai
For teams building production-grade AI agents or microservices that must survive failures, Temporal's durable execution, multiple SDKs, and cloud/self-hosted flexibility win. For individual developers or homelab enthusiasts who want a self-hosted coding agent with strong sandbox isolation and a mobile companion, Netclode is a compelling free choice—but requires Kubernetes know-how. Choose based on your operational tolerance and need for reliability vs. mobility.
GeneratedNetclode vs Voyage Ai
If your priority is high-accuracy retrieval for domain-specific RAG (finance, legal, code) with enterprise compliance, Voyage AI's specialized models and 32K context are unmatched. But if you want full control over a coding agent stack—self-hosted, isolated, and accessible from an iOS app—Netclode's free open-source approach is a unique alternative. They solve completely different problems: choose Voyage for data retrieval, Netclode for code generation on your own infra.
GeneratedFrequently asked questions
Best-of guides
Topics
Used Netclode? Help shape our editorial sentiment research.