timetobail
My stack

App Engine · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on App Engine apps on first-generation runtimes?

Time to Bail · Boarding pass

FromApp Engine apps on first-generation runtimes
ToYour pick

Act. You can stay.

Python 2.7, Java 8, PHP 5.5 and Go 1.11 on App Engine are decommissioned January 31, 2027.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Decommission date
Time left
107days
Status
Act

App Engine first-generation runtimes end January 31, 2027

Google decommissions the App Engine runtimes for Python 2.7, Java 8, PHP 5.5 and Go 1.11 on January 31, 2027. Apps on them must move to a newer runtime.

How it is winding down

  1. Jan 31, 2026Deprecated sinceDone
  2. Jan 31Decommission dateNext

What to do before January 31

Tick steps as you go. Your progress stays in this browser.

  1. Find apps on old runtimes

    In the console, open App Engine and check the runtime of each service and version.

  2. Choose a newer runtime

    Pick a supported Python, Java, PHP or Go version. Plan time for code changes.

  3. Deploy and test before the date

    Move each service and test it before January 31, 2027.

Facts we checked

Facts and their sources
Decommission dateJanuary 31, 2027[1]
RuntimesPython 2.7, Java 8, PHP 5.5 and Go 1.11[1]
Deprecated sinceJanuary 31, 2026[1]
Can the dates change?Google says key dates might be delayed[1]
If you do nothingApps on a decommissioned runtime may be disabled without further notice[2]
Deploying after the dateNot possible: you must choose a newer runtime to deploy[2]
Apps on these runtimesMust move to a newer runtime by January 31, 2027[1]

Sources

Check it yourself. Every fact above links here.

  1. App Engine standard environment support schedule Google Cloud · primary · checked Oct 13
  2. App Engine runtime lifecycle Google Cloud · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on App Engine apps on first-generation runtimes? Act. You can stay. Python 2.7, Java 8, PHP 5.5 and Go 1.11 on App Engine are decommissioned January 31, 2027.

On our scale this is Act: change a setting or plan before the date. You can stay.

Google decommissions the App Engine runtimes for Python 2.7, Java 8, PHP 5.5 and Go 1.11 on January 31, 2027. Apps on them must move to a newer runtime.

Here are the facts we checked:

  • Decommission date: January 31, 2027 (Google Cloud)
  • Runtimes: Python 2.7, Java 8, PHP 5.5 and Go 1.11 (Google Cloud)
  • Deprecated since: January 31, 2026 (Google Cloud)
  • Can the dates change?: Google says key dates might be delayed (Google Cloud)
  • If you do nothing: Apps on a decommissioned runtime may be disabled without further notice (Google Cloud)
  • Deploying after the date: Not possible: you must choose a newer runtime to deploy (Google Cloud)
  • Apps on these runtimes: Must move to a newer runtime by January 31, 2027 (Google Cloud)

You can stay on App Engine. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Google Cloud is the main source for this page. App Engine has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Apps on these runtimes: Must move to a newer runtime by January 31, 2027.

The date to remember is January 31, 2027. Make the change before then.

What to do before January 31

  1. Find apps on old runtimes. In the console, open App Engine and check the runtime of each service and version.
  2. Choose a newer runtime. Pick a supported Python, Java, PHP or Go version. Plan time for code changes.
  3. Deploy and test before the date. Move each service and test it before January 31, 2027.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on App Engine apps on first-generation runtimes can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product