Managed Containers

Run containers without managing the underlying infrastructure.

What each cloud calls it

AWS ECS, Azure Container Instances, and GCP Cloud Run all offer managed container execution without cluster management. Scaleway Serverless Containers is the closest European equivalent. OVHcloud, STACKIT, IONOS, and Hetzner do not offer a comparable managed container product; their container story runs through managed Kubernetes.
Scaleway Serverless Containers runs any OCI-compliant container image. Unlike Serverless Functions, you are not limited to supported runtimes. This makes it a practical target for teams migrating existing Dockerized applications rather than purpose-built FaaS handlers.
Scaling behaviour: Scaleway Serverless Containers scales from zero to N replicas based on incoming HTTP requests. Minimum scale can be set to one to eliminate cold starts. GCP Cloud Run offers the same pattern and is the closest architectural equivalent.
Long-running workloads are not the intended use case. Containers that hold open connections, process streams, or run background jobs continuously are better placed in managed Kubernetes. Serverless Containers is designed for request-scoped, stateless HTTP workloads.

Billing is per vCPU-second and GB-second of active execution, plus per request. Idle replicas at minimum scale incur a small cost. Scale-to-zero eliminates idle cost entirely but introduces cold start latency.
GCP Cloud Run pricing is structurally similar. AWS ECS pricing depends on whether you use Fargate (per vCPU/memory-second) or EC2-backed clusters (EC2 instance cost). Scaleway is competitive with Fargate at typical web workload sizes.
Egress from Scaleway is significantly cheaper than AWS or GCP. For containers that serve public traffic or push data to external systems, egress cost is worth modelling before comparing headline compute prices.

Deployment is via the Scaleway Terraform provider, the scw CLI, or the console. There is no native Scaleway equivalent to AWS App Runner or GCP Cloud Run's direct GitHub integration, though CI pipelines using Docker build and scw deploy are straightforward.
Custom domains and TLS termination are supported. Scaleway Edge Services can be placed in front of Serverless Containers for caching and WAF functionality.
Health checks and graceful shutdown follow standard HTTP conventions. No Scaleway-specific SDK is required; your container needs only to listen on the configured port and respond to the health endpoint.

Scaleway Serverless Containers runs inside French or Dutch regions (Paris, Amsterdam). ISO 27001, SOC 2, and SecNumCloud certifications apply. Container images are stored in Scaleway Container Registry, which is co-located in the same jurisdiction.
AWS ECS on Fargate in EU regions keeps compute in-region but routes control-plane API traffic through global AWS infrastructure. The sovereignty boundary is the same as for other AWS managed services.

Container images are portable. If your ECS task or Cloud Run service runs a standard Docker image, you can push the same image to Scaleway Container Registry and deploy without rebuilding. AWS-specific base images (Amazon Linux 2023) should be replaced with standard Linux variants.
Environment variable and secret injection differ. ECS uses Secrets Manager and Parameter Store for secret injection at task startup. On Scaleway, secrets can be injected as environment variables via the deployment configuration or pulled from Scaleway Secret Manager using the SDK at runtime.
Service discovery and internal networking. ECS services communicate over a VPC with service discovery via AWS Cloud Map. On Scaleway, Serverless Containers communicate over HTTPS; internal service mesh is not available in the serverless tier. For workloads that need internal service-to-service traffic without public exposure, Kubernetes Kapsule is a better fit.
CPU and memory configurations differ in granularity. ECS Fargate supports a matrix of vCPU and memory combinations. Scaleway Serverless Containers offers a set of predefined size tiers. Map your current Fargate task size to the closest Scaleway tier and load-test before committing.