feat(features): add a pricing page & calculator #92
+423
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nermalcat69
changed the title
|
I'll look into the calculator tomorrow! 💯 |
vankovap
reviewed
Nov 24, 2024
|
|
||
| If you hit the limits of **backup/build/egress** in a project you'll pay: | ||
|
|
||
| - **$0.50** - per **5 GB** of backup space |
There was a problem hiding this comment.
can you use the word 'extra' for each of the resources? Just in case someone is confused
e.g. $0.50 - per 5 GB of extra backup space
|
|
||
| ## Projects | ||
|
|
||
| A [project](/features/infrastructure#project) is the internal **infrastructure**, dedicated for your **services**. Think of it as a private network where you can deploy your services inside and interact with each other. |
There was a problem hiding this comment.
I am not entirely sure about this paragraph. I would prefer it to be more straight-forward. What I want a reader to find out is:
- that a project is mandatory, because it provides fundamental functionality for services within the project to work properly
- you can have one or more projects
- that the total price of each project consists of the project's core package price + cost of resources of the services within the project (+ extra costs)
- how much each project core package actually costs
Maybe you could move the third point above the ##Projects heading? Just an idea. What do you think?
| </tr> | ||
| <tr> | ||
| <td className="w-fit whitespace-nowrap"><strong>Object Storage</strong></td> | ||
| <td><strong>$0.01</strong> / GB</td> |
There was a problem hiding this comment.
it's also per 30 days, since it's mentioned everywhere else
add a table to differentiate lightweight and serious core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Type of Change is this?
Description (required)
add a pricing page to the features section of the docs
Related issues & labels (optional)