ELARA.
    Partner login
    Back to All Writing
    e272026-08-06

    The infrastructure choice that now decides how you scale

    Originally published in e27 on 2026-08-06.

    Read Original Article on e27

    Core Argument

    A founder deciding where to host the data and AI stack behind an expansion into Vietnam and Indonesia found the question moving through legal, government relations, and a conversation about which technology bloc the business wanted to be tied to for the next decade. A choice that used to sit with engineering had become a choice about the company's place in the world. Data residency rules and sovereign AI ambitions have quietly moved the ground under every founder scaling across the region. Vietnam's first AI Law took effect in March, built around national AI infrastructure prioritising local data. Indonesia mandates local data centres for categories of information. Malaysia's National AI Office requires sensitive government data to stay on local soil. This is not abstract policy. It lands directly on where you are allowed to build. This is not a compliance problem. It is a scale problem wearing a compliance costume. A fine for mishandling data residency is survivable. What is not survivable is discovering, two markets in, that the architecture chosen cannot follow you. The stack that made sense for a single country becomes the reason expansion requires rebuilding rather than extending. There is a quieter trap inside the sovereignty story. Many local data centres celebrated across the region are owned and operated by foreign hyperscalers. The data sits locally. The control does not. Residency without ownership is a thinner form of sovereignty than the ribbon-cutting suggests. Accenture reported 64 percent of Southeast Asian organisations plan to increase investment in sovereign AI and cloud. Only 22 percent extend that oversight to the AI models themselves. One in three reported a data sovereignty incident in the past year. Firms are securing where the data lives. Far fewer are securing the models that reason over it. The businesses exposed should assume fragmentation as permanent and build a data layer modular by jurisdiction, so entering a new market becomes configuration, not reconstruction.

    What I'd Revise Now

    The "residency without ownership" argument has since acquired a sharper legal edge than I gave it. Vietnam's Decree 356 and Indonesia's PDP Law both now treat a locally-hosted AI service as a cross-border transfer the moment enterprise data is fed into a hyperscaler's model for fine-tuning or inference, because the model itself remains a foreign-controlled system regardless of where the servers sit. That is the quieter trap in this column stated as an actual legal test, not just an observation. Malaysia has also moved from the position I described to a concrete counter-example. It completed its first sovereign AI data centre in 2025 and has since launched its own domestically-controlled LLM, which is the difference between hosting data locally and actually owning the stack that reasons over it. That is the model this column argued was rare. It now has one working example on the ground. Nothing here changes the core argument. If anything, the distinction between residency and ownership has become more precisely litigated since August, which makes the modular, jurisdiction-aware architecture this column recommends more urgent, not less.

    Key Takeaways

    • Data residency and sovereign AI rules have converted an engineering decision into a political one across Vietnam, Indonesia and Malaysia
    • A compliance fine is survivable; discovering the architecture can't follow you two markets in is a scale ceiling, not a fine
    • Many local data centres are foreign-hyperscaler-owned; residency without ownership is a thinner sovereignty than it appears
    • 64 percent of Southeast Asian firms are investing in sovereign cloud, but only 22 percent extend oversight to the AI models running on it
    • The architecture worth building is modular by jurisdiction, so a new market is a configuration change, not a rebuild
    Visit Original Outlet (e27)

    Related Insights

    See plansPartner login