# Amazon Q Developer Pricing: Free vs Pro Plans (2026) By Femi Adegoke · 2026-11-04 · Source: https://www.activepieces.com/blog/amazon-q-developer-pricing-free-vs-pro-plans-2026 --- ## Amazon Q Developer plans, pricing and limits ### Amazon Q Developer pricing in 2026 summary Amazon Q Developer is AWS's AI assistant for writing, reviewing and upgrading code, and it has two current plans, much as teams that also wire up routine workflows with tools like [Activepieces](https://www.activepieces.com) tend to weigh a free tier against a paid one. **Free has no per-user fee**. Pro adds a per-user monthly fee, a larger pooled allowance of Java transformation lines, and a per-line overage rate. Amazon Q Developer pricing is the structure of plan fees, usage allowances and overage charges that determines what an AWS builder pays to use the assistant, with cost driven by monthly agentic requests and Java transformation lines rather than the per-user price alone. As of 4 November 2026, the metered units, agentic requests and lines of Java transformed, decide the bill, not the plan price. Nothing is charged on Free, but the monthly allowance of agentic requests is capped, and each user gets a small monthly allowance of Java transformation lines. It has no overage, so the cap is the stop. ![A wall stopping a jug at a low mark](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/ec3d2423-d888-4753-a79b-1183b29ed4d4/amazon-q-developer-pricing-free-vs-pro-plans-202-d8b6fcee.webp) ### Free tier: what you get and where it stops You will hit the monthly agentic-request limit on Free as soon as the assistant is doing multi-step work instead of single completions, since Free costs nothing per user. According to the AWS pricing page, **Free includes about 50 agentic requests a month**. Each request is one metered unit: one instruction that sends the agent off to plan and carry out a task, however many files it reads or edits along the way. A long task that spawns several steps still draws on the month's allowance, so a handful of ambitious jobs can use it up faster than the number of chats suggests. One large legacy module can consume the second ceiling in a single run. The Java transformation allowance counts lines of code per user. Once either meter runs out, you wait for the monthly reset or move to Pro. ### Pro tier: per-user price and included allowances If you are pricing Pro, start with the flat monthly fee for each user, which includes agentic requests up to a limit, so the fee buys headroom, not unlimited use. When one engineer migrates a large codebase and the rest barely touch the feature, a team can still stay inside the allowance, because the Java transformation allowance pools across the account. Past the pool, AWS bills every extra line at the overage rate. A single big migration therefore moves the invoice more than adding a seat does, which is why the next section sizes the plan by monthly transformation volume. ## What one developer pays monthly for Q Developer $19 on Pro in a quiet month, $37 in a 10,000-line month: that is what Priya pays, so her month-to-month costs vary significantly depending on refactoring intensity. ![What one Q Developer Pro seat costs at different transformation volumes](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/db432112-8fa3-4ab9-998b-1c929b2a5cf1/amazon-q-developer-pricing-free-vs-pro-plans-202-27c80e43.svg "Source: AWS") She's a solo developer doing feature work, code review and Java upgrades, and Free would cost her $0 but stop at 1,000 transformed lines, meaning she'd hit the ceiling very quickly. ### Light month on the free tier For her, seats are not the meter that matters; lines of Java transformed are. According to AWS, Free includes 1,000 lines a month, so a small upgrade of 800 lines costs her nothing. Her feature work and review don't change that. The first sizeable migration is what pushes her past the allowance. ![Activepieces pricing page displaying four subscription tiers with features and costs.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/841ec84e-02e4-4761-aca2-e92f6d457f41/self-host-mistral-ai-enterprise-deployment-guide-c7d7dca9.webp) ### Q Developer Pro cost in a heavy month Say she upgrades 10,000 lines in one month. The bill runs in this order: 1. Pro seat: $19. 2. Java lines used against the 4,000-line allowance: 10,000 lines, so 6,000 are over. 3. Per AWS, overage: 6,000 lines × $0.003 = $18, which means significant refactoring projects quickly accumulate overage charges at this per-line rate. 4. AWS's total: $19 + $18 = [$37 per month](https://aws.amazon.com/q/developer/pricing/), putting her Pro plan at **nearly double the cost when refactoring volume surges**. ![Invoice with Pro seat, Java lines allowance and overage pile](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/c79aaa47-49d5-4b03-97c4-c014bbecccf7/amazon-q-developer-pricing-free-vs-pro-plans-202-c613e93e.webp) Run the same upgrade on Free and the allowance is 1,000 lines. The tier costs $0, but 9,000 of the 10,000 lines never get transformed, so she would have to wait for the next month or upgrade. Pro totals $37 for all 10,000. A month of 2,000 lines costs [$19](https://aws.amazon.com/q/developer/pricing/), the flat seat price, because it sits inside the 4,000-line allowance. ### Q Developer Free vs Pro break-even point Free's the cheaper plan only while she stays at or under 1,000 lines. Past that, Pro's the only choice for finishing the job, and its price is flat up to 4,000 lines. ![A 6-step Activepieces workflow automation canvas for monitoring competitor pricing with configuration panels and test…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/5c891d44-7e19-424e-8a02-c3157d493bff/gorgias-pricing-2026-plans-tickets-and-overages-6bf27971.webp) At 50,000 lines she owes [$157](https://aws.amazon.com/q/developer/pricing/), and at 100,000 lines [$307](https://aws.amazon.com/q/developer/pricing/). Of the first figure, $138 is overage, and of the second, $288, so the seat's under 13% of the bill at 50,000 lines and about 6% at 100,000. The next chart plots that climb from $19 to $307, to show that the seat price barely moves the total and the transformation volume does. ## Discover hidden costs and limits on Q Developer Two limits change your bill: the monthly agentic request cap and the pooled transformation allowance. The $19 seat price is a per-user monthly subscription, while the transformation allowance is counted separately in lines of code. ![A price tag beside a box with unlabelled dials](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/5899ef00-902e-448c-9b72-f70b6555cd7d/amazon-q-developer-pricing-free-vs-pro-plans-202-ebfb3c17.webp) ### Q Developer agentic request limits per month Each time the assistant takes a multi-step action on your behalf, such as reading files, editing across a project or running a task, it draws from a monthly cap. A seat price tells you who can log in; the cap tells you how many of those jobs you get. The AWS pricing page puts the Free cap at about 50 agentic requests a month. Pro is different in kind: it has a much higher per-user limit, and the pricing page lists it as a figure to check at purchase, since AWS adjusts it. Pro also pools differently from transformation, because the request limit is set per user, not shared across the account. Here is a worked example. Say your team's typical multi-step task, such as adding a feature across several files, takes about 5 requests once you count the follow-up corrections. At about 50 requests a month, Free fits roughly 10 such tasks, which is two or three a week. A builder who runs one every working day, around 20 a month, needs about 100 requests and is over the Free cap by the second week. If your builders lean on agents daily, the cap, not the seat, is the number to divide your workload by. ### Q Developer code transformation limits per account AWS bills transformation per line of code and pools the allowance across the account instead of giving each person their own. The [AWS pricing page](https://aws.amazon.com/q/developer/pricing/) lists 1,000 lines of Java transformation per month on the Free tier, which covers a small utility module and not much more. ![Java transformation lines included each month, by plan size](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/e6019405-114d-4d98-97f0-bf76b21047f0/amazon-q-developer-pricing-free-vs-pro-plans-202-ee090b1a.svg "Source: AWS") Start with one Pro seat: it includes 4,000 lines, so a single developer can move a mid-sized service before the meter starts. Ten Pro seats pool 40,000 lines, which means the team's allowance grows with headcount but everyone shares it, so one big migration can drain what everyone else expected. Against 40,000 included lines, a 100,000-line upgrade leaves 60,000 lines billed individually beyond the allowance. Adding seats to cover that is a poor trade, because each seat adds only 4,000 lines. ### Q Developer Pro account and sign-in requirements You cannot start on Pro from a code editor alone. It runs through an AWS account and sign-in managed with IAM Identity Center, AWS's service for assigning people to applications. That means a solo builder who only had a code editor installed now needs an AWS account and an identity setup before the first paid seat works. Budget an admin's afternoon: the cost isn't on the invoice but in the hours, and you should expect the work to repeat each time you add a contractor who needs access. ## How Q Developer pricing compares to competitors Q Developer Pro costs $19 per seat per month, the same as Copilot Business and $9 more than Copilot Pro, so seat price alone won't separate them. ### Price and limit per plan The table lists the paid seat prices from [GitHub Docs](https://docs.github.com/en/copilot/concepts/billing-and-usage/organizations-and-enterprises/seats-and-billing-cycles) next to Q Developer Pro. Read it for the gap between tiers: Q Pro sits in the middle of Copilot's range, not at the bottom. ![Where Q Developer Pro sits among Copilot's paid seat prices](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/7b56ba45-2369-43d2-8871-8ea0f3cfc92d/amazon-q-developer-pricing-free-vs-pro-plans-202-075af050.svg "Source: GitHub Docs") | Plan | Price per seat per month | Source | |---|---|---| | Copilot Pro | $10 | GitHub Docs | | Q Developer Pro | $19 | GitHub Docs comparison | | Copilot Business | $19 | GitHub Docs | | Copilot Pro+ | $39 | GitHub Docs | At $10, Copilot Pro is cheaper than Q Developer Pro, and Copilot Business costs the same $19, so you can't rely on a Q cost advantage when choosing this tier. Ten seats cost $90 a month more on Q Pro, or $1,080 a year, and that's the premium you pay for whatever Q's pooled agentic and transformation allowance gives you. Copilot Pro+ at $39 is $20 above Q Pro, so Q undercuts it on sticker price, but only if your monthly agentic volume stays inside Q's caps. [Cursor](https://cursor.com/docs/account/teams/pricing) and Claude Code bill on their own plan structures and aren't priced in this table, so check their pricing pages before comparing them with these four lines. The table shows the price of access, not the price of use. Copilot and Q both meter work separately from the seat, so the $19's a floor. ### Which one fits which workload Match the plan to what your team runs each month, not to the seat price. For light use, mostly autocomplete and chat, Copilot Pro at $10 is the cheapest paid seat here, and nothing in your usage will test its limits. If you run regular agentic tasks or code transformation across a codebase, Q Pro at $19 is worth pricing first, because its pooled overage rules let heavy and light users share one allowance across seats. For a team already on Copilot Business, Q Pro has no price advantage at $19, which means price will not drive switching decisions among Copilot users. Switch only if your measured agentic or transformation volume would otherwise push you past Copilot's caps. Pro+ at $39 costs $20 more per seat than Q Pro, which is $240 a year per person, and this premium scales with every developer you upgrade. Count your agentic and transformation runs for one month, then price each plan against that count. ## Choose between Q Developer Free and Pro **Pick Free if last month's agentic requests and transformed Java lines both fit under its caps; pick Pro if either one doesn't.** The two meters decide the plan, and the sticker price doesn't. Q Developer meters two things that matter here: agentic requests, meaning each time the agent works through a multi-step task on your behalf, and lines of Java code run through the transformation tool. Four steps, in this order: 1. Pull last month's agentic request count and the number of Java lines you transformed. Take them from your own logs or the account's usage view, not from memory. 2. Compare both counts against the Free caps: about 50 agentic requests and 1,000 Java lines a month. If you're under both, take Free. If either's over, take Pro. One meter over's enough, because you can't trade the other meter's headroom against it. 3. Set an AWS Budgets alert on the account that holds the subscription. Pro pools overage, so one heavy user can spend what the rest of the team assumed was theirs. The alert's what tells you before the invoice does. 4. Recheck the pricing page before you commit. Caps and overage rules are the parts of the page that change. Run the sequence again whenever a migration or a new agent-heavy project changes your volume, since the right tier follows the workload and not the calendar. One adjacent cost is worth keeping out of this decision. Routing review results into tickets or chat is workflow glue, and [Activepieces](https://www.activepieces.com/pricing) can handle that job; its prices are listed on its own pricing page, separate from anything you pay AWS. ## What Activepieces does about this Q Developer's meters count agentic requests and transformed lines. Activepieces is the automation that triggers and routes that work, and it meters one thing: runs. A flow costs 1 credit however many steps it has, and the free plan includes 1,000 credits a month with unlimited flows. So you can size the AWS plan on its two meters and treat the automation as a separate, flat line. Splitting a review-notification flow into small steps adds nothing to that line. The core is open source under the MIT licence, so you can self-host it. Hosted prices are on the [Activepieces pricing page](https://www.activepieces.com/pricing). ## When Zapier and Make beat Q Developer pricing Zapier and Make are not the weaker tools here; they win on criteria that matter. Zapier has one of the widest catalogues of app connections and a long record of support, so a flow that touches an obscure SaaS product is likelier to find a ready-made step there. Make's visual scenario builder shows branching and data reshaping as a diagram, which many teams find easier to read and review than a linear editor. On the same meter, per-task and per-module billing costs more as you split a flow, but a short flow with few steps pays little for it. If connector coverage or a visual canvas outweighs a flat per-run credit, either is a reasonable choice, and you should price your real flow shapes on each before deciding. ## Frequently asked questions ### Is Amazon Q Developer free for commercial use? Yes, the free tier can be used on work projects. What limits it is the monthly metering of agentic requests and code transformation, not a licence restriction on commercial code. If your team's usage outgrows the free allowance, the cost's the Pro subscription, not a legal problem. Before you put proprietary code through the free tier, read the current service terms, because the data-handling and IP protections differ between free and Pro. ### Does Amazon Q Developer Pro include a free trial? Whether a trial applies to your account, and how long it lasts, is shown at subscription time, though AWS has offered trial periods on Pro for new subscribers. The free tier is the safer way to test: you can run your real agentic and transformation workload against its caps and see how fast you reach them before paying per user. ### Can I cancel Amazon Q Developer Pro mid-month? Yes, you can remove a user's subscription at any time, and charges for that seat stop from then on. Don't assume a refund or proration for the month already started. The metered unit is the seat-month, so a seat removed on day ten of a billing month may still have been paid for in full. ### Does Q Developer pricing change by AWS region? Don't expect a different sticker price by location: the headline Pro price is quoted per user, not per region. Where the region matters is operationally. Pro subscriptions are managed through your AWS identity setup, and that setup lives in a specific region, so decide where it sits before you roll out seats to a distributed team. Check your own billing console for any regional difference in how overage is shown. ## Related reading - [Sentry Pricing 2026: Developer, Team, Business Plans](https://www.activepieces.com/blog/sentry-pricing-2026-developer-team-business-plans) - [Amazon Lambda Pricing: Cost Breakdown for 2026](https://www.activepieces.com/blog/amazon-lambda-pricing-cost-breakdown-for-2026) - [Amazon SNS Pricing: Cost Per Message (2026 Guide)](https://www.activepieces.com/blog/amazon-sns-pricing-cost-per-message-2026-guide) ## References - [AWS](https://aws.amazon.com/q/developer/pricing/) - [GitHub Docs](https://docs.github.com/en/copilot/concepts/billing-and-usage/organizations-and-enterprises/seats-and-billing-cycles)