Managed App Platform across clouds
Platform-as-a-service for web applications - App Runner, App Service, App Engine - where you bring code or a container and the platform owns the servers, the scaling and the TLS.
3 verified modules, 1 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | A Service where a Push Is Not a Deploy | static-validated |
| Azure | Azure App Service (Linux Web App) | ✓ live-tested |
| Google Cloud | The App Engine Application: One per Project, Forever | static-validated |
How to choose
Compare what you hand over (a container image, a repository, or source the platform builds), how the app reaches your network (a VPC connector, VNet integration, or not at all), whether the platform can scale to zero, and what identity the app runs as when it calls other services.
When not to use
The platform owns the servers and you still own the app: its dependencies, its secrets and its egress. A PaaS that scales to zero also cold-starts, and a plan that never scales to zero bills for an idle app at the rate of a busy one.