Skip to main content
Published in Product Insights

Buy Claude Through AWS Marketplace, Azure or Google Cloud

Buy Claude Through AWS Marketplace, Azure or Google Cloud
Table of contents
  1. Can you buy Claude through AWS Marketplace?
  2. Which Claude products does each cloud sell?
  3. Does a marketplace purchase count toward your cloud commitment?
    1. AWS
    2. Google Cloud
    3. Microsoft Azure
  4. What should finance ask before anyone clicks Subscribe?
  5. How does the bill arrive once you buy through a cloud?
  6. Can an unplanned purchase create a second Claude account?
  7. How does IT keep one governed Claude setup?
  8. Which route fits which purchase?
  9. What does Claude cost through AWS, Google or Azure?
  10. Where does The Gnar Company fit?

Yes, you can buy Claude through AWS Marketplace, and AWS's own listing says the spend can count toward an AWS commitment. In AWS Marketplace, Anthropic lists Claude Enterprise, the seats your employees use, and Claude Platform on AWS, the API your engineers build software on. The Claude API is also offered through Google Cloud and Microsoft, each with its own rule for what counts toward a commitment.

This guide is for the CFO whose company has committed spend with AWS, Google or Microsoft. It answers which Claude product each cloud sells, when the spend counts, how the bill arrives, and how one unplanned purchase can leave you with a second Claude account that IT does not run.

The Gnar Company is a Claude Select Services Partner in Anthropic's Claude Partner Network. Through its enterprise AI integration work, Gnar connects Claude to the systems a company already runs, and it can build in the company's own cloud account.

The facts about each cloud below come from AWS, Google Cloud, Microsoft and Anthropic pages read on November 14, 2026. Commitment terms also live in your own contract, so check each answer against it.

Can you buy Claude through AWS Marketplace?#

Yes, Anthropic sells Claude Enterprise in AWS Marketplace, and the listing says it gives every employee access to Claude Chat, Claude Code and Cowork. Anthropic also sells Claude Platform on AWS there, which is the Claude API for software your team builds. Both listings carry AWS's "Deployed on AWS" label.

AWS's Marketplace blog draws the line between buying and building. It says Claude models on Amazon Bedrock are for "developers building and scaling generative AI applications," while Claude Enterprise "is a fully featured software-as-a-service solution."

Anthropic's Claude on AWS page lists three ways into an AWS environment:

  1. Claude Enterprise in AWS Marketplace. Anthropic calls it "a feature-rich way to put Claude in every employee's hands, billed through AWS."
  2. Claude Platform on AWS. The full Claude API, billed by AWS. Anthropic's page says it "counts against your AWS commitment."
  3. Claude on Amazon Bedrock. Claude models "fully managed by AWS," with inputs, outputs and inference inside the AWS security boundary you control.

The first is for people. The other two are for software.

Which Claude products does each cloud sell?#

Claude Enterprise is sold directly by Anthropic and through AWS Marketplace. Anthropic's Enterprise page names no other cloud for it. The Claude API is available on all three clouds: Amazon Bedrock and Claude Platform on AWS, Google Cloud's Agent Platform, and Microsoft Foundry. So a company with a Google or Azure commitment can put API usage on that bill, but Anthropic's page does not list Claude Enterprise seats there.

Cloud Claude Enterprise, for employees Claude API, for software you build
AWS Sold in AWS Marketplace by Anthropic Claude Platform on AWS, run by Anthropic. Amazon Bedrock, run by AWS
Google Cloud Not named on Anthropic's Enterprise page Anthropic managed, in Google Cloud Marketplace. Google managed, in Agent Platform
Microsoft Azure Not named on Anthropic's Enterprise page Claude in Microsoft Foundry, through Azure Marketplace

The API routes do not give employees the Claude app. Anthropic's Claude Code deployment guide marks "Includes Claude on web" as No for Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform and Microsoft Foundry. It marks it Yes for Claude for Teams and Enterprise.

Say 300 people in finance, sales and operations need Claude to write, analyze and search. An API listing through Google Cloud's Agent Platform or Microsoft Foundry does not include Claude on the web. If the goal is software, such as a tool that reads incoming orders, the API route is the right door.

Does a marketplace purchase count toward your cloud commitment?#

It can, and each cloud states the rule in its own words. AWS's Claude Enterprise listing says spend draws down your EDP or PPA commitment. Google says Anthropic managed Claude draws down a commitment subject to its Marketplace drawdown policy, which caps eligible spend at 25% of the commitment. Microsoft says the Claude meter in Foundry is MACC eligible.

AWS#

The Claude Enterprise listing says: "For AWS customers, spend draws down directly from your EDP or PPA commitment." AWS uses EDP and PPA as names for its committed spend agreements. The Claude Platform listing says "spend retires against existing AWS commitments."

AWS's buyer FAQ, written about multi product solutions, says committed spend applies "if the products are eligible for AWS committed spend drawdown." It adds: "Products deployed on AWS typically qualify. Eligibility is determined separately for each product."

Neither Claude listing states a cap or a drawdown rate. Check your EDP or PPA for both. For Amazon Bedrock, Anthropic's deployment guide lists the billing as pay as you go through AWS. Ask your AWS account team how Bedrock spend counts under your agreement.

Google Cloud#

Google's documentation for Anthropic managed Claude says it "draws down on your Google Cloud commitment subject to the Google Cloud Marketplace Commitment Drawdown Policy." That policy carries three conditions a CFO needs:

  • Where it runs. Marketplace services "deployed on Google Cloud Platform are eligible to count" toward a minimum commitment.
  • The cap. Eligible amounts "may cumulatively (i.e., in combination) apply toward a maximum of 25%" of the minimum commitment for the period. Amounts above 25% do not count and do not roll over to a later period.
  • The exclusions. Google's drawdown rates page says 100% of Marketplace spend, other than its listed exclusions, "may count." The exclusions include services "not running on Google Cloud" and professional services. Google says the list "is subject to change at Google's sole discretion."

The policy also says usage of what it calls Third-Party Enterprise Models in Applicable Services counts toward the same cap, as its service terms describe. Ask your Google account team whether your Claude usage falls under that line.

A worked example shows why the cap matters. Take a $2,000,000 minimum commitment for the period. At 25%, at most $500,000 of eligible Marketplace spend can count toward it. That $500,000 is shared by every eligible Marketplace purchase, because the cap is cumulative. If other eligible Marketplace software has already used most of it, Claude only gets the room that is left in that period.

For the Google managed option, a Google Cloud blog post dated October 23, 2026 says it comes with "standard billing and eligible commitment drawdown." Anthropic's overview says that option bills as Agent Platform usage.

Microsoft Azure#

Microsoft's billing article for Claude in Foundry says: "The CCU meter is MACC-eligible." CCU stands for Claude Consumption Unit, the billing unit. The article says CCU spend "decrements your Microsoft Azure Consumption Commitment (MACC) the same way any other Azure Marketplace consumption does." It also says CCU billed by other cloud providers does not decrement a MACC.

Microsoft's MACC page says to "make purchases through Marketplace within Azure portal" using an Azure subscription tied to your organization's agreement. It says purchases made on Microsoft Marketplace by credit card do not contribute, and purchases paid with Azure prepayment are not eligible. Microsoft's deployment guide also lists Cloud Solution Provider subscriptions as not supported for Claude models in Foundry.

What should finance ask before anyone clicks Subscribe?#

Ask which product it is, whether it counts toward your commitment and at what rate, who accepts the offer, and who will own the account it creates. These questions come from the cloud and Anthropic pages above. Send them to your cloud account team and to Anthropic before the first purchase:

  1. Which product is this? Seats for employees, or the API for software? The answer decides which listing to use.
  2. Does this listing count toward our commitment, and at what rate? AWS's buyer FAQ for multi product solutions says eligibility is determined separately for each product. Get the answer for this listing in writing.
  3. How much Marketplace room is left? On Google Cloud the 25% cap is shared across all Marketplace purchases in the period.
  4. Which account accepts the offer? AWS says a private offer is linked to the buyer accounts it names, up to 25 of them. Microsoft says the purchase should use a subscription tied to your agreement.
  5. Is there a negotiated discount? On Claude Platform on AWS, Anthropic says discounts cannot be applied retroactively to usage before a private offer is accepted. Accept the offer first.
  6. Will this create a new Anthropic organization? On Claude Platform on AWS and on Anthropic managed Claude on Google Cloud, it will. Name its owner now.
  7. Who watches the bill? Decide who reads the monthly charges and who sets spend limits.

How does the bill arrive once you buy through a cloud?#

On each route here, Claude charges land on the cloud bill. Claude Enterprise in AWS Marketplace is a seat contract plus usage. Claude Platform on AWS, Anthropic managed Claude on Google Cloud and Microsoft Foundry (for new deployments) bill usage in Claude Consumption Units, at a published $0.01 each. Amazon Bedrock and Google managed Claude bill as ordinary AWS or Agent Platform usage. On Claude Platform on AWS and Microsoft Foundry, the invoice line shows the total. The detail by model sits in another tool.

Claude Enterprise in AWS Marketplace. The listing shows a 12 month contract for seats, with a separate usage fee "based on Anthropic API rates." Seats added mid term are billed at a daily rate "for the remainder of the contract term." Anthropic's help center says Marketplace buyers pay through AWS and are billed monthly in arrears for usage, rather than buying credits upfront.

Claude Platform on AWS and Microsoft Foundry. Anthropic's pricing page says Anthropic rates token usage at standard per model rates, applies any negotiated discount, and converts the result at $0.01 per CCU. Your AWS or Azure bill then shows a single CCU line item. Anthropic's Foundry documentation adds that CCUs are not prepaid credits, and there is no CCU balance.

Anthropic managed Claude on Google Cloud. Anthropic's docs say one CCU is $0.01 and the charges appear on your Google Cloud bill, and "Anthropic doesn't send a separate invoice."

On Claude Platform on AWS, Anthropic's pricing page says Cost Explorer shows aggregated CCU, with the model detail in the Claude Console. On Azure, Cost Management breaks CCU spend down by model and usage type. Microsoft adds that resource tags "don't provide project-level cost attribution for Claude." If two teams share one Foundry resource, the invoice will not split them for you. Usage is the number that moves month to month, and our post on what Claude Code costs per developer works through a budget for 20 developers.

Can an unplanned purchase create a second Claude account?#

Yes, signing up for Claude Platform on AWS, or for Anthropic managed Claude on Google Cloud, creates a new Anthropic organization. AWS's setup guide says that organization is separate from any your company already has with Anthropic, "including Claude Enterprise organizations procured through AWS Marketplace." The rules IT set on the existing one do not travel with it.

AWS's setup guide says API keys, workspaces and Claude Console settings from a first party Anthropic organization don't carry over. Google's documentation lists more that stays behind: "API keys, workspaces, HIPAA controls, Zero Data Retention (ZDR), and settings from an existing first-party Anthropic organization don't carry over."

The count can grow. Anthropic's Google Cloud docs say that when teams need separate access, each team gets its own Google Cloud project, and "each project has its own Anthropic organization."

A company runs Claude Enterprise for 400 employees, bought directly from Anthropic, with single sign on and retention settings IT chose. A product team with AWS Marketplace access subscribes to Claude Platform on AWS to build a pricing tool. That sign up creates a new organization with its own owner. Its spend lands on the AWS bill as a CCU line and retires against the AWS commitment. None of the Enterprise organization's settings followed it.

The Gnar Company's Claude partner page describes a related problem in general terms: "Teams picked it up on their own, in isolated pockets, and now there's a pile of experiments that never talk to each other." The page adds that nobody can see "where data is going or who approved it to go there."

How does IT keep one governed Claude setup?#

Anthropic gives admins controls: verify the company's email domain, turn on "Restrict organization creation," enforce single sign on, and claim personal accounts on the domain if needed. Domain claiming does not reach Console or API organizations. Those need a named owner and a purchase rule.

Anthropic's single sign on article says that once your domain is verified, the "Restrict organization creation" setting can "prevent users from creating new Claude or Console organizations" on your verified domains, including personal accounts. The article does not mention cloud marketplace sign ups. Ask Anthropic whether the setting applies to an organization created through AWS or Google Cloud.

Anthropic's domain claiming article says claiming works the same whether the Enterprise plan was bought directly or through AWS Marketplace. It calls domain capture "a one-way door." It also says "Claude Console organizations and API access aren't affected." So a claim cleans up personal accounts and leaves the API organizations a cloud sign up creates. Our post on how long a Claude Enterprise rollout takes covers where domain verification and single sign on fall in the setup.

The cloud side has its own gate. Google's setup needs permission to purchase in Google Cloud Marketplace on your billing account. Microsoft's guide says Claude in Foundry needs the permissions required to subscribe to Azure Marketplace offers. This is general engineering advice for using those gates:

  • Give Marketplace purchase permission to a short list of people in procurement and IT.
  • Keep a list of every Anthropic organization the company has, with one owner each.
  • Give each team its own Foundry resource or Google Cloud project, and tag the Foundry resource by team, so its Claude cost records carry the tag. On Google Cloud, each project has its own Anthropic organization, so add each one to the owner list above.
  • Review the cloud bill for new Claude lines each month.

Which route fits which purchase?#

Buy Claude Enterprise when the users are employees who need the Claude app. Buy an API route when engineers are building software. Among the API routes, the deciding question is who operates the service and where your data is processed, because that sets which terms and data processor you sign up for.

Route Who operates it Where data is processed
Claude Platform on AWS Anthropic Outside the AWS security boundary, per AWS
Amazon Bedrock AWS Inside the AWS security boundary you control, per Anthropic
Google Cloud, Anthropic managed Anthropic, as data processor On Google Cloud, under Anthropic's terms. Some supporting services, such as trust and safety systems, process data outside Google Cloud
Google Cloud, Google managed Google Cloud, as data processor Under your Google Cloud agreements, with US, EU and APAC residency
Microsoft Foundry Anthropic, as seller and operator Your choice per deployment. Hosted on Azure, prompts and outputs are processed on Azure infrastructure, per Microsoft. Hosted on Anthropic may process data outside Azure

The sources for each row: AWS's Claude Platform launch post says that service is operated by Anthropic and "the underlying requests and data are processed outside the AWS security boundary." Anthropic's Claude on AWS page describes Bedrock. Google's October 23 post describes both Google options. Microsoft's hosting comparison says Anthropic is the seller and operator for both Foundry hosting options.

What does Claude cost through AWS, Google or Azure?#

Anthropic's Enterprise page lists $20 per seat per month, billed annually, with a 20 seat minimum and usage billed at API rates. The AWS listing shows a public 12 month contract of 20 seats for $4,800 plus usage. On Claude Platform on AWS and Microsoft Foundry, usage is rated at Anthropic's standard rates and billed in CCUs at $0.01 each.

On Microsoft Foundry, Microsoft says "CCU is a change in billing format, not in price." On regional pricing, Anthropic's pricing page says: "Partner-operated platforms, Claude Models on Google Cloud (Google managed) and Amazon Bedrock, have independent regional pricing."

Discounts come through private offers. Both AWS listings carry a button to request one, and the Claude Enterprise listing says "Request a private offer to receive a custom quote." AWS's private offer guide says an accepted private offer becomes an agreement between you and the seller. Microsoft says negotiated Anthropic pricing arrives through an Azure Marketplace private offer. Anthropic's Google Cloud docs say to contact your account representative before setup if you have a discount, because "Discounts can't be applied to past usage."

A negotiated price for your seats, term and usage is not on a public page.

Where does The Gnar Company fit?#

The Gnar Company connects Claude to the systems your company already runs, once it is bought. You choose what Claude can see and change, and every lookup and change is recorded. Gnar can build those connections in your own cloud account, and you own what gets built. The first step is Gnar Discovery and Design.

The Claude partner page says Gnar builds "the governed foundation once (identity, security, data access)."

Discovery has three published tiers: $15,000 for two weeks, $20,000 for four and $30,000 for six. Each ends with a build plan and a fixed price for the build. Three commitments on every build engagement: a fixed milestone price with any overage on us, a guaranteed outcome meaning the software works as specified or we fix it, and a twelve-month bug-free warranty. It covers Discovery, Build, Forge and Maintain. It does not cover Embed. On Compass, Immerse and Integrate, ask us.

If your own engineers have the capacity and the direction, do it internally and we will say so on the call.

Frequently asked questions

Can I buy Claude Enterprise through AWS Marketplace?

Yes. Anthropic's Enterprise page says Claude Enterprise is available directly from Anthropic and through AWS Marketplace, where it can draw down from your existing AWS commit. Anthropic's help center says a Marketplace purchase is billed monthly in arrears for usage, and you pay through AWS.

Can I buy Claude Enterprise seats through Google Cloud or Azure?

Anthropic's Enterprise page names AWS Marketplace as the cloud route for Claude Enterprise and names no other. Through Google Cloud and Microsoft Foundry, Anthropic lists the Claude API. Anthropic's Claude Code deployment guide marks Claude on the web as not included on Google Cloud's Agent Platform and Microsoft Foundry.

Does Claude spend in Microsoft Foundry count toward a MACC?

Yes. Microsoft's Claude billing page says the Claude meter in Foundry is MACC eligible and decrements your commitment like other Azure Marketplace consumption. Microsoft's MACC page says to make purchases through Marketplace within Azure portal using an Azure subscription tied to your agreement, and that credit card purchases do not contribute. Claude billed by other clouds does not count toward a MACC.

Is there a cap on Marketplace spend that counts toward a Google Cloud commitment?

Yes. Google's Marketplace Commitment Drawdown Policy says eligible amounts may apply toward a maximum of 25% of a minimum commitment for the commitment period. Amounts above that do not count and do not roll over. Services not running on Google Cloud are excluded.

Does buying Claude through a cloud marketplace change the price?

Not by itself, on Claude Platform on AWS and Microsoft Foundry. Microsoft says its Claude billing unit is a change in billing format, not in price. Negotiated discounts arrive through a private offer. A negotiated price for your seats, term and usage is not on a public page.

Can a cloud sign up create a second Claude account?

Yes. AWS says signing up for Claude Platform on AWS creates a new Anthropic organization, separate from existing ones, including Claude Enterprise organizations bought through AWS Marketplace. Google says its Anthropic managed setup creates a separate organization, and that HIPAA controls and Zero Data Retention settings do not carry over.

Can The Gnar Company connect Claude to our systems once we buy it?

Yes. The Gnar Company is a Claude Select Services Partner that connects Claude to the systems a company already runs, such as its ERP or CRM, and you choose what it can see and change. It can build in your own cloud account. Start with Gnar Discovery and Design, from two weeks and $15,000. You leave with a build plan that has a fixed price on it.

We have engineers. Do we need an outside firm for this?

Often you should use your own engineers. If your own engineers have the capacity and the direction, do it internally and we will say so on the call. This work is for companies with no engineering capacity of their own to point at this.

Stay In The Loop

Never miss an update. Get the latest blogs, webinars, and expert insights straight to your inbox from The Gnar.