Creator and commerce decision
Heartbeat
A small team can implement a narrow Heartbeat replacement (pages, payments, courses, and basic chat) in several weeks, but the hosted AI co‑builder, white‑label apps, managed onboarding, and polished platform experience are costly to reproduce and justify continuing to pay for Heartbeat for those capabilities.
Visit website↗No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Allow creators to publish landing pages, accept payments, host courses, and run community channels where members interact.
What it still won’t have
- Pulse AI co‑builder (hosted AI actions and prompt-to-page automation)
- Hosted white‑label mobile app and app store delivery service
- Built-in native video hosting at scale
- Existing customer community, migration assistance, and managed onboarding
- Heartbeat transactional fees and integrated analytics/priority support
What remains hard
- Brand trust
Trusted by 25,000+ businesses and creators.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
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 minimal community SaaS on PostgreSQL + Node.js (Express) + Next.js. Implement: user signup and Stripe subscriptions (webhooks), member directory and tiers, channels with threaded posts and basic real-time via WebSocket, a simple course/content model with lesson pages and video embedding, and a WYSIWYG landing page template editor wired to create checkout links. Exclude: mobile native apps, AI co‑builder, and large-scale video storage (use 3rd‑party host). Provide error handling, webhook replay protection, tests for auth, payments, and core flows, and Docker deployment manifests for a single VPS.
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Price verified on pricing page+3
- Evidence score58
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 productHeartbeat — product home
- official pricingHeartbeat pricing
- official docsHeartbeat landing pages feature
Integrity checks
What held up, and what did not.
