Plans
👕
From XS to 2XL.
A plan defines the scaling of a booked component. Each plan has a price and a set of included resources.
# Plan resources
Each plan includes specific hardware resources and performance limits. Detailed specifications are available with the pricing page. While most components represent single scalable resources (like traffic or storage), some plans combine multiple resources. For example, MySQL plans scale both storage capacity and computing power together.
# Tiers
Plans are grouped in carefully designed buckets. That makes the costs predictable and unlikely to fluctuate often over time. In fact most standard websites and applications will work with small plans just fine.
# Changing plans
Plans can be upgraded or downgraded at any time with immediate effect. Changes are prorated with daily aggregation. Common reasons to change plans include:
- Handling increased traffic
- Optimizing costs during quiet periods
- Preparing for marketing campaigns
- Scaling for seasonal peaks
# Finding the right plan
Start small and scale up as needed. Each application has unique requirements that depend on:
- Traffic patterns
- Application architecture
- Caching strategy
- Database usage
- Storage needs
The monitoring tools help you track resource usage and determine when to scale. if in doubt.
# Regional pricing
Plan prices vary by data center location due to local infrastructure costs. Consider this when choosing a region.
Found a tpyo?Edit