AUTOSCALING
Autoscaling: your servers follow the load
An instance group adds VMs when the load goes up and removes them when it goes back down. You pay for the capacity you need, when you need it.
How it works
An instance group starts from a template: flavor, image, SSH keys, boot data, security groups and firewall. You set a minimum and maximum number of VMs (up to 20), and simple rules, for example “CPU above 70% for 3 minutes: add a VM”, or “below 20% for 10 minutes: remove one”.
Rules based on CPU and network
Rules apply to the average CPU utilization of the VMs in the group, or to inbound and outbound network traffic. The platform evaluates them every 15 seconds, then observes a cooldown period between two changes (3 minutes by default) to avoid oscillations. If no measurement is available, nothing changes: this is the safest behavior.
With your load balancer
When linked to a load balancer, the group registers its new VMs with it as soon as they boot; the load balancer only sends them traffic once their health check has passed. A VM being removed first leaves the load balancer, then is deleted after 30 seconds, giving in-flight requests time to complete.
Replacement and distribution
A VM that is out of service for longer than the replacement delay is replaced automatically. New VMs are placed preferably on the server hosting the fewest members of the group: losing a server only means losing part of the group, which rebuilds itself elsewhere.
VMs without replicas
Group members are identical VMs with no data to protect: they run without replicas, which saves space and network bandwidth. Keep your data in a replicated database or in S3 object storage.
Management
Groups are managed from the portal, the API or the AI assistant. You can also set the number of VMs manually, for example ahead of an expected peak; the rules then take over again.
AUTOSCALING
At a glance
📈
Driven by load
CPU, inbound or outbound traffic.
💓
Automatic replacement
A VM that goes out of service is replaced.
🌐
Anti-affinity
The group’s VMs are spread across several servers.
🧱
Up to 20 VMs
Per group, within the limits of your quotas.
WORKED EXAMPLE
Example: a website running on 2 to 6 servers
| Resource | Details | excl. VAT/month |
|---|---|---|
| 2 × m1.medium | 2 vCPU · 4 GB RAM · 40 GB SSD | €28.26 |
| Public IPs (EIP) | 1 IP | €2.50 |
| 1 × Load balancer Small 1 | 5,000 max. connections | €12.60 |
| Total | €43.36 excl. VAT/month or €52.03 incl. VAT/month |
At rest, two m1.medium VMs behind a Small 1 load balancer and a public IP. At peak times, the group scales up to six VMs, billed only while they are running.
PROCESS
How it works
Step 1 · Prepare the template
An image and boot data that install your application with no manual intervention.
Step 2 · Set limits and rules
Minimum and maximum number of VMs, CPU or network thresholds.
Step 3 · Link a load balancer
Traffic is automatically spread across the group’s VMs.
FREQUENTLY ASKED QUESTIONS
Good to know
What is autoscaling?
The ability of a service to automatically add or remove servers depending on the load. At Gridale, an instance group adds identical VMs when the load goes up and removes them when it goes down.
Which metrics trigger autoscaling?
The average CPU utilization of the VMs in the group, as a percentage, or their inbound and outbound network traffic, in bytes per second, measured over a period that you set in the rule.
How many VMs can a group contain?
Up to 20, within the limits of your organization’s quotas.
Can autoscaling make a VM bigger?
No: it adds or removes identical VMs (horizontal autoscaling). Changing the size of a VM restarts it, which is not suitable for automatic adjustment.
GRIDALE CLOUD
The other services in your VDC
How the Gridale cloud works
The Gridale cloud combines proven building blocks (OpenBSD, KVM, etcd, pf, relayd) around simple, auditable code. …
Your virtual data center (VDC) in France
A VDC brings your entire infrastructure together in an isolated space: servers, networks, firewall, VPN, storage …
Virtual servers hosted in France
Choose a predefined configuration or build your VM by the vCPU, by the GB of RAM and by the GB of disk. Linux and …
Encrypted VMs, from disk to memory
Encrypt each VM’s disk with AES-256 using a key unique to that VM, and its memory with the AMD processor. A …
Appstore: your applications ready in minutes
Choose an application and a VM size: the platform takes care of the rest, from installation to HTTPS, including …
Routed SDN network: private networks and public IPs
Each organization has its own network, isolated from the others at the routing level. Your VMs communicate with …
Firewall as a Service (FWaaS) based on pf
Every VM has its own firewall, applied on its interface by pf, OpenBSD’s firewall. You get the fine-grained …
VPN as a Service: IPsec and WireGuard
Connect your offices and your team members to your private network in the cloud, without exposing your servers to …
Ready to launch your project?
Estimate your infrastructure in two minutes or talk it over with an engineer.
