We get this question all the time. By email, in customer meetings, at events: “Can you sell us Claude licenses? We have a purchase order ready.”
The answer is no, but let me tell you why, and how we can help. Only Anthropic sells Claude user licenses. Resellers, Microsoft, Google and Cloud2 do not.
The reason is the useful part. A Claude license and Claude as an API are two different purchases, with different sellers and different data boundaries. Most companies need both, and the ones that mix them up find out at the audit.
01Who sells what
This is the state of play in October 2026.
| What you want | Who sells it | How you pay |
|---|---|---|
| Claude Teamclaude.ai for 2–150 people | Anthropic only, self-service at claude.ai | Credit card, monthly or annual |
| Claude Enterpriseclaude.ai, Claude Code, Cowork · 20+ seats | Anthropic directly, or AWS Marketplace | Annual contract. Via AWS Marketplace the seats land on your AWS invoice and draw down your EDP or PPA commitment |
| Claude models as an API | Amazon Bedrock, Google Vertex AI, Microsoft Foundry, or Anthropic directly | Pay per use on your cloud invoice. Bedrock access can be sold by an Anthropic Authorized Reseller such as Cloud2 |
Three things people get wrong:
- Team is not on any marketplace. If you want Team, someone in your company opens claude.ai and pays with a card. That is the only way.
- Enterprise on AWS Marketplace is still Anthropic's product. You get the same claude.ai, operated by Anthropic, with AWS as the billing channel. The main benefit is that the seats draw down your existing AWS commitment.
- Reseller programs cover Bedrock. Anthropic's reseller program, which we are part of, covers Claude on Amazon Bedrock. Claude.ai licenses are outside it. If a reseller offers you licenses, ask to see the contract.
So when you ask us for licenses, we point you to Anthropic or to the AWS Marketplace listing and help you get the private offer right. That takes an hour, and then the real work starts.
02A license is not a data boundary
In Claude on AWS, the EU way I wrote that “convenience and residency are two different purchases.” The same rule applies here, and the license question is where most companies trip over it.
A Claude Enterprise license is a SaaS subscription. Anthropic runs the service, Anthropic decides where it runs, and you get the controls Anthropic gives you: SSO, audit logs, data retention settings, a DPA. Those are good controls. A region selector is missing from the list.
Look at Anthropic’s own regional compliance page. It says you can choose where your data is stored and processed, and then it lists where: AWS Bedrock, Google Vertex AI and Microsoft Foundry. The claude.ai plans are missing from that list, and buying Enterprise through AWS Marketplace does not add them. The invoice moves to AWS. The data stays where Anthropic runs the service.
Claude on Amazon Bedrock in an EU region is the setup where you decide. You pick eu-north-1, you pin the model to the eu. inference profile, you restrict invocation with IAM, and you log every call in CloudTrail. It runs inside your AWS account under your AWS DPA. Anthropic does not receive your prompts. That is a data boundary you can show to your DPO.
03Buy the license for people, buy the API for data
Most companies need both, with a clear line between them.
Buy the license for people. Your sales team and your lawyers want Claude in a chat window. Give them Enterprise. Turn on SSO and audit logs, and write a short usage policy that says which data may go in and which may not. Treat it like Microsoft 365: a productivity tool with a sensible policy around it.
Buy the API for data. Anything that touches patient records, customer PII, financial data or source code under NDA goes to Bedrock in an EU region. That includes your own applications and agents.
The same rule applies to the tools on your laptop. Claude Code in the terminal, the IDE extension and the Claude desktop app all talk to Anthropic by default. When you use them with sensitive data, point them at your own Bedrock instead. This is a config change. The CLI and IDE read it from ~/.claude/settings.json, the desktop app has it in the setup screen. You keep the same Claude and the same workflow, and every prompt stays in your AWS account in an EU region. We showed the exact settings in the previous post.
Draw the line in writing. One page that says which tool handles which data class, and where it runs. Most companies we meet have the tools already and the page missing.
A side effect: the API side comes on the AWS contract you already have. Same invoice, same partner, no new vendor onboarding and no new DPA.
We don't sell Claude licenses. Anthropic does, and we will help you buy them right.
Our job starts after that: making sure you know where your data is, and that every team uses Claude by the rules you set.
Next step
Sort your Claude purchases by data boundary in one session
Bring your real use cases. We'll sort them by data class and hand you a one-page policy and an architecture your DPO can sign.
Book an architecture reviewCloud2 · AWS Premier Partner · AWS Security Competency · Anthropic Authorized Reseller via Amazon Bedrock
