Like most developers, I have more unfinished projects than finished ones.
I realized one day that I have 47 GitHub repositories. Maybe 4 are "done." The rest? Digital monuments to ambition, distraction, and 3am ideas that seemed brilliant at the time. Repos with names like "new-project-v2-final-actually-final" and "this-time-for-real."
The question hit me: What happens to these when I'm gone?
My sister codes too. When I go, she'll dig through the digital graveyard and laugh at how many WIPs I left behind—maybe even finish or fork a few. She knows that repos like "leetcode-day-347" aren't discipline; they're stubborn curiosity and messy iteration. That's the real story.
I wanted control over my digital legacy. Not because the world needs my half-baked Discord bot or my incomplete task manager (version 12). But because these repos—WIPs and all—are proof I was here, I was learning, I was trying.
Every developer dies twice. Once when they stop breathing, and once when their last git push is forgotten.
So I built OnDeath.dev: a service that monitors payment failures and triggers webhooks. When my credit card stops working (because I'm not around to pay it), my webhooks fire. Repos go public. Sister gets access. Digital legacy preserved.
Not because the world needs my 347th TODO.md file. But because the digital artifacts of a life spent coding deserve to outlive the coder, even if they're embarrassing.
Because eventually, everyone misses a payment.
— Lotfi, Founder