Devin vs Verdent

Devin 72

Hosted reading. Service-user keys with roles and named permissions per endpoint, revocable, with rotation endpoints in beta for Enterprise and expiring personal tokens. Custom roles are an Enterprise option, and Teams has Admin and Member only (25). Security profiles restrict network, MCP servers, git and the Devin MCP to read-only, and read-only API permissions exist. They are opt-in, and session creation accepts bypass_approval (16). AI Guardrails screen user messages and pull request comments for prompt injection, on Enterprise only, and they don't cover web pages or repository content Devin reads (8). Audit logs through the API need an enterprise-level permission. Session events and insights are available on all plans (10). SOC 2 Type II and ISO/IEC 27001:2022, a disclosure address at security@cognition.ai, no security.txt, and the trust centre answers No to having a bug bounty (13).

Verdent 33

Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.

Devin 62

API and MCP reading. The MCP server documents 13 tools, several of them consolidated manage tools, and list endpoints take first to size a page (17). Cursor pagination on every v3 list endpoint and filters on session search by tag, playbook, origin, user and time (18). problem+json with error_code, field-level errors on 422 and a 400 that lists valid platform names, but no published code list (15). No idempotency key on v3 session creation. max_acu_limit caps what a session can spend, and the MCP tool annotations couldn't be read without a key (4). Only prompt is required to start a session. No official SDK found, only a Terraform provider (8).

Verdent 35

Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.

Devin 80

API reading. Public OpenAPI 3.1 spec for v3 with 182 paths and 274 operations on 4 November 2026, and separate v1 and v2 specs (25). llms.txt with 393 lines and a Markdown twin of every page (10). Each endpoint page names its required permission, but 63 of 274 operations have no description and the MCP tool descriptions are one line each (10). Enums on fields such as devin_mode, origin and category, with most strings unconstrained and nullable (9). curl examples in the quick starts, and 401, 403, 404, 409, 422 and 429 declared on all 274 operations, without a catalogue of error_code values (11). Versioned paths (v1, v2, v3, v3beta1) and an API release notes page dated by month, newest November 2026 (15).

Verdent 55

Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as "certain tool executions" and "destructive operations" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.

Devin 75

Editorial half. Closed source with clear terms from Cognition AI, Inc. (15). Terms (30 June 2026), privacy policy, security page and data processing agreement agree with each other. Customer data may be used for model training by default on self-serve plans, with an opt-out on paid plans that also turns on zero data retention at model providers, and Enterprise data isn't trained on without written consent. Retention is stated as the length of the customer relationship, with no periods (18). The API versioning policy on the release notes page says breaking changes are announced at least 7 days in advance and a deprecated endpoint stays available through a deprecation period. Dated notices followed it for the schedules endpoints (announced 10 September, creation refused from 24 September 2026), and others cover the v2 clone endpoint and Playbooks moving to Skills (23 October). v1 and v2 are marked legacy with no end date (20). Sub-processors listed with purpose and country, and 15 days' notice of additions, per the 8 October check (18).

Verdent 55

Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47.

Devin 35

Hosted reading. Status page at www.devinstatus.com (Atlassian Statuspage) with 14 components, among them Cloud Agent and Cloud Web Client, read from the page itself on 4 November 2026 (20). Its history feed for the 90 days from 6 August 2026 lists Devin unavailable on 13 August (20 minutes), Devin Cloud unavailable on 13 August (2 hours 40 minutes) and the web app down on 24 September (about 2 hours), with minor session and Ask Devin incidents on 10 and 11 August, 3 and 17 September and 26 October. Both 13 August entries report the service unavailable. The 24 September entry names only the web app, not the API or the MCP server, so it is read as partial, as dashboard outages are on other listings. Two majors (5). Two scheduled maintenance entries (7 and 17 August) are read as maintenance. 429 is a documented response, but no rate limit figures were found (0). No Retry-After or backoff guidance found, and v3 session creation has no idempotency key (0). The platform terms give no guarantee of availability, and enterprise terms weren't read (0). The v3 API is the current, recommended surface, with 27 of 274 operations under /v3beta1 (10).

Verdent 43

Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.