The second one tested it; the first one is why I built it.
My mom had her first knee replacement in 2024. I tried to keep family in the loop. I didn’t do it well. I hate group texts; I didn’t want to text everyone individually; I didn’t want to send a dozen emails. I sent one email to everyone. The communication was real, but it was lousy.
CaringBridge was the obvious choice, and I’d used it before. It felt heavy, especially for the person doing the communicating. The caretaker is already the most tired person on the chain, and the tool was asking too much.
When the second surgery was on the calendar, I found a tool that could fill in the parts I didn’t know how to write. Node, mostly. I built it in March 2026 and called it FamilyRally because that’s what was actually happening: a small group of people rallying around someone going through it. The name is the use case.
Three days in April
The day before surgery. The morning of. The recovery-room update when my mom woke up. Two more days of “she’s eating, she’s moving, she really liked the sweet potatoes from the hospital.”
My mom is the patient. Her partner is the caretaker; he was the one with the up-close information, and he texted me what was happening so I could broadcast it through FamilyRally. The subscriber list was small: relatives and mom’s friends. They got the email when I posted; they didn’t have to come back and check. They left short notes of encouragement on the page, which my mom got to read later, on her own time.
When my mom was clear-headed enough for individual texts, I wrote a final update that said, more or less: I’m done broadcasting; she’d love to hear from you directly now. That ending matters. A coordination tool that doesn’t know how to wind itself down becomes more work for the person it was supposed to help.
Two folks texted me afterward to let me know the tool worked well for them. That’s the only signal that counted for v1.
What I left out, and why
The point of FamilyRally is restraint. It doesn’t have a chat. It doesn’t have comment threads on individual updates. Each absence was deliberate.
What I was optimizing for is a caretaker, often a partner, often exhausted, being able to push one update without thinking about who’s seen it, who’s replied, who hasn’t. The fewer features, the easier it is to use.
Email had its own troubles in April; at least one notification ended up in a spam folder and couldn’t be found. I’m working on that.
The reason FamilyRally exists is that I had a real problem in 2024 and didn’t have the time, the space, or the tools to build my way out of it. The tools caught up; the problem hadn’t gone anywhere.
If you’ve used FamilyRally and have something to say about it, I’d like to hear from you. familyrally.org.