Skip to content
Tooling & costs

Factory Droid vs Claude Code and Codex in 2026: plans, rate limits, Jira and who pays for the run

Factory sells Droid as a coding agent with its own plans, rolling rate limits and model multipliers, and since October it runs from Jira through Rovo Chat. We read Factory's pricing and docs pages and Atlassian's announcement to compare a Droid run with a Claude Code or Codex run on the plan you already pay, and to show where the brief and the design states come from in each case.

Sydla Journal cover: Factory Droid vs Claude Code and Codex, who pays for the run in 2026. On the left, a Droid run: Factory plans from $20 to $200 a month, rolling 5-hour, 7-day and 30-day limits, model multipliers from 0.04x to 2x, invoked from Jira through Rovo Chat. On the right, your own Claude Code or Codex on the plan you already pay, reading a brief, UX Studio states and evidence in one Sydla workspace at $19 per user.

One more agent, one more meter

Most lean teams already pay for a coding agent. An engineer has a Claude Pro, Max or Ultra plan for Claude Code, or a ChatGPT plan that includes Codex. Then a new tool arrives with its own agent and its own subscription. In 2026 the most visible one is Factory's Droid, which now runs from a terminal, a desktop app, Slack, Linear and, since October, from a Jira work item through Rovo Chat.

Droid is a capable agent, and Factory is clear about how it charges. The question for a small team is different: do you want a second plan with its own rate limits and multipliers on top of the plan you already have, and does it fix the part that actually slows you down? For most teams that part is not the agent. It is the brief in Confluence, the spec in Notion, the states in Figma and the decision on a Miro board, each one an MCP hop and an AI meter away. That is AI credit fatigue: many small meters and many partial views of the same feature.

This guide compares a Droid run with a Claude Code or Codex run, using Factory's pricing and docs pages and Atlassian's announcement checked on 22 November 2026.

How Factory charges for Droid in November 2026

Factory moved away from token allowances during 2026. Its pricing docs now describe managed inference governed by rolling rate limits, with model multipliers deciding how fast each request uses them.

  1. Free, $0. Bring your own inference. The pricing page says you can sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect your own API keys or a custom endpoint.
  2. Pro, $20 a month. Factory-managed inference with the desktop app, the CLI and the SDK, and full model availability.
  3. Plus, $100, and Max, $200. About 5x and 10x the usage of Pro. Factory states the multiples, not the underlying token or dollar limits.
  4. Teams, $60 a month per team plus $40 per seat. Up to 10 seats with central billing; each seat gets Pro rate limits. Business and Enterprise are custom, with SSO, SCIM, zero data retention and audit logs.
  5. Rate limits. Three rolling windows, 5 hours, 7 days and 30 days, run independently. When standard usage runs out, a free pool of open-weight models called Droid Core stays available under separate limits. You can check where you stand with /limits.
  6. Extra usage. Prepaid credits with a $10 minimum that do not expire. Missions, Droid's long-running mode, need extra usage enabled and pause when they hit a rate limit.

The multipliers matter more than the plan name. On Factory's models page, Claude Opus 5.5 counts at 1.6x, Claude Sonnet 5.5 at 0.8x, Claude Haiku 5.5 at 0.04x, GPT-5.5 at 2x and GPT-5.3-Codex at 0.7x. A team that standardises on a premium model spends its window about twice as fast as one on a mid-tier model. Some multipliers are promotional: GPT-5.6 Sol is billed at 1.6x through 22 November 2026 and returns to 2x after that, so check the page on the day you budget.

Droid, Claude Code and Codex side by side

The three agents overlap a lot in what they do: read a repository, plan, edit files, run tests and open a pull request. They differ in who sells the model access and how the limit is measured.

Monthly USD list prices for individual plans and how each agent run is metered, from vendor pages checked 18 to 22 November 2026.
AgentPlansHow a run is meteredWhere it reads the work
Factory Droid$0 BYO, $20, $100, $200; Teams $40 per seat + $60Rolling 5-hour, 7-day and 30-day limits; per-model multipliers 0.04x to 2x; extra usage prepaidRepo, plus Jira and Confluence via Atlassian MCP when started from Jira
Claude CodeClaude Pro $20, Max $100, Ultra $200Your Claude plan's usage limits; API key sessions billed as API usageRepo, CLAUDE.md, any MCP server you add
CodexChatGPT Plus, Pro, Business plansYour ChatGPT plan's limits; API key sessions billed separatelyRepo, AGENTS.md, MCP servers in config.toml
Sydla workspace$19 per userNo AI credits: it drives your own Claude Code or Codex, zero token markupBrief, criteria, UX Studio states and evidence in one MCP connection

There is a useful nuance on Factory's free tier. Signing in with ChatGPT means a Codex-capable plan can power Droid, so the model bill stays on OpenAI. The page does not offer a Claude sign-in, which fits Anthropic's rule that third-party apps may not offer claude.ai login without approval; Claude models in Droid come either through Factory's managed inference or through your own Anthropic API key. Our bring your own coding agent guide explains the three ways a run can be paid for, and our Claude Code vs Codex guide compares the two plans directly.

Droid in Jira: what the run reads

On 27 October 2026, Atlassian announced that Droid can be invoked from a Jira work item through Rovo Chat. On the first run, the engineer picks a compute environment, model settings and service accounts, which can become the defaults. Droid then pulls Jira and Confluence context through the Atlassian MCP server, runs the task, streams progress into the chat and writes results back to the work item. It runs as a Forge Remote Agent over the A2A protocol, needs Jira Cloud with Rovo enabled, and each Factory organization links to one Jira site. The Factory for Jira app on the Marketplace is free, version 4.2.0 from 8 September 2026.

That is a real improvement on a ticket-only prompt, because a Confluence spec can come along. But three meters now touch one ticket: the Factory plan for the Droid run, Rovo credits for the chat around it and any enriched MCP search, and the six seats for the tools that hold the rest of the context. Figma states, Miro decisions and Notion specs are not part of the Atlassian MCP read, so they reach the agent only if someone copies them into the ticket. Our Jira Automation coding agents guide covers the other Jira paths, and the Rovo credits guide explains pay as you go, on by default from 3 December 2026.

The six-tool stack around any agent

Whichever agent you choose, it still needs a brief, designed states, decisions and a launch visual. In a typical 2026 stack those sit in six tools, each with its own seat and AI meter.

Monthly USD list price per user, bundled AI allowance and agent handoff, from vendor pages checked 18 to 22 November 2026.
ToolSeat priceBundled AI and its limitHandoff to a coding agent
Jira Standard$9.70Rovo: 25 credits per user per month, pooled; PAYG $0.01 per credit from 3 Dec 2026Rovo Chat for Droid; Automation actions (beta)
Confluence Standard$7.15Same Rovo pool, 25 credits per userAtlassian MCP; enriched calls 1 to 10 credits
Notion Plus$12.00Custom Agents on Business and Enterprise; extra credits $10 per 1,000Notion MCP server
Figma Professional Full$20.003,000 AI credits per Full seat, no rolloverFigma MCP: 200 calls a day on Full or Dev
Miro Starter$10.0025 AI credits per license, pooled per teamMiro MCP: daily call limits by plan
Canva Business$25.00Personal AI allowance per memberOutside the build loop
Sydla workspace$19.00No AI credits: bring your own Claude Code or CodexOne MCP connection or a Sydla Desktop thread
Bar chart of monthly list price per user in November 2026: Jira $9.70, Confluence $7.15, Notion $12, Figma $20, Miro $10 and Canva $25, a combined $83.85 with six AI meters, plus a Factory Droid Pro plan at $20 with rolling limits, $103.85 in total. Against it, one Sydla workspace at $19 per user with no AI credits, using the Claude Code or Codex plan you already pay. Saving $64.85 per user per month on the tools alone.

The six tools come to $83.85 per user per month before any overage, against $19 for Sydla, a saving of $64.85. Add a Droid Pro seat and the stack passes $100 per person before a single extra-usage credit. The stack cost guide works through 5, 10 and 25 people, and the comparison overview covers each tool.

Technical walkthrough: your own agent on a shared brief and UX Studio states

Sydla takes a different route from adding another agent subscription. The context lives in one workspace, and the agent you already pay for reads it on your machine.

  1. Brief. Each ticket sits in an initiative with a versioned brief, numbered acceptance criteria and a done-means line. Every save is signed by its author, a person or an agent.
  2. UX Studio. Screens and their states, empty, loading, error and success, are designed next to the ticket and published as a handoff with tokens and a URL per state.
  3. Run. In Sydla Desktop you open the ticket, start a thread and choose claude or codex. Desktop drives the CLI you are already signed in to, so the model, the limits and the bill stay on your Claude or ChatGPT plan. Each thread has an access level, Read only, Edit files or Full access, with a Preview panel and a Changes view.
  4. Review. The agent records evidence against each criterion: test output, screenshots of each state and the diff. A person reviews it and decides the merge and release gates. An agent can request a gate but never approve one.
Two-row diagram. Top row, a Droid run from Jira: Rovo Chat on a work item, Droid on a Factory plan with rolling limits and model multipliers, Jira and Confluence context through Atlassian MCP, result written back to the ticket, while Figma states, Miro decisions and Notion specs stay outside. Bottom row, Sydla: shared brief with numbered criteria, UX Studio states, your own Claude Code or Codex in Sydla Desktop on your plan, and an evidence review where a person approves the gate.

Outside Desktop, the same context is one MCP connection away. For Claude Code, run claude mcp add with the HTTP transport and the sydla.com/mcp URL. For Codex, add an mcp_servers.sydla table to config.toml with the same URL and your key in the headers. Droid can read the same server too, since Factory supports MCP, so you do not have to pick a side to keep one source of truth. Keep the first prompt short: read the work item, list the criteria and states you will build, work on a branch and record evidence per criterion. The Desktop setup guide has every step, and the brief to pull request walkthrough follows one feature end to end.

When Droid is the right choice

Be fair to Factory. If your team wants one agent that works across many model vendors, likes to switch between Claude, GPT and Gemini models by task, and is happy to manage spend through a single Factory plan, Droid is a strong option. Missions suit long-running work, the Teams plan is simple to bill, and the free tier lets an engineer who already pays for ChatGPT try Droid without a new model bill. Enterprise buyers also get dedicated compute and on-premise options.

It is a weaker fit if your engineers already pay for Claude Max or Ultra, or a ChatGPT plan with Codex, and you mainly want the agent to stop guessing. A second subscription does not move the brief, the states or the review evidence closer to the run. Our Claude Code vs built-in AI agents guide and the AI SDLC buyer's checklist give a way to score both models.

A five-step check before you add an agent plan

Run this before adding Droid, or any other agent subscription, to the team budget.

  1. List the plans you already pay. Count the Claude and ChatGPT seats in the team. If most engineers have one, a new agent plan is a second model bill for the same work.
  2. Pick the model before the plan. Multipliers decide how fast a Droid window runs out. Price your usual model, not the cheapest one on the page.
  3. Decide the overage rule. Factory extra usage is prepaid and does not expire; Rovo pay as you go is on by default from 3 December. Set a cap on both.
  4. Check what the agent reads. Write down where the criteria, the states and the decisions live, and whether the agent can reach each without a copy and paste. Our context engineering guide has a checklist.
  5. Measure review time. If a person opens five tools to review one agent pull request, the cost is the stack, not the agent. Our 30-day migration plan shows how to move only what is alive.

Try it on your next ticket

Sydla is $19 per user per month with every feature included and no AI credits to buy. Your Claude Code or Codex plan does the coding, and the brief, the states and the evidence live with the ticket. See the pricing section, read how Sydla works, then start your workspace and keep your Claude Code and Codex accounts.

Frequently asked questions

How much does Factory Droid cost in 2026?

Factory lists Free at $0 with your own inference, Pro at $20 a month, Plus at $100 with about 5x Pro usage, Max at $200 with about 10x, and Teams at $60 a month per team plus $40 per seat for up to 10 seats. Business and Enterprise are custom. Usage is governed by rolling 5-hour, 7-day and 30-day rate limits, and prepaid extra usage starts at $10.

What are Factory model multipliers?

Each model counts against Droid's rate limits at a multiplier. On Factory's models page in November 2026, Claude Opus 5.5 is 1.6x, Claude Sonnet 5.5 is 0.8x, Claude Haiku 5.5 is 0.04x, GPT-5.5 is 2x and GPT-5.3-Codex is 0.7x. Some multipliers are promotional and change on a set date, so check the page before you budget.

Can I use my Claude or ChatGPT subscription with Factory Droid?

Factory's free tier lets you sign in with ChatGPT, GitHub Copilot or OpenRouter, or connect your own API keys. A Claude sign-in is not offered; Claude models come through Factory's managed inference on a paid plan or through your own Anthropic API key, which is billed as API usage.

Does Factory Droid work with Jira?

Yes. Since 27 October 2026, Droid can be invoked from a Jira work item through Rovo Chat. It pulls Jira and Confluence context through Atlassian MCP, runs in the compute environment you choose and writes results back to the ticket. It needs Jira Cloud with Rovo enabled, and the Factory for Jira app is free on the Marketplace.

Is there a cheaper way to run Claude Code or Codex on product tickets?

Yes. Sydla replaces Jira, Confluence, Notion, Figma, Miro and Canva in one $19 per user workspace, against $83.85 for the six tools, and runs your own Claude Code or Codex through Sydla Desktop or one MCP connection with zero token markup. The agent reads the brief, criteria and UX Studio states in one place and records evidence for a person to review.

Keep reading.

All articles

ONE WORKSPACE. THE ENTIRE SDLC.

Your next project.
One $19 subscription.

Keep using your Claude Code and Codex accounts. Bring the work into Sydla.

Get SydlaUSD / user / month · Billed monthlyProvider subscriptions remain separate.