App Engine Application
Does ZopNight manage App Engine Application?
An App Engine application is the per-project, region-pinned parent of all services and versions: 1 per project, disable-only, and free by itself. ZopNight records it via Cloud Asset Inventory as the anchor for App Engine cost attribution and topology, so service and version spend rolls up somewhere stable.
Rules that fire on App Engine Application
No active rule family targets App Engine Application today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
The App Engine application is the per-project container that holds all App Engine services and versions and pins them to a region. It carries account-wide settings that influence how every underlying service scales and bills.
No meter of its own, one region forever
The application object is free: creating it charges nothing, and it stays free no matter how long it exists. Its cost significance is indirect. Every service and version in the project lives inside it, inherits its region (chosen once at creation and unchangeable afterward), and produces the instance-hour charges that actually appear on the invoice. There is exactly one application per project, and it cannot be deleted, only disabled; disabling stops all serving (and with it the serving costs of every version), while the object itself remains.
An anchor for rolling up App Engine spend
ZopDev records the application via Cloud Asset Inventory as the parent for App Engine cost attribution and topology views. That parent role is what makes the record useful: services and versions come and go with every deploy, but the application is the one stable node the whole tree hangs from, so historical spend has somewhere durable to attach. In topology views it is also where App Engine usage becomes visible per project at a glance. A project whose application is disabled should be producing no App Engine charges at all, which makes any residual spend under it worth investigating.
Application-level review points
Because the object is configuration rather than capacity, its review questions are structural. Is the application in a project that no longer uses App Engine, still enabled with old versions serving? Was the region chosen a decade ago now far from the users and the rest of the stack, adding egress between components? And after a migration to Cloud Run or GKE, was the application disabled, or left serving a forgotten default service in parallel with its replacement?
Where the application surfaces in the console
Google Cloud console → App Engine → Settings shows the application-level view: its region, serving status, and the disable control. The dashboard above it summarizes every service and version the application contains.