Skip to content
Josué Dikoma©

20 Sep 2026 · 5 min read

Accessing Claude from the DRC: where things actually stand

The DRC appears on neither of the two lists of countries where Claude is offered — while Congo-Brazzaville is on both. What that means, why going through AWS or Google Cloud changes nothing, and what honest options remain.

Kinshasa and Brazzaville are the two closest capital cities in the world: a few kilometres of river separate them. On Anthropic's list of countries where Claude is offered, one appears and the other does not. Guess which.

This article sets out, with sources, what is actually accessible from the DRC as of September 2026 — and what is myth.

The finding, verifiable in thirty seconds

Anthropic publishes an official list of supported countries, split into two sections: commercial API access on one side, Claude.ai on the other.

I checked both. The API list has 185 entries. The Democratic Republic of Congo appears on neither. The Republic of Congo (Brazzaville) appears on both.

So this is not a bug, not a connectivity problem, and not a payment-card issue. It is a commercial coverage decision.

What it means in practice

Three direct consequences, which many Congolese developers have run into without necessarily knowing why:

  • The Claude app does not show up in the Play Store for an account registered in the DRC.
  • Creating a claude.ai account from the DRC does not complete.
  • No commercial API key can be legitimately obtained from the country.

"What about going through AWS or Google Cloud?"

Every reasonably informed developer asks this, and it was my own first question. Claude models are indeed redistributed through Amazon Bedrock, Google Cloud and Microsoft Foundry. You might assume that becoming an Amazon customer rather than an Anthropic one removes the restriction.

It does not. AWS documents this explicitly in its knowledge centre, in the article on enabling Anthropic models on Bedrock:

Confirm that Anthropic supports your location. Anthropic supports only certain countries, regions, and territories.

AWS points literally at the same list. The documentation also notes that Claude models are third-party models delivered through AWS Marketplace, which layers a second eligibility condition — AWS's own — on top of the first.

On the Google Cloud side the principle is the same: access assumes a Google Cloud project already entitled to use the platform, with a billing account in a country where the offer is available.

Conclusion: the cloud channel is not a back door, it is the same door. Two conditions apply at once instead of one.

The VPN workaround, and why I don't recommend it

Let's name it, since everyone talks about it: there is a method going around, built on a permanent VPN, a Google account created under a different geolocation, and a prepaid card. It works technically. I won't detail it here, and here is my reasoning — economic rather than moral.

You pay for a subscription that can vanish. An account opened this way breaches the terms of service. If it gets suspended, it happens after you have paid, and recourse is thin when you declared living somewhere else.

The VPN becomes a permanent dependency. It isn't a one-off formality at signup: you have to keep it running every session, with the latency and dropouts that brings — the opposite of what you want while coding.

If you use a relative's card abroad, you transfer the risk to them. Most issuers forbid third-party use of a card. If the account is flagged, it is their payment method tied to the incident.

The cost-benefit is poor. That is risk management, not a moral stance.

What honestly remains

Watch the list. It is not frozen: 185 countries for the API, with regular additions. Checking takes a minute, and it should be the first reflex before concluding anything.

The commercial route, where it reflects reality. If you genuinely operate from a legal entity established in a supported country — a real presence, not an administrative fiction — the commercial channel exists. The nuance matters: what counts is the reality of the establishment, not the address you declare.

Run models locally. This is the option I find most interesting for us, and by far the most underrated: no geographic restriction, no international card, no VPN, and your data never leaves your machine. I cover it in a dedicated article.

Check other providers one by one. Each has its own coverage. Don't assume: go read their list before reaching for your card.

What I would like to see change

Central Africa is the least well served part of the continent on this front, and the DRC — a hundred million people, a generation of developers coming up — is the clearest illustration. The river between Kinshasa and Brazzaville does not separate two levels of technical skill. Just two lines on a list.

Until it moves, we are better off building with what is genuinely within reach. It is less frustrating than keeping a VPN switched on permanently.


Sources - Supported countries & regions — Anthropic - How do I turn on access to Anthropic Claude models on Amazon Bedrock? — AWS re:Post - Claude on Google Cloud — Claude Platform Docs

Checks performed in September 2026. These lists change: verify before concluding.

IARDCAccès

Written by

Josué Dikoma — Full-stack engineer and versatile DevSecOps specialist

Next step

A project in mind?

Let's talk about it over a free 30-minute call — no strings attached.