Can Heartbeat be vibe coded?
Run a private community with channels, events, courses, and lightweight workflows
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Heartbeat, run a private community with channels, events, courses, and lightweight workflows. The hard boundary is mobile apps, automations, analytics, payments, and community onboarding, plus network, moderation, and communication infrastructure.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Host a private community with channels, events, courses, and lightweight workflows, organize discussion by topic, and keep membership and moderation under the owner's control.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- mobile apps, automations, analytics, payments, and community onboarding
- network effects
- native mobile apps
- video and voice infrastructure
- The value comes from the people already using it.
- Reliability at the vendor's scale is an operations problem, not a prompt.
Why people still pay
People still pay for Heartbeat because community software is valuable when members are already there and the operator does not have to own realtime reliability and abuse response. The recurring cost buys realtime delivery, notifications, abuse handling, search, media, permissions, mobile clients, backups, and community operations, not just the visible interface.
The value comes from the people already using it.
Reliability at the vendor's scale is an operations problem, not a prompt.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Heartbeat
Context
**Heartbeat** — Run a private community with channels, events, courses, and lightweight workflows. It currently costs $49/mo.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Heartbeat, run a private community with channels, events, courses, and lightweight workflows. The hard boundary is mobile apps, automations, analytics, payments, and community onboarding, plus network, moderation, and communication infrastructure.
This brief describes a focused, single-operator replacement for the part of Heartbeat that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Host a private community with channels, events, courses, and lightweight workflows, organize discussion by topic, and keep membership and moderation under the owner's control.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Docker.
PostgreSQL.
Public HTTPS deployment.
Email provider.
Object storage for attachments.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a personal replacement for Heartbeat in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks.
The core loop is: host a private community with channels, events, courses, and lightweight workflows, organize discussion by topic, and keep membership and moderation under the owner's control.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations.
Use WebSockets for live updates but preserve every message transactionally in PostgreSQL.
Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
Provide email digests, browser notifications, search, pinned content, and member export.
Add owner-controlled retention, account deletion, backup, restore, and health checks.
Ship Docker Compose with a seeded demo, migrations, and an emergency admin command.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out public-network discovery and existing member liquidity.
Deliberately leave out production voice or video rooms.
Deliberately leave out native mobile applications, enterprise SSO, and 24-hour abuse operations.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Mobile apps, automations, analytics, payments, and community onboarding.
Network effects.
Native mobile apps.
Video and voice infrastructure.
The value comes from the people already using it.
Reliability at the vendor's scale is an operations problem, not a prompt.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Discourse](https://github.com/discourse/discourse) — Mature open-source community discussion platform with strong moderation and search
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/heartbeat-community
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Open-source prior art
Before you start
Can Heartbeat be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Heartbeat, run a private community with channels, events, courses, and lightweight workflows. The hard boundary is mobile apps, automations, analytics, payments, and community onboarding, plus network, moderation, and communication infrastructure.
What can an AI coding agent reproduce from Heartbeat?
Host a private community with channels, events, courses, and lightweight workflows, organize discussion by topic, and keep membership and moderation under the owner's control. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Heartbeat replacement still be missing?
mobile apps, automations, analytics, payments, and community onboarding; network effects; native mobile apps; video and voice infrastructure; The value comes from the people already using it.; Reliability at the vendor's scale is an operations problem, not a prompt.
What do I still own after building a Heartbeat alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.