When you’d compare alternatives to NCDAI

The National Committee for Data and AI carries a Saudi Compute Score of 8.1, sharing that position with MCIT and Tonomus in the Sovereign Compute Operators sector. NCDAI’s role in the Saudi compute ecosystem is fundamentally different from any operating entity or investment fund: it functions as the kingdom’s primary coordinating body for AI strategy across all government ministries, setting national AI standards, coordinating data governance policy, and aligning the objectives of multiple sovereign entities — including MCIT, Humain, ALAT, and sectoral ministries — under a unified AI vision.

Analysts and international organizations compare alternatives to NCDAI for three specific reasons. The first is understanding where AI strategy authority actually sits in Saudi Arabia’s government structure. NCDAI holds a cross-ministerial coordination mandate, but its relationship to line ministries like MCIT, and to operational entities like Humain, is one of strategic alignment rather than operational authority. Analysts mapping the Saudi AI governance structure need to understand when NCDAI is the appropriate engagement point for AI policy discussions versus when Humain is the right commercial counterpart, or when MCIT is the regulatory gatekeeper, or when ALAT and PIF represent the capital and manufacturing layers.

The second reason is due diligence on AI governance risk for companies deploying AI in Saudi Arabia. NCDAI’s national AI standards and data governance frameworks affect every AI deployment in the kingdom — including those by foreign companies. Understanding how NCDAI’s policy decisions relate to those of MCIT (which administers the Cloud SEZ) and the broader Vision 2030 AI targets helps companies anticipate regulatory evolution and calibrate compliance strategies.

The third reason is identifying which entities can serve as partners for AI research, academic collaboration, or international AI governance engagement. NCDAI’s cross-ministerial role gives it the mandate to engage with international AI bodies, standards organizations, and research institutions in ways that individual operating entities cannot. But for specific computational collaboration, Humain and ALAT are more relevant; for regulatory co-engagement, MCIT takes precedence.

NCDAI’s SCS of 8.1 reflects very high Sovereignty scores — its constitutional role in national AI strategy coordination is unambiguous — alongside strong Capital scores reflecting the ministerial budget authority it can direct toward AI programs. Its Capacity score is lower than operating entities because NCDAI does not directly deploy GPU clusters, and its Velocity score reflects the policy development cadence rather than the operational deployment pace of entities like Humain.

How to read the alternative rankings

Reading the SCS components for NCDAI’s alternatives requires recognizing that NCDAI is a strategy and governance body, not a compute operator or capital allocator, and that its comparators at the same SCS level serve different functional roles.

Capacity (18%) is the component where NCDAI’s operational alternatives most clearly differentiate themselves. Humain’s 18,000-to-600,000 GPU trajectory represents operational compute capacity of a scale that no governance body can match. ALAT’s manufacturing JV and PIF’s portfolio-level compute investments similarly reflect physical infrastructure that NCDAI’s strategic coordination function does not constitute. Analysts reading NCDAI’s Capacity score should interpret it as reflecting the capacity it can influence through policy rather than the capacity it directly operates.

Capital (16%) is where PIF’s structural position is most relevant. NCDAI does not deploy capital at sovereign wealth fund scale; it directs policy frameworks that influence how PIF, MCIT, and other entities deploy their capital. PIF’s SCS advantage on this component reflects the quantum difference between a $930 billion AUM fund and a ministerial committee’s budget authority.

Silicon Access (16%) is primarily a downstream function of NCDAI’s policy role. NCDAI’s data governance frameworks and AI standards affect which foreign technology companies can operate GPU infrastructure in Saudi Arabia and under what conditions, but NCDAI itself does not procure silicon. Humain’s confirmed NVIDIA GB300 agreements and ALAT’s hardware manufacturing JV are where Silicon Access actually scores for the ecosystem.

Sovereignty (13%) is NCDAI’s strongest and most distinctive component. Its mandate to coordinate AI strategy across all Saudi government ministries gives it a cross-institutional authority that even entities like MCIT — whose Sovereignty is high but domain-specific — do not replicate. NCDAI’s Sovereignty score reflects constitutional mandate, not just operational control.

Geopolitical Resilience (13%) is where NCDAI’s policy coordination role provides indirect value. By setting national AI standards and data governance frameworks, NCDAI helps Saudi Arabia maintain regulatory sovereignty in AI — which is itself a geopolitical resilience asset, reducing dependency on foreign AI governance frameworks and export control regimes.

Velocity (12%) is NCDAI’s structural limitation. Policy standards and cross-ministerial coordination processes move on multi-year timelines that cannot match the deployment velocity of commercial compute operators. This is appropriate to NCDAI’s function but creates a persistent Velocity disadvantage relative to operating entities.

Execution (12%) reflects NCDAI’s track record in developing and publishing Saudi Arabia’s National AI Strategy and in coordinating the data governance frameworks that underpin the Cloud SEZ. That track record is positive but limited in scale compared to entities with large physical infrastructure deployments.

When the alternatives become preferable

Specific conditions determine when Humain, ALAT, or PIF offers a more relevant engagement than NCDAI.

  • When operational compute access is the requirement: For any entity that needs GPU compute capacity, AI training infrastructure, or AI cloud services, NCDAI is not the engagement point. Humain at SCS 9.3 is the operating entity with GPU allocations and commercial AI services. NCDAI can inform an entity about Saudi AI strategy and data governance requirements, but it cannot provision compute. The two engagements serve entirely different functions.

  • When hardware supply chain partnership or manufacturing investment is the objective: ALAT at SCS 8.6 is the appropriate alternative when the goal is Saudi-based hardware manufacturing, server integration, or supply chain localization. NCDAI’s policy mandate does not include industrial manufacturing partnership, and ALAT’s Lenovo JV is the specific vehicle for that engagement.

  • When capital co-investment at sovereign fund scale is needed: PIF at SCS 8.5 is the entity that provides or structures investment at the scale required for hyperscale AI compute infrastructure. NCDAI can influence how AI investment fits within Saudi Arabia’s national strategy, but it cannot co-invest or provide the sovereign capital backing that PIF’s structure offers.

  • When the regulatory engagement is specifically about telecom, data center licensing, or Cloud SEZ participation: MCIT at SCS 8.1 administers the regulatory framework for cloud computing and data center operations in Saudi Arabia. NCDAI coordinates AI strategy at the policy level, but MCIT issues the licenses that compute operators actually need to function. Companies whose critical path runs through data center permitting or Cloud SEZ entry should prioritize MCIT engagement over or alongside NCDAI engagement.

  • When the timeline requires operational speed rather than policy alignment: Companies with near-term deployment needs — measured in months rather than years — should prioritize Humain’s commercial compute relationships over NCDAI’s policy coordination processes. NCDAI’s influence on deployment conditions is real but operates on a longer cycle than commercial compute procurement.

  • When the requirement involves hardware or infrastructure procurement rather than governance: NCDAI does not procure hardware, award infrastructure contracts, or manage capital programs. For companies that need a Saudi government counterpart with procurement authority — for data center construction, networking equipment supply, or server procurement — MCIT’s administrative authority and PIF’s capital deployment function are more actionable engagement points than NCDAI’s policy coordination role.

  • When private sector investment terms and commercial contracting are the medium: NCDAI, as a national committee, does not offer commercial investment agreements, joint venture structures, or capital commitments. International companies looking for investable partnerships with Saudi government-linked entities must work with PIF, ALAT, or Humain for commercial structuring. NCDAI’s outputs are policy documents, standards frameworks, and strategic coordination — valuable for compliance and alignment purposes, but not a substitute for the commercial relationships that capital deployment requires.

The competitive tier breakdown

Humain (SCS 9.3): The 1.2-point SCS gap between NCDAI and Humain is the largest of any comparison in this analysis and reflects a fundamental functional difference: NCDAI coordinates AI strategy; Humain executes AI infrastructure at scale. Humain’s dramatically higher Capacity, Silicon Access, and Velocity scores are the primary drivers. For international AI companies, research institutions, or governments seeking to understand Saudi Arabia’s AI trajectory, NCDAI provides the strategic and policy context while Humain represents the operational and commercial reality. Neither substitutes for the other. The most sophisticated engagements with the Saudi AI ecosystem involve both: NCDAI for strategic alignment and standards compliance, Humain for commercial compute access and AI services. When a choice must be made — when a company has limited relationship bandwidth and must prioritize — the decision depends on whether the primary value driver is policy influence and regulatory alignment (NCDAI) or compute access and AI service deployment (Humain).

ALAT (SCS 8.6): ALAT’s relationship to NCDAI parallels Humain’s: ALAT operates under the AI and data governance frameworks that NCDAI coordinates, and ALAT’s manufacturing and technology integration activities must be consistent with Saudi AI strategy as NCDAI defines it. But ALAT’s SCS advantage over NCDAI on Capacity and Velocity reflects the same fundamental distinction — ALAT does things; NCDAI sets the strategic framework for how those things should be done. For companies seeking a manufacturing or hardware supply chain partner in Saudi Arabia’s compute ecosystem, ALAT offers an operational relationship with specific commercial terms and industrial deliverables. NCDAI offers a policy engagement with strategic but not operational outcomes. The 0.5-point SCS advantage for ALAT reflects that operational capability generates higher Capacity and Velocity contributions to the overall score.

PIF (SCS 8.5): PIF’s 0.4-point SCS advantage over NCDAI reflects its significantly higher Capital score and its moderate Capacity score from portfolio-level compute investments. The practical distinction between PIF and NCDAI as alternative engagement points is clearest in investment contexts: for international companies or governments that want to co-invest in Saudi compute, PIF is the capital counterpart, not NCDAI. NCDAI can inform those parties about how AI investments should align with Saudi national AI strategy, but it cannot structure co-investment agreements, guarantee capital, or provide the diplomatic weight that a PIF relationship carries. In bilateral government-to-government AI engagement contexts, NCDAI may be the appropriate counterpart for AI governance discussions while PIF handles investment structuring — reflecting a division of labor that analysts need to understand clearly to navigate the Saudi AI government architecture.

NCDAI’s structural position

NCDAI’s SCS of 8.1 captures a role that is simultaneously essential and limited. Essential because no entity — not even Humain with its $77 billion commitment or PIF with its $930 billion AUM — can substitute for the cross-ministerial AI coordination function that NCDAI holds. Saudi Arabia’s AI ecosystem involves dozens of government entities, dozens of private and semi-public operators, and a complex web of international relationships that all require strategic alignment. NCDAI is the institution designed to maintain that alignment.

Limited because NCDAI’s SCS ceiling is structurally constrained by its non-operational role. It cannot close the Capacity gap with Humain by purchasing GPUs; it cannot close the Capital gap with PIF by deploying investment; it cannot close the Silicon Access gap with ALAT by building manufacturing capacity. Its SCS advantage over entities that lack its cross-ministerial authority is real, but its SCS disadvantage relative to operating entities and capital allocators reflects a functional constraint that is baked into its mandate.

For NCDAI’s SCS to increase materially, it would require either an expansion of its mandate to include direct capital deployment or compute operations — which would fundamentally change its nature as a coordination body — or a methodological reweighting of the SCS framework that gives more weight to Sovereignty and strategic coordination functions relative to Capacity and Velocity. Under the current framework, NCDAI’s SCS is appropriately calibrated to its role: high enough to signal its genuine importance to the ecosystem, lower than operating entities whose compute deployments are the measurable output of the strategy NCDAI helps coordinate. For practitioners who engage with both the policy and the operational layers of Saudi compute, understanding NCDAI’s precise scope — and recognizing where its alternatives become the more relevant engagement point — is one of the more important distinctions in navigating the kingdom’s AI governance architecture.