Creator and commerce decision
Gumroad
Prefer self-hosting the existing open-source repository rather than reimplementing; a competent developer can deploy a minimal replacement, but you will lose Gumroad's merchant-of-record tax handling and Discover marketplace.
Visit website↗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
- Enable creators to list digital products, accept payments, deliver files/memberships, and manage payouts/transactions.
What it still won’t have
- Merchant-of-record tax collection and remittance handled by Gumroad
- Access to Gumroad Discover marketplace and its discovery-driven customers
- Built-in tax automation and global tax remittance
- Lightweight DRM/license-key generation and integrated payouts automation
What remains hard
- Compliance and regulation
We're a Merchant of Record
First-year cost
No published price
Gumroad 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 self-hosted minimal Gumroad clone using Node.js (Express), PostgreSQL, and Stripe: implement user auth, product upload with file storage (S3), product pages, Stripe Checkout + webhook handling for one-time and recurring payments, secure downloadable links, a transactions table and CSV export, and a simple analytics dashboard. Out of scope: building a merchant-of-record tax remittance system, marketplace/discovery, and DRM beyond expiring download links. Include error handling, webhook retry logic, automated tests for payment flows, and Docker Compose for local dev.
How we checked
How the score was reached
- Self-host verdict base92
- 3 cited sources+3
- 1/1 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score96
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 · 3
Every page the run actually retrieved.
- official productGumroad homepage
- official pricingGumroad pricing
- official docsGumroad features
Integrity checks
What held up, and what did not.
