Bring a Dockerfile. We run the container.
For apps that need their own build, use the Docker deployment path: point us at a repository with a Dockerfile and the platform builds, health-checks and serves it.
A managed runtime for containerised apps
Same release, TLS and access-control model as Application Hosting.
Any language
If it builds into a container, it runs. Bring your own base image and start command.
Deploy from Git
Push to the tracked branch and the image is rebuilt automatically.
Zero-downtime
A container must pass its health check before traffic moves.
Managed TLS
Certificates are issued and renewed for managed and custom hostnames.
Isolation
Containers run non-root with resource limits and encrypted secrets.
Logs
Build output and runtime logs are available from the console.
Container releases in four steps
- 1
Detect
We read your Dockerfile or use the repository build settings you provide.
- 2
Build
The image is built in an isolated build step and tagged as a new release.
- 3
Check
The container starts and must answer the configured health check.
- 4
Serve
Traffic moves to the healthy container; the prior release is kept for rollback.
Good to know
- Docker hosting uses the same plan limits as Application Hosting.
- Outbound SMTP is blocked; use a transactional email provider.
- Persist data outside the container filesystem or use volumes when available.
- You remain responsible for the base image and its security updates.
Container support is subject to the published runtime limits. Check the console for the current build configuration.
Ship a container without running a server.
Connect the repository, push, and let the platform build and serve the image.