1. Home
  2. Vertical Scaling
Vertical Scaling

Vertical Scaling: Increase or Decrease Your Server's CPU and RAM On Demand

Vertical scaling lets you manually increase or decrease your cloud server's CPU and RAM based on your actual usage and requirements, and expand storage as your application grows. You stay in control of when it happens — with no automatic triggers and no need to migrate to a new server.

Try it

Preview a manual resize

CPU and RAM move both ways, based on your usage. Storage only goes up.

20 GB minimum. Storage can only increase — this slider won't go lower.

Your resize request

This is AccuWeb.Cloud's vertical scaling feature — sometimes called "scaling up" or resizing a cloud server. It's a manual process: you decide when to increase or decrease your server's CPU and RAM, based on your own usage and needs, and you can expand storage as your application grows. Nothing here happens on its own — for automatic resizing that reacts to traffic without you doing anything, see auto horizontal scaling instead.

How vertical scaling works

Five simple steps — you're always in control

This is a manual process. Nothing resizes on its own — you decide when your server needs more, or less.

01

Check your usage

See how much CPU, RAM and storage your application is actually using right now.

02

Request more or less CPU and RAM

Based on your usage and requirements, increase or decrease CPU and RAM whenever you choose to.

03

Request more storage

Add more disk space whenever your application needs it. Storage can only be increased, never reduced.

04

We apply the change

Your requested resize is applied with minimal service interruption — no full server rebuild.

05

Keep running, on the same server

Your application keeps running on the same server, now with the performance you asked for.

Note

Vertical scaling is a manual process — CPU and RAM can be increased or decreased at any time based on your usage and requirements, but nothing changes automatically. Storage starts at a 20 GB minimum and can only be expanded, never reduced — shrinking an existing disk risks data loss and can compromise data integrity, so that direction isn't offered.

Who uses vertical scaling

Resize your cloud server whenever your workload changes

A simple way to match your server's CPU, RAM and storage to what your application actually needs — on your own schedule.

A growing application

Your app is using more CPU and RAM month over month. Increase resources on the same server instead of rebuilding on a new one.

A database running low on disk space

Expand storage as your data grows, without downtime or a risky migration to a bigger disk.

A one-time performance boost

Need more power for a specific period? Scale up, then scale back down again once it's no longer needed.

Right-sizing before you scale out

Get each server's specs correct with vertical scaling, then add more of them with auto horizontal scaling.

Choosing an approach

Vertical scaling vs. horizontal scaling

In plain terms: vertical scaling makes one server bigger. Horizontal scaling adds more servers. Many applications use both.

Scale up

Vertical Scaling

  • Increase or decrease CPU and RAM on one server
  • Expand storage as data grows (20 GB minimum)
  • Manual — you choose when to resize
  • No application migration required
Scale out

Horizontal Scaling

  • Add more servers behind a load balancer
  • Automatic — reacts to traffic on its own
  • Handles sudden traffic spikes without you doing anything
  • No single server becomes a bottleneck
See auto horizontal scaling →
Frequently asked questions

Before you resize a server

Outgrowing your current server? Resize it on your terms.

Increase or decrease CPU and RAM whenever your usage changes, expand storage as your data grows, and keep your application running on the same server the whole time. You're always in control.

Create Account