List what still runs Node.js 20 on Google Cloud — and whether source or container owns the fix.
For cloud engineers facing the 30 October 2026 managed-runtime decommission. Pick products and deploy shape. Get a path, starter gcloud commands, and a migration priority checklist — nothing uploaded.
Source vs container split
Managed runtime policy hits source deploys; custom images stay your patch problem. The matrix forces that fork first.
Commands beside the essay
Lifecycle blogs sell NES. This page emits list/describe starters you can run in your own project.
Multi-product honesty
Functions, Run, and App Engine are not one CLI. Scope the inventory before you rewrite.
Open the inventory matrix
Select products + deploy shape + timing. Copy commands + checklist.
How to run it
Eight steps from project picker to runtime redeploy verification.
Use cases
Functions-only shop, Run source+container mix, late post-deadline incident.
FAQ
Not Asset Inventory SaaS, NES upsell boundary, privacy, what we are not.
What the decommission window covers
- Managed Node.js 20 — Cloud Functions / Cloud Run source runtimes face decommission on 30 October 2026 per public Google Cloud runtime docs and industry write-ups.
- Custom containers — generally outside managed-runtime kill switches; you still must patch Node.
- GKE/GCE — self-managed; track images yourself.
- Not covered — buying HeroDevs NES, auto-remediation agents, or multi-cloud Node inventories.
Not affiliated with Google Cloud. Re-read live runtime support pages before you migrate.