Skip to content

docs: Add a Plans and billing page for Serverpod Cloud - #924

Open
developerjamiu wants to merge 3 commits into
mainfrom
docs/plans-and-billing
Open

developerjamiu wants to merge 3 commits into
mainfrom
docs/plans-and-billing

Conversation

@developerjamiu

@developerjamiu developerjamiu commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Adds a Cloud concept page for choosing and changing a project's plan and for setting up billing. It follows up on #919, where the Scale to zero page needed a page to send Starter readers to instead of carrying plan-change steps.

  • New page: /cloud/concepts/plans-and-billing, in the Concepts sidebar.
  • It covers which plan fits which project, the free trial, setting up billing, changing a plan, viewing invoices, stopping charges, and what to do when a payment fails or a project is suspended.
  • Console steps follow the rule agreed on Slack: they say where each feature lives and what the screen doesn't show, without field-by-field walkthroughs. One screenshot shows the account menu, where Billing lives.
  • Scale to zero, Recover from a failed deploy, Launch, Database backups, Storage, and the Cloud landing page now link here. The framework pages on scheduling and deploying to Serverpod Cloud do too, in docs/ and both versioned copies. On Scale to zero, the Compute line now reads "the Compute card in the Plan section", to match the console.
  • It's a concept page rather than the Plans and pricing reference page the Cloud docs structure planned, because it carries tasks, such as setting up billing, changing a plan, and stopping charges. What each plan includes and costs stays on serverpod.dev/pricing, and the page links there instead of copying it.
  • The page glosses podlets in one phrase only. A Compute page that explains podlets, podlet sizes, and the autoscaling range comes next as its own PR, and this page will link to it.
  • The first commit holds the Cloud page, its links, and the source edits in docs/. The second holds the copies in both versioned_docs/ trees, and the third addresses the review.

Copies the docs/ link edits from the previous commit into
versioned_docs/version-4.1.0 and versioned_docs/version-4.0.0 by hand.

@Isakdl Isakdl left a comment

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.

Nice! Some smaller comments and I tagged the team to validate one point.

Comment on lines +19 to +28
| Feature | Starter | Growth |
| ------------------------------------------------------------ | --------------------------------------------- | -------------------------------------------------------------------- |
| Podlets, the copies of your server that handle requests | One small podlet | Choose the podlet size, and run up to 20 podlets during busy periods |
| [Scale to zero](/cloud/concepts/scale-to-zero) | On, can't be turned off | Off by default, can be turned on |
| [Database](/cloud/concepts/database), optional on both plans | One small database with up to 2 GB of storage | Choose the size |
| [Database backups](/cloud/concepts/database-backups) | Not available | Available |
| [Future calls](/concepts/scheduling/overview) | Not available | Available |
| [Custom domains](/cloud/concepts/custom-domains) | Not available | Available |
| Team members | Only you | Invite others to the project |
| [Storages](/cloud/concepts/storage#limits) | Two, with usage caps | Up to ten, no usage caps |

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.

Do we really want to put this inside the docs? The issue with it being, we have a lot of places to update when we make changes to a plan. website, console, backend, docs. Hard to keep in sync.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Agreed. Removed the table and linked the pricing page for what each plan includes and costs. One sentence still names the features only Growth has, since most feature pages don't say which plan they need.


## Set up billing

Billing has two parts: a card that pays 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).

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.

Suggestion: This reads very AI-like, especially "has two parts:"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Rewritten without the colon.


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.


## View your invoices

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

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.

Suggestion: Link to the billing page there is a button there called "View invoices" which opens the billing portal.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Applied.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants