Suna

What Suna does

• Isolated machine per session Every session gets its own disposable, isolated Linux sandbox on its own branch. The agent can install, run, and break anything inside it, and only what it commits survives to review.[1][2]

• Company as a git repository A project is a git repo with kortix.yaml at its root holding agents, skills, memory, tools, triggers, and connectors as versioned files. Kortix hosts the repo or you connect your own, and any git client can clone it through the authenticated proxy.[1]

• Change-request review before merge The agent commits its work, pushes the session branch, and opens a change request against the default branch. A person with merge permission reviews it, unless the agent is explicitly granted permission to merge its own work.[1]

• Bring any model provider There is no bundled model: you use any provider with your own keys, or the ChatGPT plan you already pay for, and can pick the model per agent, per session, or per message.[1][2]

• Broad connector surface Connectors reach more than 3,000 apps plus any MCP, OpenAPI, GraphQL, or HTTP API, with credentials brokered server-side. Agents are reachable from web, desktop, mobile, CLI, Slack, Teams, email, git, and the MCP server.[1][2]

Who Suna fits

• Teams wanting owned agent infrastructure Suna fits teams that want their agents, skills, memory, and connector rules as auditable files in a repo they control rather than locked inside a vendor's cloud. This is an editorial inference from the ownership model, not a vendor promise about any specific compliance outcome.[1][2]

• Human-in-the-loop agent operations The change-request workflow fits organizations that want every piece of agent output reviewed before it lands. This is an inference from the merge-permission design, which can be relaxed per agent.[1]

• Self-hosters avoiding per-seat fees Teams with their own hardware and model keys can run the full platform with no per-seat fee, moving to managed cloud later without rebuilding, since the same harness runs in both places.[1][2]

Limits to weigh

• Source-available license, not OSI open source The Elastic License 2.0 forbids offering the software to third parties as a hosted or managed service. Companies running it for their own operations are unaffected, but nobody can resell Suna itself as a service.[1][2]

• Model bill stays yours Neither the free self-host nor the $40 per-seat cloud price includes model usage. Your provider charges apply on top, which keeps pricing transparent but means total cost depends on your model choices.[1]

• Enterprise controls are plan-gated SAML single sign-on and audit logs are documented only for the custom-priced Enterprise tier, so smaller teams plan around per-project and seat ceilings instead.[1]

• No fully-offline story documented Self-host setup pulls images from Docker Hub and agents need model provider keys, so a disconnected deployment cannot be confirmed from the observed sources. Treated as an evidence gap, not a proven limitation.[1][2]

Switching and compatibility