Amazon Q

What Amazon Q Developer is

Amazon Q Developer is the coding assistant from the cloud division of the retailer, and the address that used to be a standalone product now points into the wider assistant family. The positioning is a coding and operations assistant that lives inside the same ecosystem as a large share of cloud workloads.

What it does

Coding assistance generates suggestions from comments and surrounding code, from single lines to complete functions, so it fits into everyday editing. Application modernisation is a distinctive area: porting applications from one operating system to another, and updating older frameworks, which is work that few competitors package as a feature. Pricing is not published on the page beyond the free tier, which allows fifty agentic chat interactions a month, so the paid boundary sits behind a sign-in.

Who it is for

The audience is software developers and engineers, cloud operations engineers managing cost, incidents and networking, and data scientists working inside the same cloud. It suits teams that already run on that cloud and want assistance without leaving it.

What to keep in mind

The end-of-support notice changes how this product should be evaluated. Support for the editor plugins ends on a stated date, so check whether the path you would rely on is still maintained before you build a workflow around it. The data-privacy commitment is conditional and the condition matters: the page states that proprietary content may be retained or used depending on the plan and settings, so set the privacy controls deliberately rather than accepting defaults. One expectation to set: the performance claims, productivity gains and acceptance rates are the vendor's, so validate them on your own codebase. Because it is tied to one cloud, weigh lock-in alongside the convenience, and confirm what leaves your environment when you use the assistant.

If your team standardises on it, document which features depend on the cloud account and which work offline, because a future change in the assistant's availability affects more than just suggestions. Treat the modernisation features as a head start that still needs engineer review, not a finished port. If the modernisation features appeal, pilot them on one low-risk application and compare the result with a hand-done port before trusting them with anything central. Keep the privacy settings documented per team, because the default may not match your internal rules, and review them when the plan changes. The free tier is enough to learn the editing suggestions, but the agentic chat limit means heavier automation sits behind a paid plan, so size that before you build a workflow around it. Because the assistant is part of a larger cloud family, check which capabilities require that cloud and which are portable, so a future direction change does not strand work you already did.