-
Notifications
You must be signed in to change notification settings - Fork 37
Create check-pricing #1325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Create check-pricing #1325
Conversation
- Based on old Check pricing section, new section to explain how the new pricing works - Explain differences between Uptime and Synthetics - Explained Prepaid bundles - Explained Overages - Added examples
@AlbertoGoYu is attempting to deploy a commit to the Checkly Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit/question inline.
- **Prepaid check bundles**: Discounted packages of check runs purchased in advance | ||
- **Overages**: Additional charges when you exceed your plan's included check runs or monitors, typically at higher rates than prepaid bundles | ||
|
||
## Pricing Table |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit afraid that keeping all the existing pricing tables in sync is gonna be hard - we already found quite some issues keeping two tables in sync. Can't we just link to the pricing page from here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, agreed I'll work in a version that refers to the Pricing page instead
|
||
Before diving into pricing details, here are key concepts that affect your costs: | ||
|
||
- **Check run**: A single execution of a check or monitor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check runs for monitors shouldn't affect cost, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
indeed, good catch
- **Retries**: Automatic re-execution of failed checks | ||
- **Flaky checks**: Checks that fail intermittently due to network issues or timing problems | ||
- **Prepaid check bundles**: Discounted packages of check runs purchased in advance | ||
- **Overages**: Additional charges when you exceed your plan's included check runs or monitors, typically at higher rates than prepaid bundles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overages don't apply for monitors (at least not yet), right? You can only create as many monitors as you purchased
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that true, I'll update that
- **Parallel scheduling**: Running checks simultaneously from multiple locations | ||
- **Retries**: Automatic re-execution of failed checks | ||
- **Flaky checks**: Checks that fail intermittently due to network issues or timing problems | ||
- **Prepaid check bundles**: Discounted packages of check runs purchased in advance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny nit, how about moving Check runs
right above this so that we consistently explains things related to check runs right below it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'll move check runs as the first item
|
||
## Uptime Monitors | ||
|
||
A given set of Uptime Checks are included in the Starter, Team, and Enterprise plans. Users can complete the existing plan allowance of Uptime Checks by adding to their plans packages of 25 monitors for $10 each. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about something like
A given set of Uptime Checks are included in the Starter, Team, and Enterprise plans. Users can complete the existing plan allowance of Uptime Checks by adding to their plans packages of 25 monitors for $10 each. | |
A set number of Uptime Checks is included in the Starter, Team, and Enterprise plans. Users can extend their plan’s allowance by adding packages of 25 monitors for $10 each. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to change that phrasing to talk more generically about monitor packages, and point to the pricing page to see the available packages
|
||
### Parallel Scheduling | ||
|
||
Parallel Scheduling on Uptime monitors is limited to Enterprise plans. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add something like contact support
with a link or so?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will add
|
||
### Retries | ||
|
||
Retries on Uptime monitors are included in the price and limited to 1 retry per monitor per run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only the case for starter and hobby according to the gSheet, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no it's for all pans, we are going to limit retries to 1 as a whole due to costs
- **API check runs** beyond your plan's monthly allowance | ||
- **Browser check runs** beyond your plan's monthly allowance | ||
- **Multistep requests** beyond your plan's monthly allowance | ||
- **Additional uptime monitors** beyond your plan's included monitors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't allow for overages on uptime checks AFAIK, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true
Co-authored-by: Manel Fourati <[email protected]>
Co-authored-by: Manel Fourati <[email protected]>
Co-authored-by: Manel Fourati <[email protected]>
Co-authored-by: Manel Fourati <[email protected]>
Addressing all comments in the PR
Affected Components
Pre-Requisites
npm run lint
)Notes for the Reviewer
New Dependency Submission
Screenshots