Alibaba Cloud has switched on its first data center region in Brazil, the company's second in Latin America. The new region, launched August 27, runs two availability zones offering compute, storage, and database services to enterprise and developer customers, with enterprise-grade AI services set to roll out in phases. It follows Alibaba Cloud's Mexico region, which went live in February 2025 — and which the company is already preparing to expand beyond its single availability zone.

The expansion is one piece of a much larger Latin America push. BNamericas reports that at least part of the Brazilian capacity is expected to sit in data centers operated by Ascenty in the interior of São Paulo state, though Ascenty has not confirmed the arrangement. The rollout brings Alibaba Cloud's global footprint to 31 regions and 106 availability zones, on the heels of recent additions in France, Japan, South Korea, and Malaysia, against a projected US$53 billion in worldwide cloud and AI infrastructure investment.

The stakes are regional: Brazil is South America's largest cloud market, and Chinese hyperscalers are treating Latin America as their next battleground against AWS, Google Cloud, and Azure. Alibaba Cloud's playbook is consistent — land compute capacity first, then layer AI services on top once the region proves out. Don't be surprised if the first enterprise AI offerings in Brazil are Qwen-family models and agent tooling, mirroring what Alibaba has already pushed in its Asian and Middle Eastern regions.

A developer has squeezed a modern language model into 700 lines of C. The project, gemma4.c, runs Google's open Gemma 4 E2B model on an ordinary CPU using a single, readable C file that handles the tokenizer, transformer, KV cache, sampling, and CPU kernels — no inference framework underneath. The author says it's a deliberate educational exercise: start at main() and trace a prompt all the way to generated tokens.

The numbers are the surprising part. On an AMD Ryzen 7 7700, it hits roughly 639 tokens per second on prefill and 25.9 tokens per second during generation with int8-quantized weights, which the author claims is faster than llama.cpp for this workload. The catch is deliberate narrowness — it supports only this one model and only CPU inference — which is exactly why the whole thing fits in one file. As local-model runtimes grow more general and more complex, there's real pedagogical value in a version you can actually read end to end.

Are small, single-file runtimes a teaching tool or a glimpse of how lean local inference could get? Tell us in the comments.

Sources: Leiphone (雷峰网) · BNamericas · gemma4.c (GitHub) · Reddit r/LocalLLaMA