APS / Missionforce · 2026
Hyperforce Programs Overview
A narrated introduction to GCP EGL, Ali Build, and Red Queen — the three multisubstrate programs shaping your org's roadmap and V2MOM.
The Landscape
Three programs. One paved path.
GCP EGL
Complete. Hyperforce on Google Cloud. Delivered July 1, 2026. The template for everything that follows.
Ali Build
In flight. Hyperforce on Alibaba Cloud for the China market. Live Preview August 1, 2026.
Red Queen
Active dev. Air-gapped Hyperforce on AWS Secret Cloud for U.S. government SECRET workloads.
GCP · EGL
Hyperforce, now on Google Cloud.
A 15-month program to make Hyperforce run natively on GCP — and to build the paved path that unlocks every future substrate.
- Before EGL, Hyperforce ran only on AWS. EGL changed that.
- Delivered on time: July 1, 2026.
- Every tooling standard here — Managed Pipelines, Structured Config V2, FedX add-ons, Chameleon SDK — is now the required paved path for the entire Hyperforce fleet.
GCP · By the Numbers
The scope of the paved path.
sec
Cluster Provision (was weeks)
GCP · What Your Team Owns
Five things every service must do.
- 1. Adopt Structured Config V2 — externalize env-specific configuration.
- 2. Adopt FedX add-ons — replace direct AWS SDK calls with substrate-agnostic KV, queue, storage.
- 3. Migrate to Managed Pipelines — no more hand-rolled pipeline YAML.
- 4. Register with Safe Change / SRS — mandatory for all Hyperforce prod as of April 20, 2026.
- 5. Pass the GCP paved path review in Falcon.
Ali Build · Alibaba Cloud
Hyperforce for the China market.
The Ali Build ports Hyperforce to Alibaba Cloud. Architecture codename: Yanzi. Same paved path, new substrate, unique constraints.
Ali Build · The Multiplier
Chameleon: write once, run anywhere.
The cross-substrate SDK that makes Ali possible — and makes future substrates cheap to add.
- Go — primary implementation, used across platform services.
- Java (MultiCloudJ) — for JVM-based Salesforce core services.
- Python — bindings for tooling and scripting.
- Co-founded by Josh Giron. Same team that owns Managed Pipelines.
Ali Build · Scope
Nine workstreams. Same shape as EGL.
- Managed Pipelines across the Great Firewall
- Artifact Transfer — secure binary and image movement
- IAC + BOM — Terraform adapted for Alibaba providers
- Vault / PKI / KMS — security infrastructure ported
- FKP on Alibaba Container Service for Kubernetes (ACK)
- Service Mesh — Istio on Alibaba networking
- FedX add-ons — Alibaba-backed (led by Bo Yang)
- FIT — chaos engineering for Alibaba failure modes
Red Queen · GovCloud
Air-gapped Hyperforce for classified workloads.
Government Cloud Advanced. AWS Secret Cloud. SECRET / IL5+ classification. No internet, no commercial connectivity.
Red Queen · The Air Gap
Airlock in. Vantage out. Nothing else.
- Airlock (Low → High): the only way artifacts enter Red Queen. Scanned, approved, one-way.
- Vantage (High → Low): controlled data extraction — audit logs, approved telemetry only. Requires DLP review.
- No SSH. No VPN. No direct debug access.
- Every dev workflow, patch, and deploy is mediated by these two bridges.
Red Queen · The 19 Standards
Nineteen requirements. All non-negotiable.
- Build: Managed Pipelines + Airlock artifact transfer + BOM
- Config: Structured Config V2 with RQ environment profile
- Data: FedX add-ons only, plus data residency attestation
- Security: Vault/PKI seeded via Airlock, KMS, zero-trust networking
- Observability: air-gapped logging, no telemetry egress
- Change: SRS with RQ stagger, 4-environment promotion, govt approval
- Continuity: DR without commercial cloud connectivity
Your Bottom Line
What APS owns — and how to win.
- M7: Multisubstrate Service Parity — % of your services on all substrates.
- 7.1: Hyperforce Paved Path Adoption.
- 7.1.1: Paved path compliance detail (SCV2, FedX, Pipelines, SRS).
- The critical path: get every service through GCP paved path → that unblocks Ali and Red Queen simultaneously.
- Use the Staffing Model app on this site to plan headcount by area.
← → arrow keys · SPACE to play/pause narration