Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions cloud_docs/concepts/database-backups.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: Database backups on Serverpod Cloud are point-in-time snapshots of
A bad migration or an accidental bulk delete can lose data you needed. Serverpod Cloud can take point-in-time snapshots of your managed database, on demand or on a recurring schedule, and restore the whole database to any snapshot in one step. Backups run on the platform, so there is nothing for you to host or maintain. You manage them with the Serverpod Cloud CLI.

:::info
Backups are a **Growth** plan feature. On Growth you can create snapshots, schedule backups, and restore. Listing snapshots, deleting snapshots, and viewing or disabling the schedule are available on every plan, so a project on a smaller plan can still see and clean up backups it already has.
Backups are a [**Growth** plan](/cloud/concepts/plans-and-billing) feature. On Growth you can create snapshots, schedule backups, and restore. Listing snapshots, deleting snapshots, and viewing or disabling the schedule are available on every plan, so a Starter project can still see and clean up backups it already has.
:::

## When to use each kind of backup
Expand Down Expand Up @@ -111,13 +111,13 @@ Cloud asks for confirmation, then deletes the snapshot permanently. Scheduled sn

## Pricing

Backup storage is billed separately from your regular database storage, as its own metered charge rather than counting against your database usage. It is priced the same as database storage, billed by usage and prorated for partial months, and applies only on the Growth plan. A schedule usually costs less than keeping the same number of manual snapshots. Each manual snapshot is a full copy, while a scheduled series stores one full copy plus the changes between snapshots. For current plan pricing, see [Serverpod Cloud plans](https://serverpod.dev/cloud).
Backup storage is billed separately from your regular database storage, as its own metered charge rather than counting against your database usage. It is priced the same as database storage, billed by usage and prorated for partial months, and applies only on the Growth plan. A schedule usually costs less than keeping the same number of manual snapshots. Each manual snapshot is a full copy, while a scheduled series stores one full copy plus the changes between snapshots. For current plan pricing, see [Serverpod Cloud pricing](https://serverpod.dev/pricing).

## Limits

- **Up to 100 manual snapshots per project.** Scheduled snapshots do not count towards this limit. When you reach it, creating another manual snapshot returns a clear error. Delete snapshots you no longer need to make room.
- **Retention defaults.** A manual snapshot created without `--expire-in` is kept until you delete it. A scheduled snapshot created without `--retention` is kept for 35 days, then deleted automatically. No schedule can keep snapshots longer than that.
- **Downgrading with stored backups.** A project that still has backups stored cannot move from the Growth plan to a smaller plan. Delete the backups first, then change the plan.
- **Moving to Starter with stored backups.** A project with stored backups can't move to Starter. Delete the backups first, then [change the plan](/cloud/concepts/plans-and-billing#change-your-projects-plan).

## Related

Expand Down
143 changes: 143 additions & 0 deletions cloud_docs/concepts/plans-and-billing.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,143 @@
---
sidebar_position: 12
title: Plans and billing
description: Plans decide which features a Serverpod Cloud project can use, and the card and billing details on your account keep every project you own running.
---

# Plans and billing

Your project's plan decides which features it can use, such as custom domains and database backups, and how far its server and database can grow. You pick a plan when you create a project, and you can change it later. Every project you own is billed to the card and billing details on your Serverpod Cloud account.

## Choose a plan

Serverpod Cloud has two standard plans, Starter and Growth. Starter fits an app before launch or a side project. Growth fits production apps, and adds features Starter doesn't include, such as custom domains, database backups, future calls, and team members. The [pricing page](https://serverpod.dev/pricing) lists what each plan includes and costs.

For needs beyond Growth, Serverpod also offers an Enterprise plan, which you arrange with the Serverpod team. The pricing page lists what it includes.

To see which plan your project is on, open its **Settings** in the [Serverpod Cloud console](https://console.serverpod.dev). The **Plan** section shows the plan's name. From the terminal, run `serverpod cloud project show` in your project's directory and look at the `Plan` row.

## Free trial

Your first Starter project includes a one-month free trial. You don't need a card or billing details until the trial ends.

Any other project, including every Growth project, needs a card and billing details when you create it. The **New project** page asks for whichever is missing.

To see when the trial ends, open the project's **Settings**. The **Plan** section shows the end date. Serverpod Cloud also emails you a reminder before it ends.

What happens when the trial ends depends on your account:

- **Billing is set up:** The project keeps running, and its monthly plan fee starts.
- **Billing isn't set up:** The project is [suspended](#why-is-my-project-suspended) right away.

To keep the project running, [set up billing](#set-up-billing) before the trial ends. Until you do, the console shows a **Set up billing** banner at the top.

## Set up billing

Your account needs a card to pay for your projects and billing details for your invoices. Your billing details are your billing address, plus your company name if you're billed as a business. Without them, an invoice can't be issued, and the project is [suspended](#why-is-my-project-suspended).

You need both to:

- Keep a project running after its [free trial](#free-trial)
- [Change a project's plan](#change-your-projects-plan)
- Create a project without a free trial

Projects you were invited to are billed to their owner, so they don't need your card or billing details.

To set up billing:

1. In the [Serverpod Cloud console](https://console.serverpod.dev), select the person icon in the top bar, then **Billing**. The **Set up billing** buttons open the same page.

<!-- screenshot: cloud-console/account-menu-billing.png. Owner: docs team. Last verified: 2026-11-16 against console.serverpod.dev. -->
<img src="/img/cloud-console/account-menu-billing.png" alt="The person icon at the right of the Serverpod Cloud console's top bar, with the account menu open below it, listing Billing, Account settings, Security, Theme, and Log out." width="337" />

2. Add your card under **Payment methods**.
3. Fill in your billing address under **Billing info**. If you're billed as a business, select **Are you a business?** and add your company name. **VAT information** is optional.
4. Under **Billing emails**, add anyone else who should get billing messages, such as trial reminders and failed payments.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment: I'm not sure if this is true @christerswahn @vfiruz97 are we using the billing email or the owner email when sending notifications like this, probably should send them to the billing emails too actually.

5. Select **Save**. Your billing info and billing emails are saved only when you do.

Once your account has a card and billing details, the **Set up billing** banner and buttons go away.

## Change your project's plan

You can move a project between Starter and Growth in either direction. The move changes which features the project can use and which monthly fee it pays.

### Before you start

Make sure:

- **You own the project:** Only the project's owner can change its plan. For anyone else, the **Upgrade plan** or **Edit plan** button is dimmed, and hovering it explains who can change the plan.
- **Billing is in order:** Your account has [billing details](#set-up-billing) and no overdue payment.

**Moving to Growth:** If the project is on its free trial, the move ends the trial.

**Moving to Starter:** First remove what Starter doesn't include:

- **Backups:** Turn off the backup schedule with `serverpod cloud db schedule unset`, then [delete every snapshot](/cloud/concepts/database-backups#delete-a-snapshot), including scheduled ones.
- **Custom domains:** [Detach them](/cloud/concepts/custom-domains#detach-a-custom-domain).
- **Team members:** Remove each one with `serverpod cloud project user revoke` followed by their email.
- **Storages:** [Delete storages](/cloud/concepts/storage#delete-a-storage) until two remain. Deleting a storage removes its files for good, so copy out anything you need first.

### Change the plan

1. In the [Serverpod Cloud console](https://console.serverpod.dev), open your project's **Settings**. On Starter, select **Upgrade plan** in the **Plan** section. On Growth, select **Edit plan**.
2. Under **Project plan**, choose the plan.
3. Review **Compute** and **Database**, because choosing a plan resets both to that plan's defaults, which are one small podlet (a running copy of your server) and the small database size. On Starter, the podlet scales to zero. On Growth, it keeps running.
4. Select **Save**. If your account has no card, the button reads **Add card and upgrade**, and the console asks for the card first.

The change can take up to a minute to apply. The **Plan** section then shows the new plan's name. If the project has been deployed, your server restarts with the new plan's settings.

If the console says "We couldn't confirm your plan change", refresh the page. If the **Plan** section still shows the old plan, check each point under [Before you start](#before-you-start). If you're moving to Starter, also check the **Moving to Starter** list.

## View your invoices

Your invoices are kept in your billing portal, a separate page that opens in a new tab. To open it, go to the [Billing page](https://console.serverpod.dev/account/billing) of the Serverpod Cloud console and select **View invoices**.

## Stop charges

A project's charges stop when you delete it, because deleting ends its plan right away. Moving the project to Starter doesn't stop them, since Starter has a monthly fee too. Fees are billed after the period they cover, so a last invoice still arrives for the time before the deletion.

Deleting a project removes its server, database, and stored files. It can't be undone, and the project ID can't be used again.

To delete a project, including a suspended one, open its **Settings** in the console and select **Delete project**. From the terminal, run `project delete` with the project ID:

```bash
serverpod cloud project delete my-app
```

## Troubleshooting

### What happens if a payment fails?

Serverpod Cloud charges your card for each invoice. When a payment fails, what happens next depends on the invoice:

- **The first invoice on a project's plan:** The project is suspended right away. This includes the first invoice after you change the project's plan, or after you switch your account between business and individual on **Billing**.
- **Later invoices:** You have 10 days to pay, counted from the day the payment first fails. Your billing emails get a message with the date the project will be suspended.

While a payment is overdue, the console shows **Payment overdue** at the top of every page. You can't create projects, add resources such as storages, or change a project's plan until it's paid. To pay, select **Manage billing** in that banner, then pay the overdue invoice in your billing portal.

### Why is my project suspended?

A suspended project's server stops, and you can't deploy to it until it's reactivated. When a project is suspended for payment or billing setup, your billing emails get a message, and they get another when it's reactivated.

The project's page shows **Project suspended** with the reason and a button, and the project list marks it **Suspended**. From the terminal, `serverpod cloud project show` prints the reason in its `Status` row.

What to do depends on the button on the project's page:

<div className="full-width-table">

| Button | Why the project is suspended | To reactivate it |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
| **Pay invoices** | A payment is overdue | Select **Pay invoices** and pay the overdue invoices in your billing portal |
| **Complete billing setup** | Your account was missing a card or billing details when the free trial ended, or billing details when an invoice was due | [Set up billing](#set-up-billing) |
| **Manage plan** | The project's plan ended | Select **Manage plan**, then choose a plan on the project's **Settings** |
| **Contact support** | Serverpod Cloud support suspended it | Contact support from the **Need help?** menu in the console's top bar |

</div>

After you pay, complete billing setup, or choose a plan, the project is reactivated, and its server starts again with its last deployment.

## Related

- [Scale to zero](/cloud/concepts/scale-to-zero): why Starter projects scale to zero when idle, and how to turn it on or off on Growth.
- [Database backups](/cloud/concepts/database-backups): the backups that Growth includes.
- [Storage](/cloud/concepts/storage): the storages each plan includes and their limits.
6 changes: 3 additions & 3 deletions cloud_docs/concepts/scale-to-zero.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Whether a project scales to zero depends on its plan:

</div>

To see whether your project scales to zero, open its **Settings** in the [Serverpod Cloud console](https://console.serverpod.dev). The **Compute** section of the **Plan** card shows the range of podlets the project can run, such as **0-1 PODLETS**. Podlets are the running copies of your server. If the range starts at 0, the project scales to zero.
To see whether your project scales to zero, open its **Settings** in the [Serverpod Cloud console](https://console.serverpod.dev). The **Compute** card in the **Plan** section shows the range of podlets the project can run, such as **0-1 PODLETS**. Podlets are the running copies of your server. If the range starts at 0, the project scales to zero.

From the terminal, run `serverpod cloud project show` in your project's directory. The `Compute` row ends with the same range, such as `0-1 podlets`.

Expand Down Expand Up @@ -126,7 +126,7 @@ The console confirms with "Your plan is updated". The change can take up to a mi

### Turn off scale to zero

Starter projects always scale to zero, and the console shows **Upgrade plan** instead of **Edit plan**. To keep your server running, move the project to Growth, which keeps one podlet running by default.
Starter projects always scale to zero, and the console shows **Upgrade plan** instead of **Edit plan**. To keep your server running, [move the project to Growth](/cloud/concepts/plans-and-billing#change-your-projects-plan), which keeps one podlet running by default.

On other plans, set **Min podlets** to 1 or more in the console:

Expand All @@ -142,4 +142,4 @@ The console confirms with "Your plan is updated". The change can take up to a mi
- [Database](/cloud/concepts/database): the managed database, which runs separately from your podlets.
- [Scheduling overview](/concepts/scheduling/overview): future calls, which need a running server.
- [CLI reference: `status` command](/cloud/reference/cli/commands/status): the `status live` command and its options.
- [Serverpod Cloud plans](https://serverpod.dev/cloud): what each plan includes and costs.
- [Plans and billing](/cloud/concepts/plans-and-billing): what each plan includes, how to change a project's plan, and how billing works.
6 changes: 3 additions & 3 deletions cloud_docs/concepts/storage.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ The **Storage** tab in the Cloud console shows the same list, and you can add an

## Add a storage

A storage you add yourself keeps files apart from the defaults, such as exports you purge on a schedule. The Starter plan includes two storages and your project already uses both, so adding more needs the **Growth** plan.
A storage you add yourself keeps files apart from the defaults, such as exports you purge on a schedule. The Starter plan includes two storages and your project already uses both, so adding more needs the [**Growth** plan](/cloud/concepts/plans-and-billing).

Add one:

Expand Down Expand Up @@ -108,9 +108,9 @@ In the console, select a storage in the **Storage** tab to browse, upload, downl
- **Storages per project.** The Starter plan includes two and Growth allows up to ten.
- **Metered usage.** Serverpod Cloud meters three things and bills them by usage: the data you store, the data read out of your storages, and the operations performed on them.
- **Going over a cap.** Caps come with the plan, and there is no setting that raises them. When a project goes over one, your server can no longer read or write any storage in the project, and public URLs stop serving. Listing, downloading and deleting keep working from the CLI and the console, so you can clear space.
- **Getting access back.** Access returns once usage is back under the cap, the month rolls over for a monthly cap, or the project moves to a plan that covers the usage. The check runs about once an hour, so it can take up to an hour. Deleting files helps when stored data is what you went over.
- **Getting access back.** Access returns once usage is back under the cap, the month rolls over for a monthly cap, or the project [moves to a plan](/cloud/concepts/plans-and-billing#change-your-projects-plan) that covers the usage. The check runs about once an hour, so it can take up to an hour. Deleting files helps when stored data is what you went over.

See [Serverpod Cloud plans](https://serverpod.dev/cloud) for the caps and prices on your plan.
See [Serverpod Cloud pricing](https://serverpod.dev/pricing) for the caps and prices on your plan.

## Related

Expand Down
2 changes: 1 addition & 1 deletion cloud_docs/getting-started/launch.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ serverpod cloud launch
It creates a Cloud project and ships its first version in these steps:

1. **Choose the project.** If your account has no projects, the command asks *"Open the browser and create a new Serverpod Cloud project?"* Press Enter to accept. If you already have projects, it lists them, with a last option to create a new project in the browser.
2. **Create the project in the Console.** If you chose to create a new project, the Console's **New project** page opens. The project ID is pre-filled from your pubspec name (for example, `my-app`), and the database is switched on if your server config has a `database` section. Change either if you need to. Pick a plan (see [Cloud plans](https://serverpod.dev/cloud)), click **Launch Project**, and return to the terminal. The project ID becomes part of your default URL (`<project-id>.serverpod.space`).
2. **Create the project in the Console.** If you chose to create a new project, the Console's **New project** page opens. The project ID is pre-filled from your pubspec name (for example, `my-app`), and the database is switched on if your server config has a `database` section. Change either if you need to. Pick a plan (see [Plans and billing](/cloud/concepts/plans-and-billing)), click **Launch Project**, and return to the terminal. The project ID becomes part of your default URL (`<project-id>.serverpod.space`).
3. **Pre-deploy hooks.** The command adds `serverpod generate` as a pre-deploy hook, plus `serverpod run flutter_build` if your server's `pubspec.yaml` defines that script. See [Deployment hooks](/cloud/concepts/deployment-hooks) for details.
4. **Custom passwords.** If `config/passwords.yaml` has custom passwords, the command asks which ones to copy to Cloud. Passwords from the `production` and `shared` sections are preselected. Set the rest later with `serverpod cloud password set`.

Expand Down
Loading
Loading