Cookies ahead

Our support chat tool "Intercom" would like to collect some more data on you. See the related link for more details.

Docs

Plans

Reviewedbyfl

Markdown ↓

👕

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 designed for different application scales. 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. Detailed specifications are available on the pricing page.

Tiers

Plans are organized into carefully designed tiers that make costs predictable and unlikely to fluctuate frequently. Most standard websites and applications can start with small plans and scale up as needed.

Changing plans

Plans can be upgraded or downgraded at any time with immediate effect, with changes prorated on a daily basis. 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

Choosing the right plan depends on your application's unique requirements, including traffic patterns, architecture, caching strategy, database usage, and storage needs. Start with a smaller plan and scale up as your application grows.

The monitoring tools help you track resource usage and determine when to scale. if in doubt.

Regional pricing

Plan prices vary by region due to differences in local infrastructure costs, so evaluate pricing across available regions when deciding where to host your application.

Written by a human. Review, grammar checks and typo fixes by AI.

AI use & editorial processEdit on GitHub ↗