Factory launches a self-serve Teams plan for Droids

Factory has launched Teams, a self-serve subscription for up to 10 developers using its autonomous coding agents, called Droids. The Teams plan combines individual Pro-tier usage limits with centralized billing, giving small groups a route between separate Pro accounts and an enterprise contract.

The plan targets work that teams can specify, test, and review, including bug fixes, test generation, dependency upgrades, and framework migrations. Engineers can delegate those tasks to Droids while retaining control over code review, merging, and deployment.

The bill at each team size

Factory charges a $60 monthly base fee plus $40 per seat, with a maximum of 10 seats. Each seat receives its own Pro-tier rate limits.

Factory is also offering a $500 promotional credit through an application on the Teams page. The offer is available for a limited period, so applicants should confirm its deadline, eligibility rules, and expiration terms.

At general availability, Factory advertised pricing of roughly $40 per team plus $10 per active user each month, with no seat minimum. The current plan raises both charges while including Pro-tier usage for every seat. A meaningful comparison requires the usage allowances attached to each version.

How Droids divide the work

A Droid accepts a natural-language task and can plan the implementation, edit code, run tests, and prepare changes for delivery. Its practical autonomy depends on repository permissions, available tools, branch protections, and the team’s approval rules.

Developers can use Droids from the terminal, browser, Slack, VS Code, JetBrains IDEs, and Vim. Factory also supports models from Anthropic, OpenAI, and Google, allowing teams to select Claude, GPT, or Gemini for a given task.

Factory adds several coordination features above the underlying coding agents:

• Spec Mode investigates a task and drafts an implementation plan before editing code.
• Custom Droids provide specialist agents with dedicated instructions and tool permissions.
• Missions split larger projects into milestones and distribute work across multiple agents.
• Skills and plugins package reusable instructions, integrations, and workflows.
• Worktree sessions isolate concurrent changes in separate Git worktrees.

Git worktrees give each agent a separate working directory and branch while sharing the same repository. That isolation reduces collisions when several Droids modify a codebase at once, although teams still need tests and human review before merging changes.

Capital, customers, and competition

Factory introduced the plan after raising a $150 million Series C led by Khosla Ventures in April 2026 at a reported $1.5 billion post-money valuation. That round followed a $50 million Series B in September 2025 backed by NEA, Sequoia Capital, J.P. Morgan, and Nvidia.

Factory lists Nvidia, Adobe, T-Mobile, DoorDash, and Blackstone among its customers. The Teams page does not establish which subscription tier each company uses, so those names should not be read as endorsements of the new self-serve plan specifically.

Factory competes for engineering budgets with Cognition’s Devin, Cursor, Amp, Claude Code, and agent-orchestration platforms such as Tembo. Team billing and shared administration are already common in this market. Product evaluations will turn on code quality, model access, repository controls, observability, usage limits, and total cost.

Where the plan fits

The 10-seat limit places Teams squarely among startups, independent engineering groups, and small product squads inside larger companies. Organizations requiring more seats, single sign-on, audit logs, contractual security terms, or procurement support remain candidates for Factory’s enterprise offering.

Against individual Pro subscriptions priced at $40 per developer, Teams carries a fixed $60 monthly premium at every supported team size. Centralized billing and team coordination account for that premium. The promotional credit can offset it temporarily, but the standard plan does not provide a volume discount on seats.

Teams with recurring maintenance work and established review practices are the clearest fit. Flaky tests, dependency upgrades, migrations, and well-scoped bug queues provide bounded tasks that agents can execute while developers validate the resulting changes.

Checks before rollout

A production evaluation should verify the operational terms that headline pricing does not capture:

• Usage limits: confirm request caps, throttling behavior, and reset periods for each seat.
• Repository access: define which repositories, branches, secrets, and external tools Droids can reach.
• Data handling: review retention policies and whether code or prompts may be used to train provider models.
• Model billing: determine which model costs are included and whether any integrations require separate API credentials.
• Administration: check offboarding, task ownership, activity history, and permission controls.
• Promotion terms: confirm the $500 credit’s application process, eligibility window, and expiration date.