Skip to content

chore(site): update pricing page with Actions and remove compute billing #3266

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(site): update pricing page with Actions and remove compute billing #3266

wants to merge 1 commit into from
+140 −92

Conversation

@NicholasKissel
Copy link
Member

  • Updated pricing structure to include Actions with 1M limit on free tier and 1M included for paid plans
  • Removed compute billing from pricing model
  • Updated pricing calculator to include Actions with allowance
  • Updated documentation to reflect new Actions pricing structure
  • Updated all pricing displays and calculations

@NicholasKissel
chore(site): update pricing page with Actions and remove compute billing
ebfbb55 
- Updated pricing structure to include Actions with 1M limit on free tier and 1M included for paid plans
- Removed compute billing from pricing model
- Updated pricing calculator to include Actions with allowance
- Updated documentation to reflect new Actions pricing structure
- Updated all pricing displays and calculations
@vercel
Copy link

vercel bot commented Oct 26, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
rivet-site Ready Ready Preview Comment Oct 26, 2025 3:52am
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
rivet-cloud Ignored Ignored Oct 26, 2025 3:52am
rivet-inspector Ignored Ignored Preview Oct 26, 2025 3:52am

@NicholasKissel Graphite App
Copy link
Member Author

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@NicholasKissel NicholasKissel marked this pull request as ready for review October 26, 2025 03:49
@claude
Copy link

claude bot commented Oct 26, 2025

PR Review: Pricing Page Updates

Summary

This PR updates the pricing structure to include Actions billing and removes compute billing. The changes are spread across documentation and website pricing components.

Positive Aspects

  1. Consistent terminology: Good use of "Save State Reads/Writes" terminology throughout all files
  2. Well-structured documentation: The new pricing.md file is clear and includes helpful FAQs
  3. Calculator updates: The pricing calculator correctly implements the new pricing model without the compute components

Potential Issues

1. Inconsistent pricing information (Critical)

There is a discrepancy in the Save State Reads pricing between files:

  • pricing.md (line 26): $0.20 per million reads
  • PricingPageClient.tsx (line 438): $1.00 per billion reads
  • PricingCalculator.tsx (line 11): COST_PER_MILLION_READS = 0.2

Calculation: $0.20 per million = $200 per billion, NOT $1.00 per billion

This is a significant pricing inconsistency that needs to be resolved. Either:

  • Change line 438 in PricingPageClient.tsx to $0.20 per million reads, OR
  • Update pricing.md and PricingCalculator.tsx to use $1.00 per billion

Recommendation: Use consistent units across all files. I suggest using "per million" for consistency with other metrics.

2. Missing bandwidth allowance in calculator (Minor)

The pricing calculator notes "10 GB bandwidth included" (line 96 in PricingCalculator.tsx), but the documentation doesn't clearly state this allowance in the pricing tables. The calculator hardcodes this on line 23:

const bandwidthCost = Math.max(0, bandwidthGB - 10) * COST_PER_GB_BW;

However, this 10GB allowance isn't documented in pricing.md or clearly shown in the tier comparison tables.

3. Documentation formatting issue (Minor)

In pricing.md line 42, the table formatting is broken in the "Usage" column. The calculation is all on one line making it hard to read:

10GB × $0.40 = $4.00(5M–1M) reads = $0.80(1M–1M) writes = $0.00

Consider adding line breaks or restructuring the table for better readability.

Suggestions

1. Add validation/tests

Consider adding unit tests for the calculateCost function in PricingCalculator.tsx to ensure pricing calculations remain accurate.

2. Clarify Actions applicability

The docs state "Applies to Actor actions and workflow executions" but it would be helpful to clarify if Functions and Containers are billed for actions too, or if this is Actor-specific.

3. Consider adding storage allowance to pricing tables

Currently, the tiers show "5GB Storage included/limit" but the usage pricing table doesn't mention any storage allowance. Are the first 5GB free? This should be clarified.

Code Quality

  • Indentation: Properly formatted
  • Naming: Clear and consistent variable names
  • Structure: Good component organization

Testing Recommendations

  1. Verify all pricing calculations manually
  2. Test the calculator UI with various inputs to ensure the totals are accurate
  3. Cross-reference all pricing numbers across all three files
  4. Check the responsive design of the new pricing table sections

Action Items

Must fix before merge:

  • Resolve the Save State Reads pricing discrepancy

Should consider:

  • Document the 10GB bandwidth allowance clearly
  • Fix the table formatting in pricing.md
  • Clarify storage allowance in the pricing model

Overall, this is a clean pricing update, but the critical pricing discrepancy needs to be resolved before merging to avoid customer confusion and potential revenue loss.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 26, 2025

More templates

@rivetkit/actor

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/actor@3266

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@3266

@rivetkit/core

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/core@3266

@rivetkit/db

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/db@3266

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@3266

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@3266

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@3266

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@3266

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@3266

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@3266

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@3266

commit: ebfbb55

@graphite-app
Copy link
Contributor

graphite-app bot commented Oct 29, 2025 •
edited
Loading

Merge activity

  • Oct 29, 9:46 PM UTC: NicholasKissel added this pull request to the Graphite merge queue.
  • Oct 29, 9:47 PM UTC: CI is running for this pull request on a draft pull request (#3285) due to your merge queue CI optimization settings.
  • Oct 29, 10:08 PM UTC: The Graphite merge queue couldn't merge this PR because it was not satisfying all requirements (Failed CI (Check)).

graphite-app bot pushed a commit that referenced this pull request Oct 29, 2025
@NicholasKissel
chore(site): update pricing page with Actions and remove compute bill…
6e64f73 
…ing (#3266)

- Updated pricing structure to include Actions with 1M limit on free tier and 1M included for paid plans
- Removed compute billing from pricing model
- Updated pricing calculator to include Actions with allowance
- Updated documentation to reflect new Actions pricing structure
- Updated all pricing displays and calculations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@NathanFlurry NathanFlurry Awaiting requested review from NathanFlurry

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@NicholasKissel