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
SubscriptionCustom pricing
Initial build80 hours
Monthly upkeep40 hours + $100
Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

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 regulationEliminate sales tax headaches with full, automatic global tax compliance
  • Infrastructure at scale190 million transactions processed
  • Brand trust10,000+ customers using Paddle
Read the build prompt

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

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

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

Not run yet
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 checked5 sources · 2/3 runs agreed · evidence score 25

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 →

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 3 moats quoted from the page