Sandboxed coding agents with your company's context, integrations, and guardrails.
Connect all of your company's environments, from monorepos to microservices. Install any CLI, API, service, or MCP server, layer in custom instructions and skills, then set guardrails and secrets. Snapshot once so every session boots in seconds.
Install from mise, npm, brew, or github
Datadog
Salesforce
Stripe
NetSuite+ anything else
Build an alert inspector for #incidents, a sales prospector for #revenue, or a support triager for your inbox. Each one runs investigations, ships PRs, drafts replies, and posts findings without anyone asking. Tag them from Slack, Linear, GitHub, or anywhere your team already works.
Slack
LinearGitHubJira+ many more
Anyone can prompt an agent and watch it work, from engineering to support to sales. Hand off mid-session, collaborate in real time, and ship the result however your team needs: a PR, a deploy, a message, a ticket, or a report.
Live visibility into every session: tool calls, chain of thought, file changes. Track cost per agent, per user, per team. Spend limits, allowlists, and approval gates baked in.
Browser, terminal, or API.
Sandboxes, orchestration, guardrails, observability, integrations — Runtime handles the agent infrastructure your team would otherwise spend months building from scratch.
Each team gets a sandboxed agent with the data, integrations, and guardrails they need.
Self-Hostable
Deploy Runtime on your own infrastructure with your own cloud, models, and secrets. Extend it with custom skills and integrations.
MIT
Templates
Apache 2.0
CLI & Shared libs
AGPL v3
API & Worker
Self-host
Full control
Who is Runtime for?
Runtime is for any company that wants every function to ship work with a coding agent, not just engineering. Platform teams use it to roll out agents safely, while product, design, marketing, support, finance, and people teams use the same sandbox to automate work they already own.
How do agents work inside Slack? Do we always have to tag them?
You can tag them, or let them work proactively. Each team gets its own sandboxed agent in Slack with a name you choose, like @runtime-finance, @runtime-support, or @ada, that you @mention with a question or a task. You can also point it at a channel so it picks up new messages on its own without anyone tagging it. Either way, it replies in a thread with the result, the source rows it used, the cost of the run, and an Open Session button so you can step into the sandbox if you need to dig deeper.
What integrations come out of the box?
Runtime ships with first-class connectors for the systems most teams already run. That includes data warehouses (Snowflake, BigQuery, Redshift), billing (Stripe, NetSuite, QuickBooks), HR (Rippling, Gusto, Workday, Deel), CRM and marketing (HubSpot, Segment, GA4), support (Zendesk, Intercom), alerting (PagerDuty, Sentry, Datadog), and engineering (GitHub, Linear, Notion). Beyond that, you can bring any tool with an API key: the agents reach it through its CLI, MCP server, SDK, or REST API, the same way one of your engineers would call it.
Does an agent ever touch our raw production data?
No. Agents work against sandboxes that mirror or sample your data with the policies you set, including PII redaction and row-level scopes. Production writes happen only through reviewed actions or pull requests, so the agent never edits live systems on its own.
Can I self-host Runtime?
Yes. You can run Runtime fully inside your own cloud with your own models, sandboxes, and storage, or use our hosted version. Policies and audit logs follow your team across both.
if you want help getting set up.
Sandboxed, named, and live in Slack. Self-host or cloud. No credit card required.