ScalewaySkip to loginSkip to main contentSkip to footer section

NEW: Dedicated GPU power with Dedibox GPU!

Virtual Instances

A wide range of instances fully integrated into Scaleway’s cloud ecosystem, designed to offer the best price/performance ratio. Delivered in seconds, our Virtual Instances range is made to meet all your workload needs.

Dedicated resources

Production-Optimized Instances

Powered by AMD EPYC™ 7003 series

Our Production-Optimized Instances are built to provide high-performance and reliable infrastructure solutions for businesses with production workloads. Designed for production environment, high-traffic and business-critical applications, and security-sensitive workloads. Offering 99,99% SLA.
Starting from €0.074/hour

Discover the range

Workload-Optimized Instances

Powered by AMD EPYC™ 7003 series

Optimize your mission-critical applications and high-performance workloads with our secure, scalable virtual machines, equipped for high memory and compute demands. Supported by fast 12.8 Gbps network speed for seamless data transfers.
Starting from €0.074/hour

Discover the range

Shared resources

Learning Instances

Powered by AMD EPYC™ 7002/7001 series

Learning Instances provide affordable virtual machines focusing on delivering essential compute resources for basic workloads, websites and small applications. The easiest way to test and learn within Scaleway’s cloud ecosystem. Limited availability and no SLA.
Starting from €0.0001/hour

Discover the range

Cost-Optimized Instances

Powered by AMD EPYC™ 7003/7001 series or AMPERE ARM64 Altra Max

Cost-Optimized Instances provide a cost-effective solution for businesses that require flexible and scalable compute resources thanks to the shared vCPU. Ideal for development and test environments, web applications, small databases, staging servers, or other low-intensity workloads.
Starting from €0.014/hour

Discover the range

Estimate your compute cost

Choose your plan

Paris 1
Select...
Select...
GB

Min. 10 GB

You need a Flexible IP if you want to get an Instance with a public IPv4. Uncheck this box if you already have one available on your account, or if you don’t need an IPv4.

Estimated cost

OptionValuePrice
ZoneParis 1
Instance1x0€
Volume10GB0€
Flexible IPv4Yes0.004€
Total
Daily0
Weekly0
Monthly0
Start your Instance

Choose the right Instances

LearningCost-OptimizedProduction-OptimizedWorkload-Optimized
Range NamesSTARDUSTPLAY2/PRO2 & DEV1/GP1ENT1 & POP2POP2-HC & POP2-HM
UsageDiscover Scaleway or host personal projectsDevelopment and testing environments with flexible and scalable compute resourcesProduction workloads and business-critical appsHigh-performance computing and data-intensive applications requiring dedicated resources and optimal performance
StorageResilient Block Storage
or Local Storage
Resilient Block Storage
or Local Storage
Resilient Block Storage
Resilient Block Storage
ResourcesShared vCPUShared vCPUDedicated vCPUDedicated vCPU
Powered byAMD EPYC 7002 or 7001 seriesAMD EPYC 7003 or 7001 seriesAMD EPYC 7003 seriesAMD EPYC 7003 series
Sizing1 vCPU
1 GB RAM
From 1 to 32 vCPUs
From 2 to 128 GB RAM
From 2 to 96 vCPUs
From 8 GB to 384GB RAM
From 2 to 64 vCPUs
From 4 to 512GB RAM
Ratio (vCPU/RAM)1:11:1, 1:2, 1:41:4 (General Purpose)1:2 to 1:8
Maximum bandwidth100 Mbps
From 100 Mbps to 6 Gbps
From 400 Mbps to 20 GbpsFrom 400 Mbps to 12.8 Gbps

Other products you may need

Check out our entire product ecosystem

Get started with tutorials

Frequently asked questions

Whats is the difference between dedicated resources and shared resources?

Shared: A context-switching mechanism allows a physical core to be shared between multiple vCPUs for multitasking. Instances with shared vCPU can be more cost-efective for running small, non-resource intensive applications than dedicated vCPU Instances. Our different types of shared vCPU Instances offer a variety of options to balance price and performance depending on your use case.

Dedicated: Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications

How am I billed for Instances consumption?

As a public cloud provider, Scaleway operates on a “pay as you go” model: you only pay for what you use. The flexibility to provision resources when you need them and delete them when you don’t is a fundamental tenet of cloud computing, and the backbone of our billing model.

Which options are available to power off my Instance?

When you request to power off your Instance, four options are available:

  • Hard Reboot
  • Power off
  • Terminate
  • Standby

When you select the Hard Reboot option, your instance performs an electrical reboot. Your data remains on the local storage. Whenever possible, you should reboot your instance from the OS to avoid data corruption.

When you select the Power off option, all data on the local volume of your instance is transferred to a volume store, and your physical node is released back to the pool of available machines. Depending on the amount of data to be archived, the process can take time.

When you select the Terminate option, your instance and volumes are deleted. You will not be able to recover them. The flexible IP attached to your instance will not be deleted.

When you select the Standby option, your instance is stopped, but all your data remains on the local storage. Your instance is still allocated to your account, and you can restart it anytime, without delay.

Important: With the Standby option, you are still charged the same amount as if the instance is running.

Which Linux distributions are available?

We provide a wide range of different Linux distributions and InstantApps for Instances. You are free to bootstrap your own distribution.

How to secure my Instance?

All Instances are natively compatible with Virtual Private Cloud and its Private Networks. You can add it through the console or automatize your deployment on a secure network with Terraform.
More info in the documentation