Model Patreon-gated Babesky tiers, promo pricing, feature cost/ROI, partner splits, and rough infrastructure costs across Railway, Railway Postgres, Cloudflare D1, and Tigris. Built for founder planning, not accounting.
Add, remove, and experiment with fewer or more tiers. Promo fields let you model discounted entry pricing on any paid tier.
Partners and reserves
Split the after-tax profit across founders, reserve buckets, or any other recipient.
Split total: 100%
Cloud cost assumptions
Defaults below are based on May 2026 published pricing and intentionally assume you are not using the absolute cheapest/most optimized setup.
Gross monthly revenue
$0
Before Patreon and processing fees.
Net after Patreon + processor
$0
Effective take-home rate: 0%
Infra + platform costs
$0
Railway + Postgres + D1 + Tigris
After tax pool to split
$0
Tax reserve: $0
Revenue waterfall
Feature matrix
All current route-level features from the Babesky app, with toggles, tier assignment, rough cost weighting, and ROI fields.
Feature
On
Tier
Traffic
Storage
Dev hrs
$ / hr
Monthly support
One-time dev cost
Monthly burden
Breakeven subs
Tier outcomes
Tier
Subs
Price
Promo mix
Gross
Net
Feature load
Score
Partner split
Recipient
%
Amount
Scenario comparison
Save multiple pricing layouts and compare them locally in your browser.
This tool uses rough founder-planning formulas. Railway defaults use published May 2026 pricing for subscription, RAM, CPU, egress, and volume usage. D1 defaults use row-read, row-write, and storage billing with included paid-plan allowances. Tigris defaults use standard storage, request pricing, and free egress. Because you asked to assume a not-optimized stack, the calculator includes traffic and inefficiency multipliers so you can intentionally stress test pricing instead of only modeling the best case.