Who is it for?
Developers who want to publish custom API services behind the edge without classic server management.
Use case
Use Case: Container API Publish
A scenario for publishing container-based HTTP/API services with domain, SSL, WAF, healthcheck, and logs.
How does it work?
Define the container app, port, and healthcheck; after deploy, the domain connects through the edge route.
Included services
Container Apps, DNS, Auto SSL, WAF, logs, status, resource plan, and optional Object Storage binding.
Example scenario
A JSON API is published as a container image and served through a public domain once healthcheck passes.
Example scenarios
Fast API delivery
Connect services to domains quickly.
Operational tracking
Watch deploy through status and logs.
Security
Make WAF and SSL part of the default flow.
Frequently asked questions
Yes. The services described here are positioned around the same CDN account, domain, SSL, cache, and WAF layers.
Basic CDN and WordPress flows can be handled from the panel. Container, GitHub deploy, and custom migration scenarios are better planned with technical support.