Skip to main content
When scaling your application on Shuttle, you have two main options for increasing computational resources:
  • Vertical scaling: Increase the vCPU and memory of your existing project(s). This is ideal when you need more power for individual applications. Available to both Pro and Growth.
  • Horizontal scaling: Deploy replicas of your application to distribute load and increase availability. Available exclusively to Growth tier.
Both options are billed as detailed in the sections below:

​
Vertical scaling

Simply upgrade your instance size and pay the difference. Each instance size comes with a base amount of included vCPU (0.25 vCPU), and you only pay for the additional (billable) vCPU usage per hour. For example, if you upgrade from Basic (0.25 vCPU) to Medium (1 vCPU), you’ll only be charged for the additional 0.75 vCPU since 0.25 vCPU is included in your plan.
Read the Scaling section to find out how to adjust vertical scaling

​
Horizontal scaling

Growth tier users can configure a single project to run on multiple instances and have Shuttle seamlessly load balance traffic across them for higher scalability and availability. Each replica instance is billed based on its instance size and vCPU usage per hour.

​
Purchase additional projects

Pro, Growth and Enterprise users can purchase additional projects beyond their included projects. The minimum instance for each additional project is 0.5 vCPU and is billed according to the table below. Note: The vCPU allocations for additional projects do not include any “included vCPU” - you’ll be billed for the full vCPU amount of the instance size you select.

​
How many additional projects can you add on each tier?

​
Request Rate Guidelines

Shuttle provides flexible request rate guidelines to ensure optimal performance for all users and projects across our tiers. These guidelines help you determine which tier best suits your application’s needs:
  • Pro: Up to 50 requests per second
  • Growth: Up to 1,000 requests per second
These limits are not strictly enforced as hard caps but serve as performance guidance. Applications may experience performance degradation when consistently exceeding the recommended request rates for their tier. If your application regularly exceeds the recommended request rate for your current tier, our team may reach out to suggest an upgrade to a more suitable tier. This helps ensure your application maintains optimal performance and doesn’t impact the overall platform experience.