Skip to content

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

@vercel
Copy link

vercel bot commented Oct 26, 2025

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

Project Deployment Preview Comments Updated (UTC)
rivet-site Ready Ready Preview Comment Nov 1, 2025 0:54am
rivetkit-serverless Error Error Nov 1, 2025 0:54am
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
rivet-cloud Ignored Ignored Nov 1, 2025 0:54am
rivet-inspector Ignored Ignored Preview Nov 1, 2025 0:54am

Copy link
Member Author

NicholasKissel commented Oct 26, 2025


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

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
…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
- 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
@claude
Copy link

claude bot commented Nov 1, 2025

Code Review - PR #3266

Summary

This PR updates the pricing structure to include Actions billing and removes compute-based billing. Overall, the changes are well-structured and consistent across documentation and UI components.


✅ Strengths

  1. Consistent Terminology: The change from generic "Reads/Writes" to "Save State Reads/Writes" throughout all files improves clarity and reduces ambiguity.

  2. Documentation: The new pricing.md file is comprehensive and well-structured with:

    • Clear product descriptions
    • Helpful sample scenarios
    • FAQ section explaining new concepts
    • Consistent formatting and tables
  3. Aligned Changes: All three files (docs, pricing page, calculator) are updated consistently with the new pricing model.

  4. Simplified Calculator: Removing compute-based calculations (memory/requests/duration) simplifies the pricing model and makes it more straightforward for users.


🐛 Issues Found

1. Inconsistent Pricing Values (High Priority)

Location: website/src/app/(v2)/(marketing)/pricing/PricingPageClient.tsx:435-437

The pricing table shows:

Save State Reads: $1.00 per billion reads

But the pricing.md documentation states:

Save State Reads: 1M included, then $0.20 per million

Issue: These values don't align. If $0.20 per million = $200 per billion, not $1.00 per billion.

Recommendation: Verify the correct pricing and ensure consistency. The PricingCalculator.tsx uses COST_PER_MILLION_READS = 0.2, which aligns with the docs but not the display table.

2. Missing Newline at End of File

Location: site/public/docs/cloud-ee/pricing.md:71

The file ends without a newline character. While not critical, this is a common convention in version control.

3. Indentation Inconsistency

Location: website/src/app/(v2)/(marketing)/pricing/PricingPageClient.tsx:441-464

The indentation changed from tabs to mixed spacing. The diff shows removal of tabs followed by re-addition with different indentation. According to CLAUDE.md, Rust uses hard tabs, but this is TypeScript/TSX. However, consistency within the file should be maintained.


💡 Suggestions

1. Pricing Constant Discrepancy

Location: website/src/components/PricingCalculator.tsx:9-13

const COST_PER_GB_BW = 0.15;
const COST_PER_MILLION_READS = 0.2;
const COST_PER_MILLION_WRITES = 1.0;
const COST_PER_GB_MONTH = 0.40;

The bandwidth cost changed from $0.05 to $0.15, but the comment on line 92 still says:

Note: 10 GB bandwidth included, $0.15/GB for additional

This is now correct, but verify that the 10GB included allowance is accurate for all tiers.

2. Bandwidth Allowance Clarification

Location: website/src/components/PricingCalculator.tsx:25

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

The code assumes 10GB is always included, but the pricing tiers show different egress limits:

  • Free: 100GB Limit
  • Hobby/Team: 1TB included
  • Enterprise: Custom

Recommendation: Either document that the calculator is simplified or adjust the logic to match tier-specific allowances.

3. Storage Cost Changed

The storage cost changed from $0.20 to $0.40 per GB-month (doubled). Ensure this is intentional and documented in release notes if applicable.


🔒 Security Considerations

No security concerns identified. This PR only updates pricing display logic and documentation.


🧪 Test Coverage

Recommendation: Consider adding/updating tests for:

  1. Pricing calculations in the calculator component
  2. Verification that displayed pricing matches calculation constants
  3. Edge cases (e.g., zero usage, exactly at allowance limits)

📋 Action Items

Must Fix:

  • Resolve the Save State Reads pricing discrepancy ($1.00 vs $0.20 per million/billion)
  • Add newline at end of pricing.md file

Nice to Have:

  • Clarify bandwidth allowance logic in calculator
  • Add unit tests for pricing calculations
  • Verify storage cost doubling is intentional

Overall, this is a solid PR with good consistency across files. The main blocker is the pricing value discrepancy that needs resolution before merging.

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