The lane between community and crisis.
Embertide sits in the lane between peer community and a crisis-line handoff — the one place a watched member needs a continuous loop, a rule-based risk surface, and a routed human cascade before the cascade opens. Most recovery-companion tools own a slice of that lane; the comparison below shows which slice each one owns, and which slice it hands off.
Most tools sit at the edges. The lane in the middle is the one that fails first.
A peer community is great at the everyday — but it does not own a multi-day risk surface or an overnight escalation. A crisis text line is great at the worst day — but it does not see the days that led to it. An FDA-cleared DTx app is great at adherence — but it cannot route a voice when adherence breaks. A monthly clinical check-in is great at the clinic visit — but it leaves a 30-day window unwatched. Embertide owns the lane between them: continuous, rule-scored, routed, overnight, auditable — no handoff, no silent hours.
Five capabilities × five tools. Each cell names what is — and what is missing.
Embertide and four archetypal recovery-companion surfaces, scored against the five capabilities a member needs on the worst day before the worst day. A check means the capability is end-to-end present; an em-dash is the gap the column is asking for; a half-cell is where the surface owns part of the capability but not the rung the cascade needs.
If you run a recovery network, this is the watch that owns the lane.
Send your cohort size, your responder chain, and a short note on the dark-hour window you want closed first. We’ll come back with a 90-day pilot scope and the audit-trail surface your reviewer will want to see.
What to send
- · Cohort size and clinical profile
- · Current responder chain and where it goes quiet
- · Your 90-day success metric
- · The off-hours window you want owned first