Runta
Runta is the execution layer for AI agents: a secure runtime in which agents can run computers, use credentials without seeing them, and operate under governed network and resource policies. It aims to make production agents safer, more controllable, recoverable, and less expensive to operate.
At a Glance
- Enterprises deploying autonomous AI agents
- AI product companies building agent applications
- Engineering and software-development teams using coding agents
- Security-conscious organizations requiring credential isolation and governed network access
- +2 more
AI Tools by Runta
(1)Runta
Managed Runtime for AI Agents
Discussions
No discussions yet
Be the first to start a discussion about Runta
Latest News
Products & Services
Managed, persistent and isolated computers for AI agents, with OS-level execution controls, governed egress, credential injection, checkpoints, auto-suspend/resume, and memory auto-scaling.
A managed-agent API and runtime experience providing persistent computers, conversations, streaming, runs, events, artifacts, computer sessions, and resumable agent work.
An Apache-2.0 open-source AI teammate with its own persistent cloud computer. It lets users hand off tasks, close the app, and return to the same conversation, machine, files, and results.
A built-in Exo runtime that separates a durable Harness from replaceable agent Executors and an isolated Sandbox, while Runta supplies protected model credentials, checkpoints, lifecycle management, auto-scaling, and network access control.
Market Position
Runta positions itself as an execution layer beneath the agent rather than an agent model or a front-end framework. It explicitly compares the control model with cloud-computer agent products such as Grok Bot and Muse, emphasizing enforcement at the runtime and egress boundary: isolated computers, policy-controlled destinations, credential injection without exposing secrets, persistent state, and auditability. Its broader competitive set includes managed agent sandboxes and runtime platforms, while Runta differentiates around OS/network-level governance, token-cost controls, and recoverable execution.
Leadership
Founders
Guanlan Dai
Founder and CEO. Dai was an early engineer and technical lead on Cloudflare's Edge team, where he worked on the edge proxy, CDN, caching, WAF, and front-line request path. He later became a founding engineering leader at Kong, building teams and products behind Kong Gateway, Kong Cloud, the Kubernetes Ingress Controller, and Kong's AI infrastructure products.
Executive Team
Guanlan Dai
Founder and CEO
Former early Cloudflare Edge engineer and Edge Platform leader; later a founding engineering leader at Kong responsible for Kong Gateway, Kong Cloud, Kubernetes Ingress Controller, and AI infrastructure products.
Founding Story
Runta was started after Guanlan Dai's experience building Cloudflare's and Kong's boundary infrastructure exposed a limitation of conventional security controls: software generally decides its behavior before execution, while AI agents make decisions dynamically as they run. Runta's initial vision was therefore to put governance underneath the agent, at the execution boundary where filesystem, process, credential, network, token, and compute actions become real.
Business Model
Revenue Model
Prepaid, usage-based billing for runtime resources; customers pay while agents are running and for memory/disk during paused or suspended states. There is no subscription or monthly minimum, and automatic top-ups are optional.
Pricing Tiers
Running state bills vCPU, memory, and disk; paused state bills memory and disk; suspended/shut-down state bills disk only; deleted runtimes incur no charge. New accounts receive $50 in free credit with no credit card required.
Target Markets
- Enterprises deploying autonomous AI agents
- AI product companies building agent applications
- Engineering and software-development teams using coding agents
- Security-conscious organizations requiring credential isolation and governed network access
- Teams operating long-running, asynchronous, browser, or computer-use agents
- Researchers and engineering teams evaluating agent harnesses
- Running coding agents and autonomous agents in persistent cloud computers
- Enterprise deployment of agents that need controlled access to internal services and credentials
- Long-running asynchronous tasks that continue after a user closes the app
- Secure browser and computer-use automation
- Building agent products without implementing runtime provisioning, isolation, lifecycle, credential security, and durable run state
- Benchmarking and evaluating coding-agent harnesses under consistent environments