What it does
Scaleway Serverless Functions runs small code components without requiring users to manage servers. It supports Node.js, Go, Python, PHP, and Rust, with HTTP requests, CRON schedules, queues, and event-driven patterns as invocation paths. Functions run on Knative, can connect to a Scaleway VPC for outbound access to private resources, and scale automatically. Developers can use the Scaleway console and documentation-supported deployment tooling to create functions and namespaces in available European regions.
Keep the function stateless, then add only the capacity you need
The product is designed for small services, background tasks, integrations, and data processing. Its overview lists five language families and several trigger styles: synchronous HTTP, CRON schedules, queues, and asynchronous events. Functions run on Knative, and the FAQ explains that Scaleway manages scaling and the underlying infrastructure. For a first deployment, create a namespace, select a runtime and resource allocation, then configure the trigger and inspect logs or metrics.
Billing has three components: request count, memory multiplied by execution duration, and provisioned resources when minimum-scale instances are kept warm. The Paris pricing page lists 400,000 GB-seconds and one million requests per account per month as free allowances, then publishes rates for excess use. Warming instances can reduce cold starts but continue to accrue provisioned-resource charges while idle.
The official FAQ documents limits that shape architecture: functions are stateless with ephemeral local storage, do not have predictable static IP addresses, support HTTP/1.1 and HTTP/2, and do not support incoming private endpoints. Outbound VPC access is available. The product is distinct from the existing Scaleway Instances and Kubernetes Kapsule offerings. No function was created or tested for this listing.
Strengths
- Supports HTTP, scheduled, and event-driven execution across five documented language families.
- Automatic scaling and pay-for-use billing avoid managing server capacity for intermittent workloads.
- A monthly allowance covers up to 400,000 GB-seconds and one million requests per account, with an explicit rate table.
Watch out for
- Functions are stateless and use ephemeral local storage; persistent data must be stored in an external service.
- Static IPs and incoming private endpoints are unavailable, and the documented protocol support is limited to HTTP/1.1 and HTTP/2.
- Keeping minimum-scale instances warm reduces cold starts but adds continuous provisioned-resource charges.
Best for
- Small APIs, event handlers, scheduled jobs, and data-processing tasks on Scaleway.
- European-region deployments that should scale from zero and pay for requests and execution resources.
- Functions that need outbound VPC access to Scaleway databases or other private resources.
Sources
- Scaleway Functions | Scaleway (Oct 25, 2026)
- Serverless Functions FAQ | Scaleway Documentation (Oct 25, 2026)
- Serverless Pricing | Scaleway (Oct 25, 2026)