docs.heartbadge.com
HeartBadge Documentation
Self-verifying identity and rewards infrastructure.
Pick your path
Audience-first navigation. Task-first pages.
Start Here
I'm new or evaluating.
What HeartBadge is, how it works, the language we use, and how feature maturity is marked.
Go to Start Here
Members
I have, or I'm about to have, a badge.
HeartDash, activation, rewards, HeartBeat status, gifts, groups, security, and support.
Go to Members
Program Operators
I want to run a program on HeartBadge.
Membership-as-a-Service — infrastructure for communities, events, venues, and enterprises.
Go to Program Operators
Developers
I'm building on top of HeartBadge.
API reference, SDKs, guides, webhooks, and the concepts behind the surface.
Go to Developers
Trust & Architecture
I need the technical and trust surface.
Three-chain design, covenants, SPV, custody posture, audits, and responsible disclosure.
Go to Trust & Architecture
Updates
What changed, and what's next.
Changelogs, operational notices, and horizon roadmap context.
Go to Updates
How maturity is shown
Rings are status, not navigation.
Every capability sits under the audience who uses it. Release maturity appears on the page itself so you never treat a roadmap item as a how-to for today.
Read feature status guideRing 1 — Core Heartbeat
LiveShipped, tested, load-bearing. Written in present tense.
Ring 2 — Next Pulse
Rolling outIn active development. Clearly marked on the canonical page.
Ring 3 — Horizon
HorizonArchitecturally designed, not yet member-facing. Overview only.