Understand Amazon Q Business and Developer, current availability changes, the Amazon Quick path, pricing, permissions, privacy, and practical workflows.
Amazon Q is a family of AWS assistants, not one general-purpose chatbot. Q Business helps employees work with organizational knowledge. Q Developer helps with software development and AWS tasks.
There is an important update for anyone evaluating it in 2026: Amazon Q Business is closed to new customers, while existing customers can continue using the service. AWS points new business users toward Amazon Quick. Q Developer also has a published end-of-support date for its IDE plugins.
This guide explains the products, current pricing, privacy distinctions, and how to evaluate an existing deployment without overlooking those changes.
Official documentation checked October 9, 2026. Belliste has not conducted an original hands-on benchmark. Named contributor opinions below are attributed and identified as AWS-published commentary.
AWS's product comparison separates two main jobs:
| Product | Main use | Typical user |
|---|---|---|
| Amazon Q Business | Enterprise search, document questions, content, and supported actions | Employees using company knowledge |
| Amazon Q Developer | Coding, debugging, security review, documentation, and transformations | Developers and AWS operators |
Q Business retrieves information from connected organizational sources and considers user permissions. Q Developer works closer to code and development environments.
A Developer subscription does not automatically provision an enterprise knowledge index. Likewise, a Business seat does not give you every developer capability.
For existing customers, yes. For a new customer, the relevant answer is different.
The official API documentation states that Q Business stopped accepting new customers on July 31, 2026. It directs users seeking similar capabilities to Amazon Quick.
The Business pricing page says existing customers can continue using Q Business or use their existing index with Quick Suite.
Do not follow an older “create your first Q Business application” tutorial without checking your account's eligibility. The service's continuing documentation is not proof of unrestricted new enrollment.
The Q Developer product page announces that AWS will discontinue support for its IDE plugins on April 30, 2027, directing users to Kiro for similar capabilities.
That notice specifically names IDE plugins. It should not be rewritten as a claim that every Amazon Q product has already shut down.
If your team depends on the plugins, include migration planning in the evaluation. Confirm the current status of the exact environment and feature before standardizing a new workflow.
Q Developer starting price: Free $0/month · Pro from $19/user/month.
Its official pricing page lists a Free tier with 50 agentic requests per month and a $19 per-user monthly Pro tier with expanded limits.
For existing Business customers, the published seat prices are:
| Q Business option | Listed price | Additional consideration |
|---|---|---|
| Lite | $3/user/month | Index capacity is separate |
| Pro | $20/user/month | Broader capabilities; index capacity is separate |
| Starter index | $0.140 per unit/hour | Proof-of-concept-oriented index |
| Enterprise index | $0.264 per unit/hour | Production-oriented index |
These Business rates are for an existing-customer service, not an invitation to new enrollment. Check region, consumption, processing, connector, and related charges before budgeting.
An index can incur charges even when employees are not chatting. On a 730-hour month, one Starter unit is approximately $102.20, and one Enterprise unit is approximately $192.72, before seats and other costs.
Those are arithmetic examples, not a complete AWS quote. A low per-user price can be misleading when the infrastructure cost is omitted.
An existing deployment can support questions such as:
The usefulness depends on the connected content. An assistant cannot reliably identify the current policy if the index contains several conflicting versions without clear ownership.
Before changing models or prompts, check document freshness, source quality, and permissions.
AWS's product comparison includes commentary from Oleksii Bebych, identified as a re:Post Top Contributor. He emphasizes that Q Business connects organizational sources while respecting access controls.
The same page attributes to Gary McLean, also a re:Post Top Contributor, a view of Q Developer that goes beyond completion: code transformation, tests, and security review.
These are named opinions published by AWS, rather than independent Belliste test results. They illustrate two different priorities: knowledge access for employees and code changes for developers.
Our editorial takeaway is to verify each on its own terms. For Business, test whether the right person sees the right evidence. For Developer, inspect and test the actual change.
Choose a question with a known answer in a current document. Define the expected source and what information must remain inaccessible.
Use representative user accounts with different access levels. A successful administrator query does not establish that employee permissions are correct.
Confirm the source was synchronized, the relevant text is searchable, and the document's access metadata is accurate.
Request citations and the effective date of a policy or procedure. Distinguish an answer drawn from organizational material from a general suggestion.
Use an outdated document, conflicting versions, a missing answer, and a question involving restricted material. The assistant should handle uncertainty rather than invent an internal policy.
For an action-enabled workflow, inspect the destination, content, and permissions before completing it. A correct answer does not prove that an external action is appropriate.
Record accuracy, source coverage, employee correction time, and infrastructure cost. Also review the migration path to Amazon Quick.
Start on a small repository or task you understand. Ask it to explain a failure before changing code. Give a bounded objective and relevant project context.
Inspect the resulting diff, run meaningful checks, and verify that the change does not introduce unrelated behavior. Review any dependency, command, or deployment suggestion before adopting it.
For a transformation, assess compatibility and behavior after the upgrade, not just whether the tool produced newer syntax. Include the IDE plugin deadline in your planning.
For business knowledge:
Question + Authorized sources + Scope + Evidence requirement + Format
> Using the current approved travel policy, summarize reimbursement rules for a three-day domestic trip. Cite the relevant sections and effective date. If meal limits or exceptions are missing, say so instead of inferring them.
For document analysis:
> Compare these reports. Separate changed figures from changed wording, cite the source sections, and identify contradictions requiring an owner to resolve them.
For developer work:
Observed behavior + Expected behavior + Scope + Constraints + Verification
> Investigate why this endpoint returns a server error for an empty request. Explain the cause, propose the smallest fix, preserve the API contract, and run the relevant checks. List any unresolved behavior.
AWS's Q Business getting-started guidance says customer data is not used for service improvement or improving underlying language models.
Developer has different tier rules. The service-improvement documentation describes possible use of Free-tier content, including model training, with opt-out mechanisms.
The IDE opt-out guide says Pro does not collect content for that sharing purpose and provides controls for Free users. The applicable opt-out depends on the environment; IDE controls and AWS Organizations policies are different routes.
Do not translate these statements into “nothing is stored” or “no telemetry.” Review retention, regional processing, operational logging, and organizational requirements separately.
A perfectly written answer can still be wrong for the recipient if it exposes restricted information. A permissions test therefore belongs alongside factual testing.
Check direct queries, follow-ups, citations, and any generated summary involving protected documents. Repeat the test after source-permission or identity changes.
Also verify that employees can reach authorized information. Over-restrictive mappings can make the assistant appear ignorant even when the document exists.
Amazon Q fits a different workflow from a personal chatbot. Its value is tied to development environments, organizational knowledge, access controls, and AWS administration.
For everyday brainstorming, a consumer assistant may be easier to start. For a company deployment, account identity, source synchronization, operational costs, and service lifecycle deserve more attention than a fluent demo response.
Amazon Q needs a product-specific evaluation in 2026. Existing Q Business customers have continuing service and an Amazon Quick path, while new business customers should follow AWS's current guidance. Q Developer remains a separate offering, with an IDE-plugin support deadline that teams should plan around.
Use a bounded task, inspect the evidence or code, and measure correction time and total cost. Start with the official Amazon Q documentation and confirm the status of the exact product you intend to use.
Amazon Q is an AWS assistant family. Q Business focuses on organizational knowledge and supported work tasks, while Q Developer focuses on software development and AWS workflows.
AWS says Q Business closed to new customers on July 31, 2026. Existing customers can continue using it; AWS directs new users seeking similar capabilities to Amazon Quick.
The published notice concerns IDE-plugin support ending April 30, 2027. It does not state that every Amazon Q product has already shut down.
AWS lists a Free tier with 50 agentic requests monthly and a Pro tier at $19 per user monthly with expanded limits.
Published seats are $3 per user monthly for Lite and $20 for Pro. Index capacity and other applicable charges are separate.
AWS says Q Business customer data is not used for service improvement or improving underlying language models. Retention and operational controls are separate questions.
AWS documents possible Free-tier content use and opt-out controls. The applicable setting depends on the environment where the service is used.
Permission-aware retrieval must match the user's authorized sources. Test both access to allowed information and exclusion of restricted information with representative accounts.
