What changed in the call script
In Q4 2025 and Q1 2026, Anthropic’s enterprise sales team added a new question to their first-meeting script: “Where does the compute that calls our API actually run?”
This was not in the script in 2024. The trigger appears to be a combination of EU customer pressure on data residency, US Bureau of Industry and Security export-control conversations, and Anthropic’s own internal compliance posture. We have observed the question in 11 of 13 enterprise conversations our clients have had since January 2026.
What “onshore compute” actually means
“Onshore” is shorthand. In the actual underwriting it expands into three sub-questions:
- Physical location of the inference workload — which country, which data center
- Jurisdiction of the entity operating the compute — where the legal contract for that compute lives
- Where the resulting logs, prompts, and responses are stored — file system, retention, access control
Customers who answer “AWS US-East” to question 1 but cannot answer 2 and 3 cleanly create slowdowns in deal closure. Customers who answer all three with one consistent jurisdiction tend to close in normal timelines.
How a Malaysian Sdn Bhd + KL Mac mini answers all three
This is why the Sdn Bhd + KL physical compute pattern has gotten popular in 2026:
- Question 1: Physical compute is a Mac mini in a Tier-III data center in Kuala Lumpur, Malaysia
- Question 2: The entity that operates the compute is the same Sdn Bhd that signed the Anthropic enterprise contract
- Question 3: Logs and request data live on the same Mac mini, in Malaysia
Three questions, one country, one entity, one answer. The conversation moves on within minutes.
The competing answers and why they slow deals
“AWS Singapore” — Strong on physical location, weak on entity (your contracting entity is usually not AWS Singapore’s contractor; AWS handles that legally). Anthropic’s underwriting then asks about your AWS contract terms, which adds a meeting.
“Azure US-East” — Adds an export-control question because of US-China dual-use compute classifications. Your team will be asked to demonstrate that no Chinese-resident person has admin access to the inference environment.
“GCP Tokyo with our Hong Kong holding” — Triggers the cross-jurisdiction question. Anthropic asks for a memo from your counsel showing how Japanese data residency rules interact with Hong Kong corporate structure.
“Mac mini in Shenzhen” — Closes the conversation. Anthropic enterprise generally cannot sign with mainland-resident compute under their current 2026 posture.
Operator FAQ
Does Anthropic actually verify where the compute runs?
For initial signing, mostly self-attestation. For renewal and for accounts above ~USD 100K ARR, Anthropic increasingly requests proof. We have seen them accept photos of the rack, screenshots of the data center’s certifications (Tier rating, ISO certs), and the Sdn Bhd’s lease for the colocation rack space.
Is dedicated hardware necessary, or does shared cloud work?
Shared cloud works for accounts under USD 30K ARR, where the question is asked but not deeply audited. For larger accounts, dedicated hardware in a known jurisdiction makes the conversation an order of magnitude shorter. We model the shift point at roughly USD 30K–50K ARR based on conversations our clients have had.
What happens if my Mac mini goes down?
You have a window. Anthropic has not, in any case we have seen, terminated a contract because a single physical machine had a 4-hour outage. What does cause friction: if your fallback is a different jurisdiction without notifying Anthropic. We recommend documenting fallback infrastructure in the contract addendum.
Can I use AWS Singapore for inference and still answer “yes” to onshore?
Technically yes for the physical layer. But the entity-jurisdiction question (Q2) will follow. AWS Singapore’s contracting party will not match your Sdn Bhd cleanly unless you have an AWS Enterprise Agreement with your Sdn Bhd as the AWS customer of record.
How long does this whole question delay a deal?
In our sample (Q1 2026, n=11 enterprise opportunities): clean answer = closes in 4–6 weeks. Messy answer = 10–14 weeks, and a meaningful share (3 of 11) stalled out before signing.
One-line conclusion
Anthropic enterprise increasingly wants one country, one entity, one consistent answer about where compute runs. A Malaysian Sdn Bhd plus KL physical compute is currently the cleanest single-jurisdiction answer at this price point.
Observations from MalakaToken’s own client conversations (Q1 2026, n=11 enterprise procurement processes for Anthropic, OpenAI, and Google). Methodology available on request. MalakaToken is not affiliated with Anthropic, OpenAI, or Google.