← November 17, 2026 edition

helix-2

Run AI agents in isolated desktop sandboxes

Helix Gives Every AI Agent Its Own Desktop and That Changes Everything

The Macro: The AI Agent Infrastructure War Is Just Getting Started

There is a quiet arms race happening in AI infrastructure right now. Everyone agrees that AI agents are the future. Nobody agrees on how to run them. The current landscape is a mess of competing approaches: cloud-hosted sandboxes, local execution environments, browser-based automation, API orchestration layers. Each approach makes different tradeoffs around security, performance, cost, and control.

The enterprise AI agent market is projected to hit $47 billion by 2030, according to multiple analyst estimates. That growth is being driven by companies who want agents that can actually do work, not just answer questions. But doing work means accessing systems, running code, browsing the web, and manipulating files. You need an execution environment that is both capable and secure. Most current solutions compromise on one or the other.

The agent orchestration space has gotten crowded fast. CrewAI, AutoGen, and LangGraph are all fighting for mindshare at the framework level. On the infrastructure side, E2B and Modal offer cloud sandboxes. Replit provides development environments. But there is a meaningful difference between giving an agent an API endpoint and giving it an actual computer. That difference is what Helix is betting on.

The Micro: Full Desktops for AI Agents, Not Just API Wrappers

Helix is an AI agent orchestration platform built around a concept they call Agent Desktops. Each agent gets a full GPU-accelerated 4K streaming desktop with browser access, terminal access, and filesystem access. These are not containers pretending to be computers. They are actual desktop environments that agents can see, navigate, and interact with visually.

This matters more than it might sound. Most agent frameworks operate through APIs and command-line interfaces. That works fine for structured tasks. But a huge amount of real-world work happens in graphical interfaces that were designed for humans: web applications, design tools, spreadsheets, email clients. Giving agents actual desktops means they can interact with those tools the same way a human would. No custom integrations required.

The fleet orchestration system uses a kanban-style workflow: Backlog, Design Review, Implementation, Done. You can run 3 to 5 parallel agent instances through their multi-agent CLI. The platform includes something called Kodit for code intelligence, which provides semantic search and codebase navigation. Security is serious: RBAC, SOC 2 Type II certification, ISO 27001 certification, and ephemeral per-task credentials that get destroyed when the agent finishes its work.

The pricing tiers reveal who Helix thinks its customers are. The Mac App tier at $299 per year gives you up to 15 agent desktops running on your own hardware. That is aimed at individual developers and small teams who want local control. The Cloud tier at $499 per month per team offers 30 concurrent desktops and 5,000 tasks per month. Enterprise starts at $75,000 for an 8-week pilot with Kubernetes deployment. And then there is the Sovereign Server option at roughly $175,000: a physical 4U rack server with 8 RTX 6000 Pro GPUs and 768GB of VRAM that you install in your own data center.

That Sovereign Server tier is fascinating. It tells you that Helix is going after customers who cannot or will not put their agent workloads in someone else’s cloud. Defense contractors, financial institutions, healthcare organizations, government agencies. The kind of buyers who need agents that can do real work but also need absolute certainty about where their data lives.

The open-source component on GitHub adds credibility. You can inspect the codebase, understand the architecture, and evaluate whether the security claims hold up under scrutiny. That transparency is rare in the agent infrastructure space, where most vendors ask you to trust their black box.

The multi-timezone workflow capability is a nice touch for distributed teams. Agents can hand off work across time zones, which means your engineering team in Berlin can kick off an agent task at end of day and your team in San Francisco picks up the results in the morning. Continuous progress without continuous human attention.

I could not find specific founder information through public sources, but the technical depth of the product and the SOC 2 and ISO certifications suggest a team with serious enterprise software experience.

The Verdict

Helix is making a bet that agents need computers, not just APIs. I think that bet is correct. The gap between what agents can do through API calls and what they could do with full desktop access is enormous. Every web application that does not have an API becomes accessible. Every manual workflow that requires clicking through a GUI becomes automatable.

At 30 days, I want to see real-world performance benchmarks. GPU-accelerated 4K streaming desktops sound expensive to run. The economics need to work at scale, or the pricing becomes untenable for anything beyond high-value tasks.

At 60 days, the security model needs battle testing. Giving AI agents full desktop environments with browser access is powerful but also risky. One misconfigured agent with web access could do real damage. The ephemeral credential model and RBAC need to be rock solid.

At 90 days, I want to see how the multi-agent orchestration handles failure. When agent number 3 out of 5 crashes mid-task, what happens to the kanban board? What happens to the work the other agents were depending on? Coordination at scale is where most agent platforms fall apart.

The Sovereign Server tier alone tells me this team understands their market. They are not building toys. They are building infrastructure for organizations that take both AI capability and data sovereignty seriously. That is a small market today and a very large market tomorrow.