Creator and commerce decision
Paddle
You can implement core billing and subscription flows yourself, but reproducing Paddle’s merchant-of-record, global tax remittance, fraud liability, and scale/operational support is expensive and legally complex, so keeping Paddle is often justified for global SaaS.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off80 h to build
$100/mo40 h/mo upkeep
No published price to break even against.
The code exists. It is not what you are paying for.
These 2 projects are real, published, and do the core job — and this page still says keep paying. What the subscription buys is compliance and regulation, infrastructure at scale and brand trust, and none of that ships in a repository. Fork one anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Paddle alternatives, with the arithmetic →
What a replacement has to do
- Accept a checkout, create/manage subscription records, collect payment via gateway, generate invoices/receipts, handle basic retry/dunning.
What it still won’t have
- Merchant-of-Record legal/tax remittance and filings
- Global automated VAT/sales-tax collection and remittance
- Liability coverage for fraud and chargebacks
- Global localized checkout optimizations and local payment methods
- 24/7 payments-related customer support and managed migrations
What remains hard
- Compliance and regulation
Eliminate sales tax headaches with full, automatic global tax compliance
- Infrastructure at scale
190 million transactions processed
- Brand trust
10,000+ customers using Paddle
First-year cost
No published price
Paddle does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a merchant-of-record-lite using Node.js + Express, PostgreSQL, and a payment gateway (e.g., Stripe). Implement: (1) hosted checkout page + webhook handlers, (2) subscription billing engine with proration and plan management, (3) transaction and invoice records in Postgres, (4) a simple dunning worker to retry failed payments and send emails, (5) a customer portal to update payment methods and cancel/upgrade subscriptions. Out of scope: global automated tax remittance filings, acting as legal Merchant-of-Record, full fraud liability coverage, and multi-country localized payment optimizations. Include error handling, idempotent webhook processing, basic automated tests, and deployment scripts (Docker + single VPS or managed DB).
How we checked
How the score was reached
- Pay verdict base20
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Hard moats found in the evidence-6
- Evidence score25
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productPaddle - Subscriptions, Payments & Tax Compliance for SaaS & Mobile Apps
- official pricingAll-in-One Pricing, No Hidden Costs | Paddle
- official docsSaaS Subscription Management Software | Paddle
- open sourcegetlago/lago
- open sourcekillbill/killbill
Integrity checks
What held up, and what did not.
