Agentic Index
Factory vs Capy (2026)
Factory last verified ·Capy last verified
Factory and Capy both run fleets of coding agents in parallel, and they are built for different buyers. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Factory sells to enterprise engineering organizations. Its Droids take tickets from Linear and Jira, Missions plan multi feature projects that an orchestrator splits across parallel workers, AutoWiki keeps a wiki of each repository current on every push, and deployment runs from Factory's cloud and a dedicated EU instance to the customer's own VPC or a fully airgapped install. Capy, built by Scrapybara, Inc., sells to engineering teams that want agent swarms on one shared plan. Captains orchestrate hundreds of agents in Firecracker microVMs, a Review agent reads every pull request while Autofix clears CI failures and merge conflicts, and agents test web apps in Chrome and mobile builds on cloud phones.
Both let customers pick models from Anthropic, OpenAI, Google and xAI or bring their own keys and subscriptions, both take work from Slack, Linear and GitHub, and both start free on the customer's own inference. Factory charges $20 to $200 a month per individual, and Teams adds $40 a seat to a $60 team fee. Capy charges one organization price from $20 to $200 a month with no seat fee.
Choose Factory for long, governed work across many repositories. Choose Capy for parallel agents a whole team shares on one plan.
On the Agentic Index coding agent ranking, neither Factory nor Capy clears the bar, which asks for all five merge loop capabilities documented in full. Factory does not document testing, debugging and optimization in full; Capy does not document knowledge grounding and RAG in full, nor testing, debugging and optimization. 3 of the 96 vendors in the lane clear it. See the coding agent ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Factory and Capy are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,212 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Factory if
- Work arrives as tickets. Droids pull a Linear or Jira ticket's description, acceptance criteria, comments and linked context before they start, and work can also be handed over from Slack, Microsoft Teams or Google Chat.
- Projects run for weeks across many features. Missions get a plan of features and milestones approved, then an orchestrator hands the work to parallel workers and checks each milestone.
- Code cannot leave your network. Factory Private runs Droid sandboxes in your own VPC through OpenCompute in private preview, and a fully airgapped deployment uses your own model endpoints.
- Agents should answer production alerts. Incident Response sets Droid on alerts in Slack, and automations start Droids on a schedule, a GitHub event or a webhook.
- Security review needs depth. Factory holds SOC 2 Type II, ISO 27001 and ISO 42001, and Business and Enterprise add SSO, SCIM, audit logs and zero data retention.
Choose Capy if
- The whole team shares one bill. Capy charges one subscription per organization with unlimited members, from Lite at $20 a month with $20 of model usage and 30,000 machine minutes to Max at $200.
- Mobile apps need testing too. From Pro up, agents test iOS and Android builds on cloud iPhones and Android phones and record annotated videos of each run.
- Pull requests should fix themselves. The Review agent reads each pull request in a real checkout and comments on specific lines, and Autofix answers CI failures, review comments and merge conflicts.
- Agents should move between machines. A thread can start in Capy's cloud and continue on a laptop through the desktop app or on any server through the Dock CLI.
- You want to compare models on one task. The same task can run on several models side by side, and each subagent can use its own model.
| Feature | F Factory |
C Capy |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
FactoryIntegrations & Tool Calling MCP connects Droid to the customer's own tools and data, and Connectors add third party apps with managed authentication and organization level controls. Delegations take work from Slack, Linear, Jira, Microsoft Teams and Google Chat with shared instructions, plugins, identity and compute, and automations act on GitHub events and inbound webhooks, with org policy deciding which models, tools and integrations Droid may use. Sourcedocs.factory.com/harness/mcp, harness/connectors, delegations and enterprise/identity-and-access; docs.factory.com/delegations/indexread 2026-10-28 |
||
|
CapyIntegrations & Tool Calling Capy acts inside the tools a team uses. A GitHub App opens and reviews pull requests, Slack threads take @Capy, delegating a Linear issue creates a native agent session that streams progress back, and Sentry reports can be imported. MCP servers connect over HTTP or stdio with OAuth, Tailscale ephemeral nodes reach private databases and internal services, Vercel previews, Revyl and Paper are integrated, and OIDC federation gives machines short lived GCP, AWS, Azure or Vault credentials. GitHub Enterprise Server is not supported. Sourcedocs.capy.ai/integrations/mcpread 2026-10-28 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
FactoryWorkflow Orchestration Custom droids are subagents with their own system prompt, model and tool policy that Droid delegates focused tasks to in a fresh context window. Missions plan and run large multi feature projects: the customer approves a plan of features and milestones, and an orchestrator in Mission Control assigns the work to workers, validates milestones and runs headless through droid exec --mission. Worktrees keep parallel sessions apart. Sourcedocs.factory.com/harness/subagents, missions/overview and missions/referenceread 2026-10-28 |
||
|
CapyWorkflow Orchestration A thread delegates work to subagents that nest up to three levels, on a shared or a fresh machine, each with its own model, and work such as a migration splits across subagents that each ship their own pull request. Captains are long lived orchestrator agents that direct crews of threads, keep their own Drive and can manage hundreds of agents, so a team can run thousands of agents at once, each task on its own branch and machine. Sourcedocs.capy.ai/subagentsread 2026-11-19 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
FactoryTriggers & Channel Coverage Automations start a Droid session on a schedule (plain words or cron), a Slack message, a GitHub event or an inbound webhook, running on a Droid Computer, an Environment, the desktop app or GitHub Actions. Incident Response sets Droid to respond to production alerts in Slack, Triage classifies inbound work and routes it, and Droid Exec publishes GitHub Actions workflows for PR review and weekly cron runs. Sourcedocs.factory.com/software-factory/automations, incident-response, triage and droid-exec/overviewread 2026-10-28 |
||
|
CapyTriggers & Channel Coverage Automations carry one to twenty triggers: cron with a five minute floor, GitHub events, Slack message bursts, an incoming webhook and on demand runs from the API, and the API adds Linear triggers (issue created, status changed, end of cycle) and Sentry triggers. Delegating a Linear issue or mentioning @capy on a pull request comment starts work, and a thread wakes on its own when CI finishes, a review lands or a pull request merges. Sourcedocs.capy.ai/automationsread 2026-10-28 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
FactoryKnowledge Grounding & RAG AutoWiki generates structured wikis of each repository's architecture, modules, APIs and conventions. The /wiki command builds one from the Droid CLI, /install-wiki sets up a CI action that regenerates it on every push to the default branch, the Wiki Browser in the Factory App searches and manages wikis, and the AutoWiki API creates runs, browses pages, searches and exports. Sourcedocs.factory.com/software-factory/wiki/overview, wiki/auto-refresh, wiki/web-viewer and api-reference/wikiread 2026-10-28 |
||
|
CapyKnowledge Grounding & RAG Agents work over a real checkout of the customer's repository inside their machine, nested AGENTS.md files load when a folder is first touched, a Review context page holds organization rules and files, and imported context such as Sentry reports and attached files lands on the agent's machine. No persistent codebase index, embeddings or retrieval layer is described, so what an agent knows of the code comes from reading the checkout during the task. Sourcedocs.capy.ai/instructionsread 2026-10-28 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
FactoryMemory & State Persistence Sessions are resumable across the app, CLI, web and mobile and drivable through the Sessions API, and AGENTS.md and hierarchical settings carry configuration across sessions. Session state stays within one session, AGENTS.md holds standing instructions, and the documentation index lists no memory layer of Factory's own. Sourcedocs.factory.com/api-reference/sessions, harness/agents-md and llms.txtread 2026-10-28 |
||
|
CapyMemory & State Persistence A thread is a durable conversation stored on Capy's servers that holds the full history of its messages, machines, subagents and pull requests, survives archiving and resumes when woken. An opt in Memory experiment keeps what a user teaches Capy across threads, and review findings list the memory they rest on, but no scope, lifetime or way to delete entries is described. Drive holds AGENTS.md instructions at personal or organization level, which are instructions, not memory. Sourcecapy.ai/changelogread 2026-10-28 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
FactoryHuman Oversight & Guardrails Autonomy levels (Off, Low, Medium, High) decide what Droid may do without confirmation, and permission rules allow, require approval for, or block matching shell commands, with an ask rule requiring approval even at High autonomy. Missions start only after the customer approves the plan, org managed settings enforce these as hard policy, and OS level sandboxing and Droid Shield secret scanning sit beside them. Sourcedocs.factory.com/autonomy-and-safety/permission-rules, auto-run and missions/planningread 2026-10-28 |
||
|
CapyHuman Oversight & Guardrails Capy never merges or enables auto merge unless asked in the thread, the Merge menu offers Enable auto merge and Force merge, and a root AGENTS.md can grant standing merge permission. The agent waits for a go ahead when told to, review mode runs Off, Once or on every push, paired devices ask before use, any agent can be stopped mid run, and a thread or Captain tags the user under Needs you when blocked on a decision, access or credentials. Sourcedocs.capy.ai/admin/securityread 2026-10-28 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
FactorySecurity, Identity & Governance Factory lists SOC 2 Type II, ISO 27001 and ISO 42001 with reports, architecture documents and subprocessor lists in its Trust Center at trust.factory.com, and offers SSO over SAML or OIDC, SCIM directory sync, organization roles flowing from the identity provider, service accounts with their own API keys and an organization audit log that records authentication, SSO and SCIM changes and policy changes. Sourcedocs.factory.com/enterprise/compliance-audit-and-monitoring and enterprise/identity-and-accessread 2026-10-28 |
||
|
CapySecurity, Identity & Governance Capy holds SOC 2 Type II on every plan, audited and pen tested every year, with the report available through its trust center. Organizations carry Owner, Admin and Member roles, and every plan includes an audit log. Single sign on through SAML and OIDC with Okta, Google Workspace and Microsoft Entra ID, with required MFA, is a $100 a month add on for Lite, Pro and Max and included on Enterprise, and the desktop app signs in with SSO. Zero data retention is available on request, code is not used for training, and data is encrypted in transit and at rest. No SCIM is documented. Sourcecapy.ai/pricingread 2026-11-19 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
FactoryObservability & Auditability Droid exports OpenTelemetry to the customer's collector: each user turn produces a trace whose child spans are the model calls and tool runs, with droid.tool and droid.message spans when message content logging is on, plus tool, MCP and blocked command metrics tagged by session and user. An organization audit log records who did what, including who started a Droid session from a connected tool, and Factory Analytics reports usage, credits and tool use per session. Sourcedocs.factory.com/enterprise/telemetry/data-reference, audit-log and compliance-audit-and-monitoringread 2026-10-28 |
||
|
CapyObservability & Auditability Each thread keeps its full transcript and tool output, shows the agent's plan, terminal output, file changes and diffs, and a status (active, waiting, needs attention, ready for review), with the machine's desktop streamed live into the thread pane. An Activity page and usage reports break spend down by member, model and thread, the API streams events, end to end test runs record annotated video, and every plan includes an audit log. Sourcedocs.capy.ai/async-workread 2026-11-19 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
FactoryDeployment & Data Residency Factory offers two deployment options. Factory Managed runs the control plane in Factory's cloud while Droid runs on developer machines, CI, machines the customer registers through Remote Control and Factory managed Droid Computers, with LLM traffic routed to the customer's own providers or gateways and a dedicated EU deployment (api.eu.factory.ai, EU session storage and EU only inference) for enterprise customers. Factory Private, in private preview, runs Droid sandboxes inside the customer's own VPC through OpenCompute, a self hosted service that provisions sandboxes on Kubernetes, EC2 or Lambda microVMs on demand. A fully airgapped Custom Deployment uses in network model endpoints with no Factory cloud at runtime, and Enterprise adds data residency, dedicated compute and on premises options. Sourcedocs.factory.com/enterprise/network-and-deployment, opencompute/overview, enterprise/airgapped-deployment and factory.com/pricingread 2026-10-28 |
||
|
CapyDeployment & Data Residency Each cloud thread runs on its own Firecracker microVM on Ubuntu 24.04, sleeping after about two minutes and deleted after 30 days asleep. The hosted service runs in one region, US East (New York), with no region choice. Threads can also run on the customer's own Mac, Windows or Linux computer through the desktop app or on any server through the Dock CLI, moving between machines mid task, and Enterprise offers running in the customer's own cloud on request, with OIDC federation issuing short lived cloud credentials to machines. Sourcedocs.capy.ai/machinesread 2026-11-19 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
FactoryPrebuilt Agents, Templates & Packs Plugins package skills, commands, custom droids, output styles, hooks and MCP servers, and Factory maintains an official marketplace at Factory-AI/factory-plugins naming droid-control (terminal, browser and computer automation for QA and demos), droid-evolved (skills for navigation, writing, design and frontend work) and security-engineer (security review, threat modeling and vulnerability validation). Organizations run internal approved marketplaces, and since 27 October admins pick plugins from their registered marketplaces. Sourcedocs.factory.com/harness/plugins, enterprise/internal-plugin-marketplaces and changelog/release-notesread 2026-10-28 |
||
|
CapyPrebuilt Agents, Templates & Packs A plugin marketplace offers searchable, categorized plugins that bundle MCP servers and skills, with a Verified by Capy mark on plugins Capy has picked and tested, and named plugins include Firecrawl, ClickStack and Supermemory. A team installs plugins across the organization or per project or adds one from a GitHub repository. An Explore page lists plugins, skills and themes, and built in skills ship with the product beside the Review agent and Captains. Sourcedocs.capy.ai/integrations/pluginsread 2026-10-28 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
FactoryModel Flexibility & Routing The customer picks among Factory hosted models from Anthropic, OpenAI, Google, xAI and Factory's own pool, lets the Factory Router choose per task, or brings its own OpenAI, Anthropic, open source or local models by key, and enterprise controls restrict which models, base URLs and providers a fleet may use. Sourcedocs.factory.com/models and model-independence/byokread 2026-10-28 |
||
|
CapyModel Flexibility & Routing A person picks the model per thread and per subagent from Anthropic, OpenAI, xAI, Google, Moonshot, Z.ai, DeepSeek, Alibaba, MiniMax, Meta and other makers, and can run one task on several models to compare. Teams can bring Anthropic, OpenAI, Google and xAI keys or gateways such as Vercel, OpenRouter and Cloudflare, and existing Codex, Copilot and SuperGrok subscriptions connect and draw on the provider's limits. Model tokens bill at each provider's list price with no markup. Sourcedocs.capy.ai/models-and-pricingread 2026-10-28 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
FactoryAPIs, SDKs & MCP Extensibility A REST API at api.factory.ai with bearer API keys creates and drives Droid sessions, wiki runs, CI automations and readiness reports (the Sessions API is enabled for selected organizations), beside the Droid SDK and headless droid exec for scripts and CI. Sourcedocs.factory.ai/api-reference/sessions and droid-exec/overviewread 2026-09-29 |
||
|
CapyAPIs, SDKs & MCP Extensibility A public REST API with bearer keys and an OpenAPI specification covers projects, threads, messages, tasks, automations, reviews and usage, so developers can start, message, interrupt and archive agent work from their own code and stream its events. MCP servers and plugins extend what the agents can reach, and the Dock CLI attaches any server as a machine for Capy threads. Sourcedocs.capy.ai/api-reference/overviewread 2026-10-25 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
FactoryTesting, Debugging & Optimization The Agent Readiness model scores how ready the customer's repository is for agents, Agent Effectiveness measures throughput, output and spend across the organization, and code review, security review and Automated QA test the customer's code. Factory publishes its own benchmark results (Agent Arena, Legacy Bench, Terminal Bench). Factory does not describe a harness, scored test set or optimization loop for evaluating Droid's behavior on the customer's work. Sourcedocs.factory.com/agent-readiness/overview, agent-effectiveness/overview and benchmarksread 2026-10-28 |
||
|
CapyTesting, Debugging & Optimization A built in Review agent checks every pull request from a real checkout, labels each finding confirmed or investigate and comments on specific lines, and Autofix answers CI failures and review comments. Agents run the project's own tests and end to end checks in their machines, which tests the customer's code. On the agent side, the same task can run on different models to compare approaches, and there is no evaluation suite or regression testing of agent behavior. Sourcedocs.capy.ai/reviewread 2026-10-28 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
FactoryBrowser & Computer Use Droid Control, an official Factory plugin, lets Droids launch and operate web apps and Electron apps through end to end flows. The Droid clicks, types and captures screenshots as QA and demo evidence, and Automated QA tests the application as a real user would with visual evidence. The CLI also ships an agent-browser skill for browser automation, the browser pane in Factory's desktop app takes Droid's clicks and keystrokes directly, and since 20 October the built in browser can import Chrome cookies on macOS so Droid stays signed in. Sourcedocs.factory.com/software-factory/droid-control, automated-qa and changelog/release-notesread 2026-10-28 |
||
|
CapyBrowser & Computer Use Each cloud machine runs an XFCE desktop with Google Chrome that streams live into the thread pane, and the agents use native computer use and browser use for end to end testing, recording annotated videos of each run. From the Pro plan, agents also test iOS and Android builds on cloud iPhones and Android phones through Revyl. Capy does not describe approvals for purchases or form submissions made in the browser. Sourcedocs.capy.ai/machinesread 2026-10-28 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | F Factory |
C Capy |
|---|---|---|
|
Entry price Lowest public entry point |
Free with your own inference; Pro $20 a month; Plus $100; Max $200; Teams $60 plus $40 a seat | Free on your own computers; Lite $20 a month, or $16 billed annually; Pro $100; Max $200; Enterprise custom |
|
Pricing confidence How public the numbers are |
Public, partial | Public, exact |
|
Billing Primary billing axis |
A flat monthly plan price with usage inside rolling rate limits, plus optional prepaid Extra Usage. Teams adds a charge per seat to a team fee. | One subscription per organization with a shared monthly credit balance and no seat fee. Model tokens and cloud machine time draw the credits down. |
|
Variable cost Workload / overage exposure |
High variable cost | High variable cost |
|
Free tier / trial Try before you buy |
Free tier
|
No free tierTrial
|
|
Buying motion Self-serve vs sales call |
Mixed | Mixed |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Factory
-
· Human approval / guardrails
Droid CLI and Desktop v1.12.0 reclassify git actions in Droid's risk model: a plain push or pull request now counts as medium risk, while force pushes stay high.
Source -
· Security / enterprise
Droid CLI and Desktop v1.11.0 extend command sandboxing to Windows.
Source -
· Security / enterprise
User Groups lets enterprise admins give groups synced from their identity provider their own monthly usage limit and model access, applied in the Factory organizations they choose.
Source
Capy
-
· Security / enterprise
Version 0.8.0 of Capy adds an Identity and access page in organization settings where admins verify a domain by DNS record and connect Google Workspace sign in, sold as an add on, with Microsoft Entra ID, Okta and other SAML or OIDC providers by contact.
Source -
· Deployment / data residency
The new Dock CLI in Capy 0.7.0 runs Capy without the desktop app, so a build server, cloud VM or spare Mac can host agent threads with the tools and credentials already on it.
Source -
· Workflow orchestration
Capy 0.4.7 lets a Captain, the agent that coordinates a crew of other threads, run on one of the user's paired devices, and the Captain can start crew threads on any paired device or in the cloud.
Source
Factory raised $200 million at a $5 billion valuation in September 2026, for more than $400 million in total, and counts Nvidia, Blackstone, RBC and Adyen among its customers. Capy comes from Scrapybara, Inc., a Y Combinator company whose first Capy release came in August 2026, and its hosted machines run only in US East, while Factory offers a dedicated EU deployment. Factory's in VPC option is in private preview. Neither prints what a typical task costs, since model usage and machine time draw on each plan, so ask both how a long migration would bill.
More comparisons with Factory or Capy
Other matchups in coding agents
Not the pairing you were after? These compare a different set of coding agents on the same 14 capabilities.