Repository navigation
docs: Add a Plans and billing page for Serverpod Cloud - #924
developerjamiu wants to merge 3 commits into
Conversation
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
left a comment
There was a problem hiding this comment.
Nice! Some smaller comments and I tagged the team to validate one point.
| | 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 | |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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). |
There was a problem hiding this comment.
Suggestion: This reads very AI-like, especially "has two parts:"
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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**. |
There was a problem hiding this comment.
Suggestion: Link to the billing page there is a button there called "View invoices" which opens the billing portal.
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.
/cloud/concepts/plans-and-billing, in the Concepts sidebar.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.docs/. The second holds the copies in bothversioned_docs/trees, and the third addresses the review.