The canonical intelligence terminal for Saudi compute.

What the Sovereign Compute Terminal Is

The Sovereign Compute Terminal is saudicompute.com’s flagship intelligence product. It is an integrated, continuously-updated, methodology-disclosed analytical workspace that sits on top of the platform’s underlying intelligence database and gives subscribers a single operational view of every entity, every deal, every facility, every silicon flow, every policy action, and every capital movement that intersects with the Saudi compute buildout. Where the public site surfaces the analytical layer, the Terminal surfaces the underlying data layer, the live SCS scoring, the comparative dashboards, and the alerting infrastructure that lets analysts and allocators operate against the buildout in real time.

The Terminal is engineered to a Bloomberg Intelligence depth standard. It is not a press-release aggregator and not a conference-content repackager. It is a structured intelligence product whose datasets, scores, methodology, and update cadence are open by design, so that subscribers can both consume the platform’s outputs and audit the inputs that produced them.

The Live SCS Layer

The Sovereign Compute Score (SCS) is the analytical anchor of the Terminal. Every entity in the tracked universe — currently 131 entities and expanding — has a live SCS, decomposed across the seven weighted components defined in the methodology section. Subscribers see the aggregate score, the component breakdown, the status tier (Top Tier, Strategic, Competitive, Emerging, Watch), and the score trajectory over time as the underlying inputs update.

The Terminal surfaces SCS at three resolutions. The entity view gives the per-entity score, the component decomposition, the underlying input attributes (capacity, capex, ownership, stage, US alignment), and the trajectory. The portfolio view aggregates SCS across user-defined entity sets — by sector, by geography, by counterparty exposure — and surfaces aggregate movements. The cohort view surfaces tier-transition events and ranked changes across the universe.

The Deal Flow Layer

Every disclosed transaction with a Saudi counterparty, a Saudi-resident asset, or a Saudi-anchored capital provider is logged in the deal flow layer. The dataset includes counterparty pairs, capex disclosures, operational status, BIS-license posture (for silicon deals), and source attribution. Subscribers can filter by counterparty, by date range, by capex band, by status, and by intersection with specific entities or facilities.

The deal flow layer is the foundation under the SCS Velocity component and the Capital component. It is updated on a rolling cadence as new disclosures surface; the Terminal flags new entries and material status changes through the alerting layer.

The Capacity Tracker

The capacity tracker is the per-facility view of the Saudi compute buildout. Every campus in the disclosed pipeline — Humain’s Riyadh and Eastern Province sites, the DataVolt NEOM program, Hexagon, the Center3 footprint, the AWS region, the Azure footprint, Google Cloud’s commitment, OCI Riyadh, the xAI training cluster, and the long tail of mid-cap sites — is logged with its disclosed IT load, its operational stage, its accelerator footprint, its hyperscaler tenancy, its sovereignty posture, and its power architecture.

The capacity tracker resolves the announcement-versus-delivery question on a per-campus basis. Each campus has a status (Announced, Permitting, Civil Works, Fit-Out, Energized, Operational) and a date stamp on the most recent stage transition. The aggregate of those statuses across the universe gives the announced-to-delivered ratio that anchors the Velocity component of the SCS.

Comparison Dashboards

The Terminal’s comparison layer lets subscribers run side-by-side analytical views across any pair or set of entities. The default templates include Humain vs G42, NVIDIA vs AMD inside the Saudi pipeline, Saudi-resident hyperscaler regions side-by-side, and the Kingdom-vs-UAE-vs-Singapore Tier-2 comparison. Custom templates let subscribers define their own comparison sets — for example, banking-workload-eligible Saudi capacity, or Arabic-first model-training footprints, or BIS-license-active counterparties over a specific date range.

The comparison dashboards inherit the SCS framework as the analytical anchor. Every comparison surfaces the SCS aggregate and component breakdown side-by-side, with the comparable underlying input attributes for each entity in the comparison set.

Policy and Silicon Alerts

The alerting layer surfaces three classes of events in real time. Policy alerts cover SDAIA decree publications, PDPL guidance updates, sector-regulator publications, and cabinet-level Saudi AI announcements. Silicon alerts cover BIS license actions intersecting Saudi counterparties, AI Diffusion Framework updates, vendor-side accelerator framework announcements, and OEM disclosures. Capital alerts cover PIF capital deployments, hyperscaler commitments, mid-cap deal disclosures, and SCS tier transitions.

Subscribers configure alert routing by category, by entity, by counterparty, and by date sensitivity. The alert content is structured (counterparty, date, classification, source link) and is paired with the analytical context that the Terminal’s editorial team assembles around each event.

The Underlying Data Layer

Underneath the analytical surface, the Terminal exposes the structured data layer. Subscribers at the data-access tier can query the full entity universe, the deal flow records, the capacity tracker rows, the source corpus, and the documents index through programmatic access. The schema is documented; the data model is stable; the update cadence is published.

The data-layer access is the differentiating feature for institutional subscribers — sovereign wealth allocators, hyperscaler business-development teams, semiconductor strategy desks, and policy researchers — who want to integrate Saudi compute intelligence into their own analytical workflows. The access pattern is structured query against the platform’s underlying database, with rate-limit and snapshotting controls.

Pricing Tiers

The Terminal is offered in four tiers. The Public tier is the open analytical surface — the entity profiles, sector landings, methodology, and high-level SCS displays — accessible without authentication and supported by the platform’s public publishing model. The Analyst tier adds the live SCS layer, the deal flow filtering, the capacity tracker, the comparison dashboards, and the alerting layer; this is the typical individual-analyst subscription. The Institutional tier adds programmatic data access, multi-seat licensing, custom comparison templates, and a higher alert-routing budget. The Enterprise tier adds bespoke analytical work, custom dashboards, on-call analytical support, and direct engagement with the platform’s editorial team.

Pricing is published. The platform is independent and not affiliated with any operating Saudi entity, hyperscaler, or silicon vendor; subscriber revenue is the primary revenue model.

What the Terminal Is Not

The Terminal is not a trading platform, an investment-recommendation engine, or a brokerage product. The SCS is a structured capability index, not an investment thesis. The deal flow layer is a disclosure tracker, not a private-deal flow product. The Terminal does not surface non-public information; every record in the underlying data layer is sourced from public disclosures, regulatory filings, and verified press, with source URLs attached at the record level.

Subscribers use the Terminal as the canonical reference layer on top of which they run their own private analytical and investment work. The platform’s role is to be the highest-quality public-information layer; the subscriber’s role is to integrate that layer into proprietary workflows.

Workflow Integration Patterns

Subscribers integrate the Terminal into a small number of recurring workflows. The most common is the daily-morning briefing, where an analyst reviews overnight alerts (BIS license actions, SDAIA decree publications, partner-newsroom disclosures, capacity-tracker status transitions) before the working day begins. The alert layer is calibrated for that workflow: alerts surface in priority order, with structured metadata that lets the analyst triage in seconds.

The second pattern is the weekly comparative review, where an analyst pulls comparison dashboards across a defined entity set (silicon vendors operating inside the Kingdom, hyperscaler regions, sovereign-AI peer programs) and reviews the SCS aggregate-and-component movements over the prior week. The Terminal’s snapshotting and historical-comparison features are calibrated for that workflow.

The third pattern is the deal-driven deep dive, where an analyst pulls every record connected to a specific transaction or entity announcement (the deal flow records, the entity-profile data, the source corpus, the documents subset) and assembles a comprehensive briefing in a compressed time window. The Terminal’s per-entity and per-deal landing pages, with their full underlying data layer, are calibrated for that workflow.

The fourth pattern is the methodology-audit workflow, used primarily by institutional subscribers, in which the analyst inspects the SCS computation for a specific entity (the seven component scores, the underlying input attributes, the recomputed aggregate) and validates or contests the score. The Terminal’s reproducibility-disclosure features are calibrated for that workflow.

API and Programmatic Layer

At the institutional and enterprise tiers, the Terminal exposes an API and programmatic-access layer that lets subscribers query the underlying database directly. The API surfaces the entity universe, the deal flow records, the capacity tracker rows, the sources directory, and the documents index through structured query endpoints. Authentication uses standard token-based mechanisms; rate-limiting and snapshotting controls protect the underlying database.

The schema is documented and stable. Breaking changes are versioned and pre-announced through the subscriber-communications layer. The platform’s commitment is that programmatic-access integrations remain stable across update cycles, so that subscriber-side analytical pipelines do not require continuous maintenance to track Terminal-side changes.

Editorial and Analytical Layer

Beyond the data and SCS surfaces, the Terminal includes an editorial and analytical layer that the platform’s team produces continuously. Per-event analytical notes accompany the major announcements that move SCS scores or trigger tier transitions. Per-entity deep-dive reports accompany the highest-SCS entities and the entities undergoing material transitions. Per-topic long-form pieces accompany the topics index and surface the analytical work integrating across the platform’s primary lenses.

The editorial cadence is calibrated to the buildout itself: compressed during LEAP, the US-Saudi Investment Forum, and FII; steadier during quieter periods. The editorial standard is the same as the public site’s: senior-analyst voice, source-attributed claims, comparative framing for every Saudi number, dense paragraphs with no padding.

Onboarding and Support

New Terminal subscribers go through a structured onboarding process that maps their analytical use case to the relevant Terminal surfaces. The onboarding covers the SCS framework, the deal flow tracker, the capacity tracker, the comparison dashboards, the alerting layer, and the programmatic-access layer where applicable. The platform’s editorial team is available for onboarding engagement at the institutional and enterprise tiers.

Ongoing support covers methodology questions, data-layer audit requests, alerting-configuration adjustments, and the broader question-and-answer workflow that subscribers run as the buildout progresses. The support cadence is calibrated to subscriber tier; institutional and enterprise tiers carry direct editorial-team access, while analyst-tier support is structured through the broader subscriber-help framework.

Roadmap

The Terminal’s near-term roadmap focuses on three workstreams. The first is breadth: continued expansion of the tracked entity universe, the deal flow corpus, and the capacity tracker. The second is depth: incremental enrichment of the per-entity profiles, the comparison dashboards, and the analytical-narrative layer. The third is the programmatic-access layer: continued development of the API endpoints, the snapshotting infrastructure, and the integration patterns that subscribers run against the Terminal.

The medium-term roadmap includes evaluation of an Arabic-language analytical layer, expanded comparative-jurisdiction coverage (UAE, Singapore, India sovereign-AI programs), and the alerting-and-distribution architecture that supports institutional notification workflows at higher resolution than the current alerting layer provides.

Trial and Evaluation

Prospective subscribers can evaluate the Terminal through a trial-access tier that exposes the analytical surfaces, the SCS layer, and a representative subset of the deal flow tracker and capacity tracker. The trial duration is calibrated to give the prospective subscriber sufficient time to validate the platform against their analytical workflow without committing to the full subscription tier; the trial does not include the programmatic-access layer or the multi-seat licensing options.

Conversion from trial to standing subscription is the primary acquisition channel for the Terminal. The conversion pattern is anchored on the analytical depth of the SCS layer, the deal-flow tracker, and the capacity tracker; the alerting layer is the secondary acquisition driver; the programmatic-access layer is the institutional-tier acquisition driver. The platform’s conversion data informs the continuous calibration of the trial-and-onboarding architecture.

Comparative Positioning

In the broader landscape of intelligence and analytical platforms, the Sovereign Compute Terminal is most directly comparable to specialized industry-intelligence products like CB Insights’ technology trackers, Bloomberg Intelligence’s sectoral coverage, and the broader S and P-Capital-IQ analytical layer. The differentiator is geographic and topical specialization: the Terminal is the only product purpose-built for the Saudi compute story at the depth and methodology-disclosure standard that institutional analytical work requires.

The pricing posture is calibrated against that comparable set. Subscribers compare Terminal pricing against the analytical depth and the editorial cadence; the platform’s commitment is to deliver a product whose pricing is justified by the analytical surface it provides. Continuous calibration of the pricing tiers against subscriber feedback and against the comparable-platform pricing landscape is part of the standard product-management cadence.

For deeper reading:

• Methodology — the SCS framework that anchors the Terminal
• About — platform mission, editorial standards, and independence posture
• Sources — the source corpus underlying the data layer
• Tables — the structured-data layer accessible at Institutional and Enterprise tiers