Comparison

Nairi vs Devin

Cognition's Devin is a polished, managed coding-agent product with a serious enterprise sales motion. Nairi is the open-runtime team-agent platform. Pick the harness per agent, mention it from Slack or Discord, run the full agent loop on your own hardware if you need to. Here's an honest side-by-side.

TL;DR

Devin is one of the most mature managed AI-coding products you can buy today. Series D >$1B at a $26B valuation, $492M ARR as of May 2026, deep first-class Slack integration, the Windsurf-derived Devin Desktop IDE, a dedicated Devin Review PR-review specialist, turnkey Auto-Triage for channel monitoring, 40+ curated MCP marketplace, Windows VMs, Android emulators, SOC2 Type II since 2024. If you're buying an enterprise agent product where every primitive is hosted and managed, the depth Devin offers there is real.

Nairi sits at a different point. The full agent loop runs in an open-source Go daemon you can host yourself. Shared-chat agents in Slack and Discord pick the harness per agent (Claude Code, Codex, OpenCode, Cursor). LLM cost is pass-through to your provider key. No ACU quotas, no metered active-runtime billing. One shared team agent in a channel; rules, skills, and MCP servers at the org level.

Honest framing: pick Devin if you want the most polished managed product and you're comfortable with Cognition's harness, the ACU pricing model, and the orchestration plane running on Cognition's cloud. Pick Nairi if you need to run the agent loop on your own hardware, you want harness optionality in shared-chat agents, or you'd rather pay your LLM provider directly than buy thinking-time quotas.

Side by side

Structural differences first, then the areas where Devin matches or wins.

Self-host the entire agent loop

The nairid daemon is open-source Go. The full loop — message receive, harness invocation, tool execution, response back — runs inside the daemon on your hardware. Docker, Kubernetes, a VM, an air-gapped box. Nothing phones home for orchestration.

Cognition retired self-hosted deployment on May 12, 2026. Their own blog: "hosting even our best Tab model would require a full rack of frontier GPUs." Customer Dedicated Deployment relocates the Devbox sandbox into a customer VPC, but the Brain — the orchestration plane — is per their docs "always residing in Cognition's Cloud."

Pick your harness in shared-chat agents

Per-agent choice across Slack, Discord, and the web app: Claude Code, Codex, OpenCode, or Cursor. Bring your provider key. Mix harnesses across the same org for different jobs.

Devin Desktop (the Windsurf-derived IDE) supports the Agent Client Protocol locally, so Claude Agent / Codex / OpenCode load there. Devin Cloud — the SaaS product behind Slack and Auto-Triage — is locked to Cognition's own harness. On 2026-06-13 Cognition announced forced removal of Claude Fable 5 access; users on the cloud harness don't pick when models disappear.

LLM cost model

Pass-through to your LLM provider per the chosen harness. You bring your Anthropic / OpenAI / Google key; the agent's thinking time costs you what your provider charges. No metered active-runtime billing on top.

ACU-based quotas under monthly tiers (Free / Pro $20 / Max $200 / Teams $80 + $40/seat / Enterprise). Numeric ACU allowances aren't disclosed on the public pricing page. Overage is billed at "API pricing" (also undisclosed). Independent reviews repeatedly flag the predictability problem — Brainroad: "teams budgeted for $20 and got invoiced for $400."

Slack and Discord, symmetric

Slack and Discord are both first-class. The same agent runs in either, with the same rules, skills, MCP, and config. Install, pick channels, mention.

Slack is first-class and deep (@-mention, thread chat, slash-style keywords like !ask / !deep / !dana, emoji-reaction status). Microsoft Teams is supported. Discord is not — the Integrations Overview page lists only Slack and Teams under Communication.

Team-shared agent abstraction in channels

Agents are owned by the org. Anyone in the channel can mention them. Rules, skills, and MCP servers apply at the agent level, not the user level. Conversation state lives in the thread, available to everyone on it.

Devin's Slack model is session-per-trigger inside a thread. The web app and Auto-Triage have their own orchestration. Workspace API keys are per-workspace, and per Cognition's docs MCP scope is "shared within your organization" — admin-gated at the org level rather than configured per agent for a team.

GitHub-native PR review specialist

PR review is one of several use cases. A GitHub Action calls the Nairi REST API on PR open; the agent runs in its own container with the harness and tools you configured.

Devin Review is a dedicated PR-review product with inline review comments, Review Autofix that pushes follow-up commits, and GitHub Enterprise Server support. If PR review is the only workflow you care about, Devin ships a deeper specialized surface here.

Persistent channel monitor + auto-PR

Achievable via skills + scheduled jobs + MCP servers, but not packaged as a single turnkey feature.

Auto-Triage (launched 2026-05-18) is a turnkey product: persistent Devins monitor Slack channels, Linear, GitHub, Sentry, Datadog, PagerDuty, and webhooks; auto-investigate, dedupe reports, route to owners, open PRs. Per-channel Automations templates configure it.

Hosted long-running primitives

Per-agent containers with the harness and tools configured. Scheduled jobs for cron-style runs. No multiagent orchestration primitive today.

Memory, multiagent orchestration ("Devin Manages Devins"), Outcomes evaluation, Computer Use for desktop testing, Windows VMs, Android emulators, Devin CLI for local→cloud handoff. Cognition ships features in this space every two to three weeks.

MCP marketplace breadth

Per-agent MCP configs. Composio-hosted MCPs supported alongside self-hosted MCP servers. Custom MCP via stdio / SSE / HTTP.

40+ curated MCP servers in a built-in Marketplace (Datadog, Sentry, Linear, Asana, Postgres, MySQL, Neon, BigQuery, Figma, Stripe, Looker, Metabase, Notion, Confluence, Salesforce, PostHog, etc.). MCP scope is organization-level with admin gating. Built-in Secrets feature for MCP credentials.

Enterprise procurement and brand

Earlier-stage on the enterprise motion. SaaS at nairi.ai plus the self-host option for teams that need it.

SOC2 Type II since September 2024. Series D >$1B at $26B valuation (May 2026). $492M ARR as of May 2026. Named customer wins (Mercedes-Benz, Itaú, Microsoft via Windsurf history). Customer Dedicated VPC deployment for regulated buyers. Cognition's enterprise sales motion is materially more mature.

Devin descriptions reflect Cognition's public docs at docs.devin.ai, blog posts on cognition.ai/blog, and devin.ai/pricing as of June 2026. Cognition ships product changes every two to three weeks; verify the current behavior before relying on any specific detail.

Run the full agent loop on your own hardware

Cognition put self-hosted Devin into maintenance mode on May 12, 2026. No new self-hosted customers, no feature development on that path, and existing self-hosted customers are being incentivized to switch to cloud or to the Customer Dedicated Deployment option. Their own blog gave the reasoning: "hosting even our best Tab model would require a full rack of frontier GPUs." Customer Dedicated, the remaining enterprise option, relocates the Devbox sandbox into a customer VPC over PrivateLink or IPSec, but the Brain (the orchestration plane that coordinates the agent's actions) is per Cognition's docs "always residing in Cognition's Cloud."

That's the right shape for organizations that are comfortable depending on Cognition's cloud for the brains of the agent. It's the wrong shape if your procurement, compliance, or data-residency posture treats "the agent's orchestration runs on a third-party cloud" as a hard blocker. Regulated industries, government contractors, certain financial-services accounts, air-gapped or sovereign-cloud deployments, or any deal where the security review asks where the agent loop runs.

Nairi's nairid daemon is open-source Go that runs the whole agent loop inside the daemon: receive messages from Slack or Discord, call the configured harness, execute tools, post back. Nothing phones home for orchestration. Run it in Docker, on Kubernetes, on a single VM, or on an air-gapped box. Most teams take the managed SaaS at nairi.ai because they don't want to run a daemon; the self-hosted path exists for teams that need to answer "yes, the orchestration runs on our infrastructure" during procurement.

Pick the harness for your shared-chat agent

Devin Desktop, the Windsurf-derived IDE rebranded after the December 2025 Codeium acquisition, supports the Agent Client Protocol locally, so Claude Agent, Codex, OpenCode, and other ACP-compatible runtimes load into the IDE on your laptop. That's a real concession to harness optionality. The gap is that Devin Cloud, which is where Slack, Auto-Triage, and shared-chat agents live, is still locked to Cognition's own harness. When Cognition announced forced removal of Claude Fable 5 access on June 13 2026 following Anthropic's directive, users on the cloud harness had no choice in the matter.

Nairi treats harness as a per-agent setting in shared chat. One agent on Claude Code where it has the edge, one on Codex where it's strong, one on OpenCode for the open-source-stack path, one on Cursor for the IDE-integrated workflow. Each agent has its own provider key. The choice isn't structural; it's a config field. You can mix harnesses across the same org and change them later without re-platforming.

The bet is that harness optionality matters more over time, not less. New harnesses ship every few months. New models with new capability curves arrive on different schedules. Teams that lock to one vendor's runtime pay the switching cost later. Nairi makes harness a config setting so the choice can change without rebuilding the team's agent platform.

Pay your LLM provider directly

Devin's pricing structure is a monthly tier (Free, Pro $20, Max $200, Teams $80 + $40/seat, Enterprise) with ACU quotas under each tier. The numeric ACU allowance per tier isn't disclosed on the public pricing page, and overage is billed at "API pricing" that also isn't posted publicly. The friction the community keeps flagging is predictability: ACUs are spent on agent active-runtime, not on successful output, so cost scales with how long the agent thrashes on a problem. Independent reviews repeatedly describe surprise bills. Brainroad documents "teams budgeted for $20 and got invoiced for $400"; Frontier AI's one-month review notes that larger tasks consumed disproportionate ACUs and often failed, so "you get nothing for your $40."

Nairi's pricing has no metered-runtime layer. LLM cost is pass-through to your provider key (Anthropic, OpenAI, or Google) per the chosen harness. The agent's thinking time costs you what your provider charges at their posted rates, not a Nairi-side multiplier. The team subscription covers the platform; the LLM bill is yours, directly, at posted rates.

Light, bursty usage might come out cheaper on a managed metered model than on per-provider rates plus a team subscription. The Nairi shape wins when usage is consistent enough that paying for thinking-time becomes the larger line item, or when cost predictability matters more than the raw cents-per-run.

Where Devin wins

Honest comparison pages are honest both ways. Here's where Cognition's managed product has the edge and we wouldn't try to claim parity.

  • Devin Review for PR review. A dedicated PR-review product with inline review comments, Review Autofix that pushes follow-up commits when fixes are mechanical, and GitHub Enterprise Server support. If PR review is the workflow you care about most, the specialized product is deeper than a general agent platform handling it as one use case.

  • Auto-Triage as a turnkey product. Persistent channel-monitor across Slack, Linear, GitHub, Sentry, Datadog, PagerDuty, and webhooks, with auto-dedupe, owner routing, and auto-PRs. Nairi can replicate the pattern via skills + scheduled jobs + MCP but not as a single one-click feature.

  • Hosted infra breadth. Memory, multiagent orchestration ("Devin Manages Devins"), Outcomes evaluation, Computer Use for desktop testing, Windows VMs, Android emulators, Devin CLI. Cognition ships features in this space every two to three weeks.

  • 40+ curated MCP marketplace. Datadog, Sentry, Linear, Asana, Postgres, MySQL, Neon, BigQuery, Figma, Stripe, Square, Looker, Metabase, Notion, Confluence, Salesforce, PostHog, Amplitude, Tavily, Raindrop and more, built in and admin-gated at the org level. Nairi supports per-agent MCP including Composio and self-hosted servers; the catalog isn't pre-curated.

  • Devin Desktop polish. The Windsurf-derived IDE is genuinely good. Local ACP runtime support there is a real concession to harness optionality on the laptop, even if it hasn't reached Devin Cloud yet.

  • Enterprise procurement gravity. SOC2 Type II since September 2024, $26B valuation, $492M ARR, named customer wins like Mercedes-Benz and Itaú, AWS Marketplace-class distribution. Cognition's enterprise sales motion is materially more mature.

Common questions

What teams ask when they're weighing the two.

Devin is Cognition's flagship AI coding agent product, first launched in March 2024. Today (June 2026) the product surface includes Devin Cloud (the web app and SaaS APIs), Devin Desktop (the Windsurf-derived IDE rebranded after Cognition's December 2025 Codeium / Windsurf acquisition), Devin CLI for local-to-cloud handoff, Devin Review for PR review, plus first-class Slack and Microsoft Teams integrations. Pricing tiers run Free / Pro $20 / Max $200 / Teams $80 + $40/seat / Enterprise. Cognition closed a Series D >$1B at a $26B valuation in May 2026 and reports $492M ARR as of the same month. This page is about how Devin compares to Nairi specifically; it isn't a general Devin review.
They overlap on "a team wants a coding / ops agent on their existing tools" but the architecture and surface are different shapes. Devin is a managed product: Cognition runs the agent loop, the harness, the model, the sandbox, the multiagent orchestrator, and ships a polished IDE, web app, Slack bot, and PR-review specialist on top. Nairi is the open-source-runtime team-agent platform: pick the harness per agent (Claude Code, Codex, OpenCode, Cursor), mention agents from Slack or Discord, run the full agent loop on your own hardware if you need to. One way to think about it: if your team is willing to depend on Cognition's runtime and pay metered ACUs for the polish, Devin is the more polished product. If you want harness optionality, predictable LLM cost via your own provider, or an agent loop that runs entirely on your infrastructure, that's the Nairi shape.
Not the orchestration plane, not anymore. Cognition formally moved self-hosted deployment into maintenance mode on May 12, 2026 — no new self-hosted customers, no feature development on that path, existing self-hosted customers "incentivized to switch" to cloud or Customer Dedicated. Their reasoning, in their own blog: "hosting even our best Tab model would require a full rack of frontier GPUs." The remaining enterprise option is Customer Dedicated Deployment, which relocates the Devbox (the sandbox) into a customer VPC via PrivateLink or IPSec — but per Cognition's docs, the Brain "always resides in Cognition's Cloud." Nairi's nairid daemon is open-source Go that runs the full agent loop on your hardware. Receiving messages from Slack or Discord, calling the configured harness, executing tools, posting back — all inside the daemon. If "the orchestration never leaves our infrastructure" is a hard requirement (regulated industries, government contracts, certain financial-services compliance bars), it's the structural difference that lets you say yes.
Not in Devin Cloud — and Slack, Auto-Triage, and the shared-chat agents all live in Devin Cloud. The cloud agent loop is Cognition's own harness, calling Cognition's SWE-family models or the configured frontier model (OpenAI / Claude / Gemini). Devin Desktop (the local IDE) is different: it ships ACP (Agent Client Protocol) support, so Claude Agent, Codex, OpenCode, and other ACP-compatible runtimes can run inside Devin Desktop locally. ACP support hasn't reached Devin Cloud yet. Today, June 13 2026, Cognition announced forced removal of Claude Fable 5 access following Anthropic's directive; users on the cloud harness don't choose when models or harnesses change. Nairi treats harness as a per-agent setting in shared chat: one agent on Claude Code where it's strong, one on Codex where it has the edge, one on OpenCode for the open-source path, one on Cursor for IDE-integrated workflows. Each agent has its own provider key.
Devin runs on monthly tiers with ACU (Agent Compute Unit) quotas under each tier. Free / Pro $20 / Max $200 / Teams $80 base + $40 per seat / Enterprise custom. The numeric ACU allowance per tier isn't disclosed on the public pricing page, and overage is billed at "API pricing" (also not posted publicly). The community-flagged friction is predictability: ACUs are spent on agent active-runtime, not on successful output, so cost scales with how long the agent thrashes. Independent reviews repeatedly describe surprise bills — Brainroad documents "teams budgeted for $20 and got invoiced for $400"; Frontier AI's one-month review notes that larger tasks consumed disproportionate ACUs and often failed, so "you get nothing for your $40." Nairi passes LLM cost through to your own provider key per the chosen harness — Anthropic, OpenAI, Google. You pay your LLM bill directly at your provider's published rates. No metered active-runtime layer on top, no opaque ACU accounting, no Nairi-side overage tier. The team subscription covers the platform; the agent's thinking cost is your LLM provider's.
No. Cognition's Integrations Overview lists only Slack and Microsoft Teams under Communication; there's no native Discord integration and the docs don't mention one. That matches Devin's go-to-market — engineering organizations standardized on Slack and Teams. If you're a dev-tools company with a community on Discord, an open-source project with a Discord server, a Discord-first team, or you're running ops in a community-facing channel that doesn't exist on Slack, Nairi treats Discord symmetrically to Slack: same agent, same rules, same skills, same MCP servers, same vault, same audit log. It isn't an afterthought.
This is a place where Devin wins on specialization and we shouldn't pretend otherwise. Devin Review is a dedicated PR-review product with inline review comments, Review Autofix that pushes follow-up commits when issues are mechanical, GitHub Enterprise Server support, and tight VCS integration. Nairi handles PR review as one use case among several — a GitHub Action calls the Nairi REST API on PR open, the agent runs in its own container with per-repo skills and rules. Both approaches work; Devin's is deeper at the GitHub-native layer. If the only workflow you care about is PR review and you'd rather have a specialized tool than a general agent platform, Devin Review is the more polished option. Nairi fits when the same agent platform also handles on-call response, scheduled jobs, support triage, knowledge Q&A, data-analyst queries, and arbitrary other team workflows — and PR review is one of the many.
Auto-Triage (launched 2026-05-18) is one of Cognition's most polished products. Persistent Devins monitor Slack channels, Linear, GitHub, Sentry, Datadog, PagerDuty, and arbitrary webhooks. When something fires they auto-investigate, dedupe against recent reports, route to the right owner, and open a PR when there's a mechanical fix. Long-term memory via a scratchpad, configured via Automations templates per channel. Nairi can achieve similar outcomes today via skills + scheduled jobs + MCP servers + per-channel rules — but not as a single turnkey feature. If "channel-monitor + auto-PR" is the specific pattern you need and you want one click to enable it, Devin's Auto-Triage is the more direct path. If you're already configuring skills and scheduled jobs anyway for other workflows, the achievement gap closes.
Yes, with a curated marketplace. 40+ MCP servers built into Devin's Marketplace including Datadog, Sentry, Linear, Asana, Postgres, MySQL, Neon, BigQuery, Figma, Stripe, Square, Looker, Metabase, Notion, Confluence, Salesforce, PostHog, Amplitude, Tavily, and Raindrop. Custom MCP via stdio, SSE, or HTTP. MCP scope is organization-level — admins control which servers are available; access is "shared within your organization" per Cognition's docs. Built-in Secrets feature for credentials. Nairi also supports MCP per agent, including Composio-hosted MCP servers and self-hosted ones, with secrets injected from the org-scoped vault at runtime. Devin's MCP catalog is broader out-of-the-box; Nairi's MCP binding is finer-grained per agent. Pick the model that fits your governance preference.
Pick Devin if any of the following hold. You want the most polished out-of-the-box agent product with a dedicated web app, IDE (Devin Desktop), and Slack bot. PR review is the workflow you care about most and you want a specialized product (Devin Review) over a general platform. You want Auto-Triage as a turnkey channel monitor + auto-PR feature without configuring it yourself. You need Windows VMs or Android emulators as agent runtime environments. The 40+ pre-curated MCP marketplace is more useful to you than per-agent MCP binding. You're comfortable on Cognition's harness with frontier model choice (OpenAI / Claude / Gemini) and don't need Claude Code, Codex, OpenCode, or Cursor specifically. ACU-quota pricing fits your usage shape better than per-team subscription. You're buying via AWS Marketplace or you value the SOC2 Type II + $26B + $492M ARR procurement gravity.
Pick Nairi if any of the following hold. You need the orchestration plane to run on your own infrastructure, not just the sandbox — regulated industry, government contract, hard data-residency bar, air-gapped environment, or any procurement conversation where "is the agent loop running on someone else's cloud" is a blocker. You want to choose the harness per agent (Claude Code, Codex, OpenCode, Cursor) in shared-chat surfaces, not just in a local IDE. LLM cost predictability matters and you'd rather pay your provider directly at posted rates than buy ACU quotas. Your team's chat surface is Discord, or you need Slack and Discord with equal first-class support. You want one shared team agent in a channel that everyone can mention, with org-level rules and skills, instead of session-per-trigger semantics. The faster the team needs an agent platform without compounding LLM-runtime fees, and the more important multi-harness flexibility and self-host posture are, the more Nairi fits.

Run the agent loop on your terms

Pick the harness per agent. Mention it from Slack or Discord. Self-host the runtime if you need to. Pay your LLM provider directly.