Skip to content

Postgres-sync pricing exercise#4041

Draft
balegas wants to merge 25 commits intomainfrom
claude/pricing-plans-breakdown-fEJaq
Draft

Postgres-sync pricing exercise#4041
balegas wants to merge 25 commits intomainfrom
claude/pricing-plans-breakdown-fEJaq

Conversation

@balegas
Copy link
Copy Markdown
Contributor

@balegas balegas commented Mar 23, 2026

Note: This is a proposal that has not been discussed yet.

Summary

  • Fill in plan card content (features, target audience) for PAYG, Pro, and Scale tiers
  • Split write pricing into per-service rates: $1/1M for Durable Streams (baseline) vs $3/1M for Postgres Sync (premium, due to shape filtering compute cost)
  • Add max shapes limit per tier: PAYG 10K, Pro 100K, Scale/Enterprise unlimited
  • Tier discounts apply to both service rates (Pro 10%, Scale 20%)

Changes

  • website/data/pricing.yaml — two base write rates per service
  • website/data/pricing.data.ts — compute effective rates for both services
  • website/data/plans/*.yaml — plan cards with real content, shapes limits
  • website/src/components/pricing/ComparisonTable.vue — separate write rate rows + shapes row
  • website/src/components/pricing/PricingCalculator.vue — per-service write volume inputs

thruflo and others added 17 commits March 6, 2026 13:29
Replace Lorem ipsum placeholders with real feature bullet points
and target audience descriptions for each pricing tier.

https://claude.ai/code/session_018BN3sP9BUYKkLiCmErHK8Z
Filtering operations in Electric (Postgres streams) are significantly
more compute-intensive than simple appends to durable streams, which
justifies the higher base rate.

https://claude.ai/code/session_018BN3sP9BUYKkLiCmErHK8Z
…es Sync

Durable Streams writes stay at the $1/1M baseline. Postgres Sync writes
carry a $3/1M premium because shape filtering is significantly more
compute-intensive than a simple stream append.

- pricing.yaml: two base rates (durableStreamsWritesPerMillion, postgresSyncWritesPerMillion)
- pricing.data.ts: compute effective rates for both services per tier
- ComparisonTable: show separate write rate rows per service
- PricingCalculator: separate write volume inputs per service
- PAYG plan card: split pricing bullet into per-service lines

https://claude.ai/code/session_018BN3sP9BUYKkLiCmErHK8Z
- PAYG: 10K shapes
- Pro: 100K shapes
- Scale: contact sales for custom quote
- Enterprise: unlimited

https://claude.ai/code/session_018BN3sP9BUYKkLiCmErHK8Z
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 23, 2026

Deploy Preview for electric-next ready!

Name Link
🔨 Latest commit d6ef2ac
🔍 Latest deploy log https://app.netlify.com/projects/electric-next/deploys/69c14df643b69300085e766a
😎 Deploy Preview https://deploy-preview-4041--electric-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@msfstef
Copy link
Copy Markdown
Contributor

msfstef commented Mar 23, 2026

small note: counting postgres writes as 3 write units would also be slightly simpler for billing (to avoid introducing a separate invoice line) and maintain observability and breakdown at dashboard level

@balegas
Copy link
Copy Markdown
Contributor Author

balegas commented Mar 23, 2026

I specifically wanted to not model 1 postgres write as a cost of 3 durable stream writes because that is a bad mental model.

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.

4 participants