Amazon Q is AWS's family of generative-AI assistants. The confusing part — and the thing this page exists to fix — is that one name covers two very different products: Q Developer, an AI coding assistant for engineers, and Q Business, an assistant that answers employees' questions over your company's own data. This page explains what each one actually is, the problem each solves, where they show up, how they relate to Amazon Bedrock under the hood, who they're for, and how to start — no prior AWS background assumed.
If you only read one paragraph: Amazon Q is AWS's brand for ready-made generative-AI assistants — finished products you can use out of the box — and it comes in two flavours, one that helps engineers write and operate code (Q Developer) and one that answers employees' questions over your company's own data (Q Business).
The single most important thing to understand about Amazon Q is that the name covers two separate products with different buyers, different surfaces, and different pricing. AWS describes Q as "the most capable generative-AI assistant for accelerating software development and leveraging your enterprise data." That one sentence already contains both products: "accelerating software development" is Amazon Q Developer, and "leveraging your enterprise data" is Amazon Q Business. They share a brand and a security posture — not a use case.
A generative-AI assistant, in plain terms, is software you ask questions in natural language and that answers in natural language — like ChatGPT, but built into a specific place to do a specific job. Q Developer's job is to sit inside the tools engineers already use and help them write, fix, test, and upgrade code. Q Business's job is to sit on top of your company's documents and let any employee ask "what's our refund policy?" or "how do I file an expense?" and get a cited answer drawn from internal sources.
The word that does the most work in the definition is "ready-made." Amazon Q is a finished assistant, not a toolkit. You do not assemble it from models and prompts the way you would if you built your own AI feature — AWS has already done that assembly and handed you a product you log into or install. That is the line that separates Q from Amazon Bedrock, AWS's service for building your own AI applications, which we come back to in section V.
It is worth saying what Amazon Q is not, because the name gets misused. Q is not a single model you choose and tune — AWS manages the models for you. It is not a build-your-own-AI platform (that is Bedrock). It is not a low-level machine-learning platform for training models from scratch (that is Amazon SageMaker). Amazon Q is the layer above all of those: the off-the-shelf assistant you reach for when you want results today rather than a project to build.
Q Developer = AI coding assistant for engineers (code editor, terminal, AWS console). Q Business = assistant that answers questions over your own company data (with citations, across ~40+ connectors). Same brand, same Bedrock-backed security posture, completely different jobs. When in doubt, ask "Developer or Business?" first.
This is the section that prevents the most confusion. Read it once and almost every other Amazon Q question answers itself. The two products diverge on who buys them, where they run, what "good" looks like, and how they're priced — and they overlap only on the brand and the security guarantees.
The reason the distinction matters so much in practice: conflating the two leads to the wrong pilot, the wrong budget line, and the wrong success metric. An engineering leader who pilots "Amazon Q" expecting a coding assistant but stands up Q Business will be disappointed — and vice versa. So before any other detail, lock in which product you mean.
What it is, in plain terms: an AI pair-programmer that lives inside the tools engineers already use. You type a comment or a function name and it suggests the code; you ask "why is this failing?" and it explains; you ask it to add a feature and it can write across several files.
Who it's for: software engineers, platform teams, and the engineering leaders who buy tools for them.
Where it runs: inside your code editor (VS Code, the JetBrains editors like IntelliJ and PyCharm, Visual Studio, Eclipse), in the command-line terminal, and inside the AWS Management Console as an on-hand helper for AWS questions and troubleshooting.
The problem it solves: engineers spend a large share of their time on boilerplate, repetitive edits, writing tests, reading unfamiliar code, and slow, risky framework upgrades. Q Developer compresses that toil — it completes code as you type, answers "how do I…" without a context switch to a browser, generates tests and docs, and can run guided upgrades (for example, moving a codebase to a newer Java version). Because it also understands AWS, it can reason about your cloud architecture, not just generic code.
For the full feature list, editor setup, and the per-tier breakdown, see the dedicated Amazon Q Developer guide.
What it is, in plain terms: "ChatGPT, but it knows everything in our company's documents — and only tells each person what they're allowed to see." Employees ask a question in plain English; Q Business finds the relevant internal documents and answers, showing which source each answer came from.
Who it's for: CIOs, IT teams, knowledge-management and internal-operations leaders — anyone responsible for helping employees find answers.
Where it runs: a web app employees log into (usually through your company sign-on), an embeddable chat widget for an intranet, browser extensions, and a Slack/Microsoft Teams integration. It is not a coding tool and does not live in a code editor.
The problem it solves: company knowledge is scattered across SharePoint, Confluence, Salesforce, ServiceNow, Google Drive, shared S3 buckets, and dozens of other systems. Employees waste time hunting for answers, and the help desk answers the same questions over and over. Q Business connects to those sources, indexes them, and answers questions with citations back to the source document — while respecting each user's existing permissions, so an employee only ever sees answers from documents they were already allowed to read.
For connector lists, the index sizing model, permission handling, and admin setup, see the dedicated Amazon Q Business guide.
| Dimension | Q Developer | Q Business |
|---|---|---|
| In one line | AI pair-programmer for engineers | Cited answers over your company data |
| Primary job | Write, fix, test & upgrade code | Answer employees' questions from internal docs |
| Who buys it | Engineering / platform teams | CIO / IT / knowledge management |
| Where it lives | Code editor, terminal, AWS console | Web app, Slack/Teams, intranet widget |
| What it reads | Your codebase + AWS account | ~40+ enterprise data connectors (RAG) |
| Pricing shape | Free / Pro (~$19/user/mo) | Lite (~$3) / Pro (~$20) + index cost |
| Trains base model on your data? | No | No |
It helps to see Amazon Q not as one product with two modes, but as AWS answering two separate, expensive problems with the same brand. Understanding the problems makes the products obvious.
Both problems are about turning generative AI into something usable without a build project. Plenty of teams want AI help but do not want to assemble it from raw models, prompts, and infrastructure. Q is AWS's pre-assembled answer for two of the most common wants: better coding, and answers over internal knowledge.
A large fraction of engineering time goes to work that is necessary but not creative: writing boilerplate, wiring up tests, reading code someone else wrote, looking up syntax and AWS service options in a browser, and slow framework or language upgrades that nobody wants to own. None of it is the hard, interesting part of the job — but it eats the calendar.
Q Developer's premise is that a model sitting inside the editor, with awareness of your code and your AWS account, can absorb most of that toil: complete the obvious next lines, explain an error in place, generate the test you were going to write anyway, and execute a guided upgrade across the codebase. The win is measured in less boilerplate, faster time-to-merge, and upgrades that actually happen instead of lingering on a backlog.
In most companies, the answer to a routine question already exists in writing — it is just buried in one of a dozen systems, behind a search box that does not work very well, and possibly in a document the asker is not allowed to open. So employees interrupt colleagues, file help-desk tickets, or simply guess. The cost is slow answers, repeated tickets, and inconsistent information.
Q Business's premise is that an assistant connected to all those sources at once can answer the question directly, in plain language, with a citation so the employee can trust and verify it — and crucially, while honouring the permissions that already exist, so it never surfaces a document the asker was not entitled to see. The win is measured in deflected support tickets, faster time-to-answer, and one consistent source of truth instead of a dozen.
Both halves of Amazon Q exist so a team can get real generative-AI value without building an AI application. Q Developer pre-packages "AI help where I write code"; Q Business pre-packages "AI answers over our own documents, safely." If you instead want to build a custom AI feature into your own product, that is Amazon Bedrock's job — see section V.
Part of what makes "Amazon Q" feel slippery is that it appears in a lot of places. Here is the full footprint in plain terms, so nothing surprises you — grouped by which product (or service) it belongs to.
The simple pattern to hold onto: Q Developer appears wherever engineers work, Q Business appears wherever employees ask questions, and a few other AWS services embed a "Q" feature inside themselves. Only the first two are products you license per seat; the embedded ones come bundled with their host service.
You do not need this section to use Amazon Q, but it answers the question every technical reader eventually asks — "what is Q actually running on?" — and it explains both the security story and the relationship to the rest of AWS's AI stack.
Amazon Q is built on Amazon Bedrock. Bedrock is AWS's managed service for foundation models — the big general-purpose AI models from providers like Anthropic (Claude), Meta (Llama), Mistral, and Amazon (Nova and Titan). When you call Bedrock directly, you pick which model to use and you build your own application around it. Amazon Q sits one layer up: it calls models on Bedrock for you and manages the model choice itself. That is the key difference — with Bedrock you choose the model; with Q you choose the product and the tier, and AWS handles the model behind the scenes.
Why that matters for trust: because Q runs on Bedrock, it inherits Bedrock's data guarantees. Your prompts, your code, and the documents Q Business indexes are not used to train the underlying foundation models, are not shared with the model providers, and stay within AWS's security boundary. This is the same property that makes Bedrock attractive to regulated and enterprise buyers, handed down to Q for free.
How Q Business actually answers from your data is worth a plain-English line, because it is the cleverest part. It uses a technique called retrieval-augmented generation (RAG): Q Business first loads your documents into a managed index (a searchable store), then, when someone asks a question, it retrieves the most relevant passages and hands them to the model as context so the answer is grounded in your content — and it cites the documents it used. That is why Q Business can answer about your specific policies without that information ever being baked into a model. If you wanted to build that retrieval pipeline yourself instead of buying the finished product, you would reach for Bedrock Knowledge Bases or roll your own RAG on AWS.
The relationship in one sentence: Bedrock is the engine room (raw models and building blocks you assemble), and Amazon Q is the finished vehicle (an assistant AWS has already assembled for a specific job). Choosing between them comes down to a single question — do you want to build an AI feature, or do you want to use a ready-made assistant? That trade-off is the whole table below.
| AWS service | What it is, in plain terms | You choose… | Reach for it when… |
|---|---|---|---|
| Amazon Q Developer | A ready-made AI coding assistant in your editor/terminal/console | The product + tier | You want AI help writing and operating code today |
| Amazon Q Business | A ready-made assistant that answers over your company data | The product + tier | You want "chat with our docs" without building it |
| Amazon Bedrock | A managed API to many foundation models + building blocks | The model + how you build | You're building a custom AI feature into your own product |
| Amazon SageMaker | The full ML platform to build, train & deploy models at the lowest level | Everything (models, training, serving) | You need to train custom models or control the stack |
Being honest about fit is part of being a useful reference. Amazon Q suits a lot of teams, but not every situation — and because it is two products, "fit" has to be answered twice.
Q Developer fits you well if: you have engineers who want AI help inside their editor; your stack leans on AWS (so the AWS-awareness pays off); you value managed code upgrades and want central license and policy control across a team. Individual developers can start entirely free.
Q Business fits you well if: your company's knowledge is spread across many systems; you want employees to self-serve answers with citations; your data and security perimeter already live in AWS (or you want them to); and per-user permission enforcement is a hard requirement rather than a nice-to-have.
Amazon Q may be off-target if: you want to build a custom AI feature into your own product with full control of the model and prompts — that is Amazon Bedrock, not Q. If you need to train a brand-new model from scratch or control the serving stack, that is Amazon SageMaker. And if all you want is a personal chatbot to talk to, a consumer product like ChatGPT or Claude.ai is simpler than standing up an enterprise assistant.
A useful way to place the people who get the most from each: Q Developer is for engineers and the leaders who equip them; Q Business is for CIOs, IT, and knowledge-management teams serving the whole organization. You do not need data scientists or ML experts to adopt either — both are designed to be used, not assembled.
Ask: (1) "Is this for engineers writing code, or employees asking questions?" → Developer vs Business. (2) "Do I want a finished assistant, or to build my own AI?" → Q vs Bedrock. Two questions place almost everyone correctly.
Both products start free or small and scale per seat. This is the plain-English version; the full per-tier detail lives on the dedicated product pages and the flagship Amazon Q guide. Figures below are representative as of 2026 — always confirm current rates on the AWS pricing page, since AWS adjusts tiers periodically.
Amazon Q Developer is the simpler of the two: a Free tier that gives an individual developer inline suggestions, chat, and a capped amount of the heavier features (multi-file agent runs and security scans) at no cost, and a Pro tier at roughly $19 per user per month that raises those limits and adds central license management and policy controls for a team. A few advanced actions, such as large-scale code transformations, can add a little usage-based cost on top of the seat — but for most developers the seat fee is the whole story.
Amazon Q Business has two seat tiers plus one extra line item people often forget. The seats: Lite at about $3 per user per month for lighter ask/answer usage, and Pro at about $20 per user per month for the full feature set (including Q Apps). The extra item is the index — the store that holds and serves your documents — billed by capacity sized to how many documents you have and how much querying you do. So the mental formula is: Q Business bill = (seats × tier) + (index capacity). For a small pilot the index is modest; for an enterprise indexing millions of documents it becomes a meaningful share, so size it to real volume rather than over-provisioning on day one.
The headline for budgeting: you can try Q Developer for free and pilot Q Business cheaply, but a production Q Business rollout — many connectors, identity wiring, permission mapping, a right-sized index, guardrails — is a real engagement. That is precisely the kind of build AWS credits are designed to cover, which is why this explainer sits alongside CloudRoute's offer rather than ending at "go sign up."
AWS funds generative-AI builds through credit programs — Activate (up to $100K), a dedicated Bedrock / GenAI proof-of-concept pool ($10K–$50K), and the GenAI Accelerator (up to $1M for selected startups). CloudRoute routes you to the right pool and a vetted AWS partner to build the Q Business deployment — the customer pays $0; AWS funds the engagement and the partner pays CloudRoute.
The fastest path depends entirely on which product you need — so pick the column first, then follow the steps. Both start free or small; the difference is that Q Developer is a same-afternoon install, while Q Business is a small project worth scoping deliberately.
The smarter path if you intend to ship Q Business — and want it funded. A real Q Business rollout means wiring up many connectors, mapping permissions correctly across sources, sizing the index, configuring guardrails, and managing the change across departments. Before you spend your own money and engineering time on that, it is worth knowing AWS will frequently fund the build with credits. Those credit pools are largely partner-filed — requested through the AWS Partner Network rather than a public form — which is why most teams route through a partner. CloudRoute matches you to the right credit pool for your stage and to a vetted AWS partner who can both file the credit application and build the deployment. The customer pays $0; AWS funds the credits and the partner pays CloudRoute a routing commission. The next section is a real, anonymized example of exactly that.
Install the Amazon Q extension in your code editor (VS Code, a JetBrains editor, Visual Studio, or Eclipse) or set up the command-line version. Sign in with a free Builder ID to use the Free tier immediately — you do not even need an AWS account to try it. When you want to roll it out across a team on the Pro tier, set up subscriptions through AWS IAM Identity Center so licenses, limits, and policies are managed centrally. From "install" to "first useful suggestion" is usually a matter of minutes.
In the AWS console, create a Q Business application, connect it to your identity provider through IAM Identity Center (so it knows who each user is and what they're allowed to see), then add one or two high-value data sources first — SharePoint or Confluence are common starting points. Size the index, set guardrails and access controls, and share the web experience with a small pilot group before expanding. Because Q Business touches data, identity, and security all at once, most teams deliberately scope a focused pilot rather than connecting everything on day one.
Because Q spans two product categories, it gets compared to two different sets of tools. This is the plain-English placement; the deep, number-by-number coding head-to-head lives on the dedicated Amazon Q vs GitHub Copilot page.
| Tool | Category | Best when | Pricing shape | Your data trains the base model? | Standout strength |
|---|---|---|---|---|---|
| Amazon Q Developer | AI coding assistant | AWS-heavy stack; want managed code upgrades | Free / ~$19 per user/mo | No | AWS awareness + guided code transforms |
| Amazon Q Business | Assistant over company data | Data & security perimeter live in AWS | ~$3 / ~$20 per user/mo + index | No | Per-user permissions + 40+ connectors in your account |
| GitHub Copilot | AI coding assistant | GitHub-centric teams; broadest editor + model choice | ~$10–$39 per user/mo | No (Business/Enterprise) | Market-leading ecosystem & adoption |
| Microsoft 365 Copilot | Assistant over company data | Standardized on Microsoft 365 | ~$30 per user/mo | No | Native Microsoft 365 grounding |
| ChatGPT Enterprise | General assistant | Want top raw model quality + flexibility | Custom / per-seat | No | Frontier model quality, broad tooling |
Situation: Operations and support staff burned hours every week hunting for the same answers — carrier rules, SOPs, customer-specific exceptions — scattered across Confluence, SharePoint, and a large S3 archive of PDF policy documents. The team had read about "Amazon Q" but were unsure which product they even needed, and the security team had a hard line that the operational data could not leave the company's AWS perimeter for an external assistant. They wanted one assistant grounded in all their sources, with strict per-user permissions — and they had no internal team free to build it.
What CloudRoute did: CloudRoute clarified the fit in the first call — this was a Q Business need, not Q Developer — and matched them within a day to an AWS Advanced-tier partner with IAM Identity Center and Q Business experience. CloudRoute helped the partner file for AWS credits to fund the work: a Bedrock/GenAI proof-of-concept pool to cover the pilot, with Activate Portfolio credits behind it for the broader AWS spend. The partner stood up a Q Business application, federated identity to the company's existing provider, connected Confluence, SharePoint, and the S3 archive, mapped permissions so each role only saw entitled documents, and set guardrails before a 50-person pilot.
Outcome: The pilot answered roughly three-quarters of routine operational questions with citations inside four weeks; the company expanded to about 450 Pro seats the following quarter. Approximately the first $35K of AWS consumption across the pilot and rollout was credit-funded. CloudRoute's commission was paid by the partner out of AWS's engagement funding — the customer paid $0 to CloudRoute.
fit clarified: call 1 · pilot window: 4 weeks · seats at expansion: ~450 · credit-funded AWS spend: ~$35K · cost to customer: $0
You bring the use case. CloudRoute routes you to a vetted AWS partner who builds Q Business — connectors, identity, permissions, guardrails — and helps secure AWS credits to fund it. Customer pays $0. AWS funds the engagement.