Enterprise Google Cloud Launch
15-month mission to deliver Hyperforce on Google Cloud Platform — the foundational paved path enabling multisubstrate expansion.
Executive Summary
A 15-month program (Apr 2025 – Jul 2026) that delivered Hyperforce on Google Cloud and, more importantly, produced the paved-path standards that unlock every future substrate — Ali and Red Queen included.
Why it matters to APS/Missionforce: the five paved-path requirements (Structured Config V2, FedX add-ons, Managed Pipelines, SRS, Falcon review) are the prerequisite for onboarding your services to Ali and Red Queen. Services still off the GCP paved path are the largest single blocker to V2MOM M7 and 7.1 progress.
The result: $2.41M in annual savings, 88% deploy-diff reduction, 393 pipeline macros unified, cluster provisioning cut from weeks to seconds, and a repeatable substrate-launch playbook.
What is EGL?
EGL (Enterprise Google Cloud Launch) was the program to make Hyperforce run natively on GCP. Before EGL, Hyperforce only ran on AWS. EGL unlocked GCP as a first-class substrate and produced the paved path — the standardized tooling every service must adopt — that Ali Build and Red Queen now depend on.
Your org (APS/Missionforce) owns services that must run on every substrate. The five app-dev requirements defined here are the same for Ali and Red Queen onboarding.
Scope & Uplifts
Managed Pipelines
Pipeline-as-code replacing hand-rolled YAML. 393 macros unified into shared standardized macros.
CompleteStructured Config V2
Config externalized from code. 88% DIFF reduction in deploy diffs — critical for GCP tractability.
CompleteFKP V2
Falcon Kubernetes Platform v2: API-driven cluster provisioning. Weeks → seconds.
CompleteService Mesh (GCP)
Istio-based mesh ported to GCP networking. Led by Shakti Das.
CompleteIngress / Edge
GCP-native ingress routing and edge proxy. Led by Rajesh Jalagam.
CompleteVault / PKI / KMS
HashiCorp Vault and PKI ported to GCP. GCP-native KMS integration.
CompleteFedX Add-ons
Substrate-agnostic add-ons (kv, queue, message, object-storage, postgres) with GCP backends.
CompleteObservability Stack
Logging, metrics, tracing adapted for GCP. GCP-native log sink adapters.
CompleteHyperforce Teams
| Lead | Workstream | Status |
|---|---|---|
| Josh Giron | Managed Pipelines; Chameleon Multi-Substrate SDK (co-founder) | Done |
| Anubhav Dhoot | Structured Config V2, service enablement; FKP support lead | Done |
| Amit Kumar | FedX substrate-agnostic add-ons (GCP backends) | Done |
| Young Bu Park / Jacob Delorme | FKP V2 — cluster provisioning API | Done |
| Shakti Das | Service Mesh / Istio on GCP | Done |
| Rajesh Jalagam | Ingress / Edge on GCP | Done |
| Jeff Lin | Platform engineering coordination; also leads Ali Build substrate eng | Done |
| Shannon Quinn / Tara Earhart | Program management | Done |
App Dev Requirements
Services in your org must complete these steps to run on GCP (and any subsequent substrate):
| # | Requirement | Why |
|---|---|---|
| 1 | Adopt Structured Config V2 | Separates env-specific config from code; enables substrate-portable deploys |
| 2 | Adopt FedX add-ons | Replace direct AWS SDK calls with substrate-agnostic interfaces (KV, queue, storage) |
| 3 | Migrate to Managed Pipelines | Replace custom pipeline YAML with standardized paved-path macros |
| 4 | Register with Safe Change / SRS | Mandatory stagger config before any Hyperforce prod promotion |
| 5 | Pass GCP paved path review in Falcon | Checklist gate required before first production workload on GCP |
Timeline & Milestones
Key Metrics
Sources & Curated Docs
Paved Path — Falcon Documentation
-
Falcon Paved Path Landing Page
Canonical onboarding guide covering 80%+ of service development. Start here.
-
Hyperforce on GCP — Developer Resources
GCP-specific dev FI onboarding, add-ons, training, production readiness.
-
Safe Change / SRS — Standard Staggers Onboarding
How to onboard your service to Standard Risk-aware Staggers (required for prod).
-
FOX — Falcon Onboarding Experience
Get control approvals to add services to Falcon.
FedX Substrate-Agnostic Add-ons
- kv-addon uplift guideMigration from AWS DynamoDB-specific to substrate-agnostic KV.
- queue-addon uplift guideMigration from SQS to substrate-agnostic queue.
- message-addon uplift guideMigration from SNS to substrate-agnostic messaging.
- object-storage-addon uplift guideMigration from S3 to substrate-agnostic object storage.
- postgres-addon uplift guideMigration from RDS to substrate-agnostic Postgres.
Slack Channels
- #gcp-hyperforce-foundation-gaMain GCP Hyperforce GA discussion channel.
- #hyperforce-on-gcpPublic channel for Core Org's journey to Hyperforce-GCP.
- #gcp-dev-supportFalcon/Hyperforce support on GCP.
- #managed-pipelines-communityManaged pipelines migration; very active.
- #falcon-k8s-platform-supportFKP support channel — Anubhav Dhoot leads.
- #fedx-platformMain FedX platform discussion.
- #falcon-addons-communityFEDX add-ons development discussion.
- #safe-change-policy-forumFY27 Safe Change Policy discussions.
- #hyperforce-paved-path-upliftFY27 Falcon Paved Path program — migration pilots.
Not Indexed — Ask Team
- EGL completion retrospective / metrics sourceThe 393 macros / 88% DIFF / $2.41M numbers were not found in a canonical doc. Ask Shannon Quinn / Tara Earhart or Jeff Lin.
- Structured Config V2 canonical migration guideOnly a Quip migration doc surfaced (Migrating Variables to Structured Config). Ask #hyperforce-paved-path-uplift.
- Managed Pipelines canonical Falcon pageAsk Josh Giron or #managed-pipelines-community.
- FKP V2 API docsGeneral FKP overview: Confluence MICROPR page. Ask Young Bu Park / Jacob Delorme.