Scaleway

Scaleway offers cloud infrastructure and managed services through a European provider. Its catalogue spans virtual machines, dedicated hardware and platform services, allowing teams to choose which operational layers they want to run themselves. Product availability and pricing are tied to the selected service and location.

Key features

• Compute. Instances and dedicated-hardware products cover different resource and isolation requirements.
• Storage. Object storage and other storage products complement application compute.
• Managed platforms. Kubernetes, databases and serverless services are part of the catalogue.
• Regional choices. Official documentation and pricing pages identify regional and zonal product availability.

Who it is for

Development and infrastructure teams considering European deployment locations and a mix of self-managed and managed services. Data-residency requirements still need to be checked against the specific service and contractual terms.

Pricing at a glance

Cloud products are priced using their own consumption units, with separate compute, storage and networking charges. Some services have allowances or trial offers, but this profile does not assume a provider-wide free production plan.

Pricing model checked on 15 October 2026; confirm current terms on the official product page. No currency conversion or fixed price estimate is used in this profile.

Things to consider

• Check regional availability and capacity for every component in the architecture.
• A European provider does not by itself establish compliance for an application.
• Budget for storage, backups and transfer alongside the main compute resource.

Before moving a production workload, record its runtime versions, storage needs, database size and external services. Decide who will own updates and incident response. A small pilot is a better way to establish compatibility than relying on a headline feature list; include a restore exercise and check that the team can retrieve its data independently.

Getting started

1. Read the official documentation and plan information, then write down the features and costs your project needs.
2. Choose a small test environment that matches the application’s runtime and persistent-data requirements.
3. Configure restricted access, domain settings and certificates; keep secrets out of source repositories.
4. Test deployment, backups and restoration with representative data before changing production DNS.
5. Review usage and recurring charges after the pilot, and document a migration or cancellation path.