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.