PHP 5 has reached end of support and will be
deprecated
on January 31, 2026. After deprecation, you won't be able to deploy PHP 5
applications, even if your organization previously used an organization policy to
re-enable deployments of legacy runtimes. Your existing PHP
5 applications will continue to run and receive traffic after their
deprecation date. We recommend that
you migrate to the latest supported version of PHP.
Stay organized with collections
Save and categorize content based on your preferences.
Historically, the App Engine standard environment provided several scalable,
proprietary services for app development. These services were bundled with
first-generation runtimes
(also called
App Engine legacy runtimes), which include
Python 2,
Java 8,
Go 1.11, and
PHP 5.5. Because several
of the legacy runtimes are no longer maintained by their respective
open-source communities, as an App Engine developer, you may face hard choices
on whether to invest time and effort in migrating to a newer runtime or else
incur growing costs to retain your app on a legacy runtime.
Recognizing this challenge, Google Cloud is committed to providing you with a
more incremental migration path to newer runtimes. To reduce runtime migration
complexity, Google Cloud now supports a set of App Engine legacy bundled services and
their associated APIs on second-generation runtimes, which include
Python 3,
Java 11,
Go 1.12+, and
PHP 7/8. Your app
can call legacy bundled services APIs for second-generation runtimes through
language-idiomatic libraries.
Figure 1. How apps access the App Engine legacy bundled services
In runtime migration scenarios, you often also have the option to use
Google Cloud products that offer similar functionality as the
legacy bundled services. For the legacy bundled services that are not available as
separate products in Google Cloud, such as image processing, search, and
messaging, you can use third-party providers or other workarounds as suggested
in the Runtimes guide.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eApp Engine's first-generation runtimes, like Python 2 and Java 8, utilized scalable, proprietary bundled services, but many are no longer supported by their open-source communities.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud now provides support for a set of App Engine legacy bundled services and APIs on second-generation runtimes, including Python 3 and Java 11, to facilitate an easier migration.\u003c/p\u003e\n"],["\u003cp\u003eWhen migrating, developers can opt to use similar Google Cloud products or third-party alternatives for legacy bundled services not offered as separate Google Cloud products.\u003c/p\u003e\n"],["\u003cp\u003eSpecific information on how to migrate off of legacy bundled services can be found in a dedicated guide.\u003c/p\u003e\n"]]],[],null,["# Overview of legacy bundled services\n\nHistorically, the App Engine standard environment provided several scalable,\nproprietary services for app development. These services were bundled with\n[first-generation runtimes](/appengine/docs/standard/runtimes)\n(also called\nApp Engine *legacy runtimes* ), which include\n[Python 2](/appengine/docs/legacy/standard/python/runtime),\n[Java 8](/appengine/docs/legacy/standard/java/runtime),\n[Go 1.11](/appengine/docs/legacy/standard/go111/runtime), and\n[PHP 5.5](/appengine/docs/legacy/standard/php/runtime). Because several\nof the legacy runtimes are no longer maintained by their respective\nopen-source communities, as an App Engine developer, you may face hard choices\non whether to invest time and effort in migrating to a newer runtime or else\nincur growing costs to retain your app on a legacy runtime.\n\nRecognizing this challenge, Google Cloud is committed to providing you with a\nmore incremental migration path to newer runtimes. To reduce runtime migration\ncomplexity, Google Cloud now supports a set of App Engine legacy bundled services and\ntheir associated APIs on second-generation runtimes, which include\n[Python 3](/appengine/docs/standard/python3/runtime),\n[Java 11](/appengine/docs/standard/java-gen2/runtime),\n[Go 1.12+](/appengine/docs/standard/go/runtime), and\n[PHP 7/8](/appengine/docs/standard/php-gen2/runtime). Your app\ncan call legacy bundled services APIs for second-generation runtimes through\nlanguage-idiomatic libraries.\n**Figure 1.** How apps access the App Engine legacy bundled services\n\nIn runtime migration scenarios, you often also have the option to use\nGoogle Cloud products that offer similar functionality as the\nlegacy bundled services. For the legacy bundled services that are not available as\nseparate products in Google Cloud, such as image processing, search, and\nmessaging, you can use third-party providers or other workarounds as suggested\nin the [Runtimes guide](/appengine/docs/standard/runtimes).\n\n\u003cbr /\u003e\n\nTo learn more about these options for migrating your app, see\n[Migrate off of legacy bundled services](/appengine/migration-center/standard/services/migrating-services).\nIf you need to access the App Engine legacy bundled services when migrating to second-generation runtimes,\nsee [Access legacy bundled services for PHP 7/8](/appengine/docs/standard/php-gen2/services/access).\n\n\u003cbr /\u003e"]]
