APIs and web applications
Your backend exists as a container image and should go into production without a cluster of your own. You supply the image; we run it with multiple replicas, health checks and a custom domain including automatic TLS.
You deliver a container image, we keep it running: multiple replicas, health checks, rolling updates without downtime and a custom domain with automatic TLS.
New versions roll out replica by replica – if the health check fails, the old version stays live.
Every project gets its own network; services talk internally, and only what you expose is public.
Data on CephFS or local storage – with scheduled backups and restore.
Your backend exists as a container image and should go into production without a cluster of your own. You supply the image; we run it with multiple replicas, health checks and a custom domain including automatic TLS.
Deployments should be possible during the day without users noticing. New versions roll out replica by replica, and if the health check fails, the old version stays live.
Exports, imports and mail delivery should not slow down the web application. Workers run as a separate Container App in the isolated project network and process jobs from the queue without being publicly reachable.
Business teams and customers should see new features before they are merged. Each branch is deployed as its own Container App with its own address and removed again after review.
You are billed for what your containers reserve – per second. A small, always-on service fits within the free allowance.
Container Apps comes in three operating models – and you can switch at any time as your team grows or wants to focus on other things.
You get the cluster with full access and orchestrate it yourself.
We operate cluster, ingress and updates – you push images.
We also build pipelines and deployments and take responsibility for operating your application.