Skip to main content
You can scale an application’s resources by changing the instance size (vertical scaling) or increasing the number of instances that simultaneously run your application (horizontal scaling).
If you add persistent storage to your application’s web or background processes, those processes are limited to one instance each. There is no horizontal scaling for web or background processes with persistent storage, but you can vertically scale them by increasing the instance size for the process. You cannot add persistent storage or horizontal scaling to a cron job or job.
  • Vertical scaling gives instances more power to complete resource-intensive tasks.
  • Horizontal scaling improves resilience and load balancing for applications that process many requests. For example, if you run three versions of the same instance, the underlying technology routes requests to one of the three instances, effectively distributing the load between them. If one instance becomes unstable, requests will route to the other two until the third instance is healthy again.

​
Manual scaling

To change the instance size of a process, go to Applications > app name > Processes. Click the ellipsis > Update process. Update the Resource to increase the resources available to a single instance (vertically scale), or update the Instance count within Scaling to add instances and improve the load balance (horizontally scale). There is a maximum of 20 instances, and all instances use the same size. Note: If you choose the Hobby instance size for your web process, you will not be able to add a custom domain to your application. If you need a custom domain for your application, you can upgrade your web process to a larger instance size anytime.
Update your application's web process

Change resources, instance count, and horizontal autoscaling for a process.

Once you have made your changes, click Update process. The updated process costs are added to your monthly invoice and are prorated for the first month.

​
Automatic horizontal scaling

Horizontal auto-scaling can be enabled for a stateless web process or background worker within Processes (Applications > app name > Processes). When you enable horizontal auto-scaling, you’ll define a minimum and maximum number of instances you want the process to use. Note: The maximum number of instances cannot exceed 20. When horizontal auto-scaling is enabled, the process automatically increases by one instance, up to the maximum number you’ve set, whenever CPU or memory usage on the current instance(s) reaches its target. By default the target is 80% of the instance’s available CPU and memory, and you can adjust the CPU and memory targets when you configure auto-scaling. If CPU and memory usage drop and fewer instances are required, the system automatically scales down the number of instances to match current demand. However, it will never reduce the count below the minimum number of instances you’ve configured for horizontal auto-scaling. While there currently isn’t a way in Sevalla to see how many instances are in use, behind the scenes, only the number of instances needed will be used. You will only be billed for the number of instances your application actually uses. For example, if the minimum instance is set to one and the maximum is set to five, but the application only uses one instance during the billing period, you will only be charged for that one instance. If the application uses more instances for part of the time during the billing period, you will only be billed for those additional instances for the time they are actually used.