What it does
Scaleway Serverless Containers runs containerized web applications and services without asking teams to manage servers or Kubernetes. Deploy an image from Scaleway Container Registry or a public registry, select a region and resource allocation, and let the service scale instances in response to demand. The product supports HTTP and cron triggers, custom domains, VPC connections, and private endpoints. Unlike a general virtual machine, it is intended for stateless, request-driven containers that expose an HTTP server.
Start with an image that serves HTTP
The documented console flow creates a namespace and then deploys a container from either Scaleway Container Registry or an external public registry. Choose the region, image, container name, and resource allocation, review the estimated cost, and deploy. A container must run a web server and listen on the PORT environment variable. The quickstart then uses the service endpoint to reach the application.
This arrangement fits a small web service, internal tool, or short-lived processor better than an always-on VM. HTTP and cron triggers can start the workload, and the service can scale from zero to 200. Private endpoints and VPC attachment help keep internal services off the public internet; custom domains are available when a service needs a public address.
Pricing is based on resource consumption, with separate memory and vCPU meters and monthly account-level free allowances. A reliable estimate depends on the selected region, allocated resources, runtime, and traffic pattern. Scaleway's quickstart cautions that external registries may introduce rate limits and changing terms; the Scaleway registry is the documented integrated path. No container was deployed for this listing.
Strengths
- Accepts container images built in any language, provided the application serves HTTP on the required port.
- Offers HTTP and cron triggers, scale-to-zero behavior, and a documented maximum scale of 200.
- Private endpoints and VPC attachment support services that should not receive public internet traffic.
Watch out for
- The documented container model is for stateless HTTP services, not a general-purpose server for arbitrary persistent processes.
- Resource-based billing varies with runtime and allocation, and external public registries may impose rate limits outside Scaleway's control.
Best for
- Deploying a small HTTP application or microservice without maintaining virtual machines.
- Running scheduled or intermittent container work that can scale down when idle.
- Keeping internal web services on a private Scaleway network.
Sources
- Serverless Containers | Scaleway (Oct 26, 2026)
- Containers - Quickstart | Scaleway Documentation (Oct 26, 2026)
- Serverless Pricing | Scaleway (Oct 26, 2026)