Kortix vs Gumloop: the open-source platform you can own

Kortix is the open-source AI Management System: one git repo holds your agents, skills, company memory and connectors, and each session runs on its own isolated Linux machine. Gumloop is a strong hosted no-code builder for teams that want agents without running infrastructure. The difference is ownership: with Kortix the platform is yours to read, self-host and change, and every change lands as a diff a person reviews.

Compared here:

Gumloop

What Gumloop gets right

• No-code building for the whole team. Gumloop's pitch is that understanding a task is the only prerequisite to automating it, so the people closest to the work build the agents (Gumloop).
• A company brain. Shared knowledge, the skills a team runs on and live context from connected tools feed one brain that agents and people both use (Gumloop).
• Agents that improve themselves. Gumloop agents reflect on their own runs and tune themselves over time, and built-in evals measure quality and catch regressions (Gumloop).
• Built to share. One teammate builds an agent and the whole company uses it, with owner, editor, viewer or use-only access granted per person, team or organization (Gumloop).
• Pricing that starts small. Pro starts at $37 per month, and Enterprise is custom priced (Gumloop pricing, checked October 2026).
• Enterprise controls. Audit logging, SAML SSO and SCIM, SOC 2 Type II and GDPR zero-retention agreements for third-party models ship as platform features (Gumloop enterprise).
• VPC deployment. A customer can run Gumloop inside its own AWS, Azure or Google Cloud environment so data stays in its network (Gumloop enterprise).

Where Gumloop stops for a company that wants to own the stack

• The platform is not published as source. Gumloop's "Open-source by default" line is about running open-source models, and its public GitHub organization hosts an editor plugin and MCP forks rather than the agent platform itself (Gumloop, Gumloop on GitHub).
• Configuration lives in Gumloop, not your repo. Agents are assembled in Gumloop's builder, with connectors and skills chosen in its interface. No repo of yours holds the agents, memory and connector rules as versioned, diffable files (Gumloop docs).
• VPC is hosted software in your cloud. A VPC deployment keeps data inside your network. The platform still runs as hosted software, and you do not inspect or change it (Gumloop enterprise).
• Approval happens on a tool call. A write tool can pause for a person, which guards the action itself. The work that follows still does not arrive as a diff against a repo your team owns (Gumloop docs).

None of that is a flaw in Gumloop. It is the shape of a hosted product, and it fits teams that would rather not operate any infrastructure.

What Kortix does differently

One git repository holds the agents, skills, company memory, connector configuration and triggers, and every session runs on its own isolated Linux machine (Kortix docs).

curl -fsSL https://kortix.com/install | bash

# kortix.yaml (excerpt)
sandbox:
  image: Dockerfile
agents:
  ops-morning:
    file: agents/ops-morning.md
    connectors: [slack, stripe]
triggers:
  - type: cron
    agent: ops-morning
    cron: '0 7 * * 1-5'

• The company is one repo you own. Agents and skills are Markdown and memory is files, so you can grep the whole company, diff any change and roll any part of it back (Kortix docs).
• Any model, your keys. Pick the model per agent, per session or per message: Claude, OpenAI, Gemini, the ChatGPT subscription you already pay for, or your own OpenAI-compatible endpoint (Kortix).
• Every business tool. 3,000+ apps connect alongside any MCP, OpenAPI, GraphQL or HTTP API. Credentials are brokered server-side, and each tool call is allow, ask or block (Kortix).
• Every session gets its own computer. A session boots an isolated Linux sandbox on a branch named after it, and thousands run in parallel on one configuration (Kortix docs).
• One gate to land work. The agent commits to its branch, and the work reaches the default branch through a change request a person reads as a diff. Merge is default-deny for agents (Kortix docs).
• Start work from anywhere. Kick off a session from the web app, Slack, Teams, email, mobile, CLI or API, or let cron and signed webhooks start one with nobody asking (Kortix).
• Deploy anywhere. Self-host on a laptop, a VPS, your VPC or on-prem, or run managed Kortix Cloud. Self-hosting is free, and the Team plan is $40 per seat per month (Kortix pricing, checked October 2026).

Kortix is open source (Elastic License 2.0): self-host, read and modify the code. The source is at Kortix on GitHub.

What leaving each platform costs

Kortix keeps the company as text files, so a move means cloning the repo and running it wherever you choose, or taking the managed cloud path. Gumloop keeps agents, skills and connector configuration inside its product, and those settings do not travel as files, so a move means rebuilding them somewhere else. Self-hosting Kortix means operating it, and managed Kortix Cloud removes that work. A team that expects its stack to change should weigh which of those it wants.

Side by side

When to pick which

Next reads: Kortix vs Claude Cowork and what an open-source AI agent platform is.

Start with Kortix and keep the whole company in a repo you own.