Your health, finally in one place. Forward your lab reports on WhatsApp. Spinachi sorts them for you and your family.
See where you stand, how it's changing, and when your next test is due. No app. Never a diagnosis.
Hi Product Hunt, I'm Chinmay, the maker of Spinachi.
A few months ago I broke my shoulder, and the recovery turned into a pile of scans, prescriptions, and lab reports. At the same time I was managing my parents' health documents too. Keeping all of it organised, and remembering what was due when, became a recurring headache for months.
So I built Spinachi. Think of it as a Google Drive for your medical records, on WhatsApp. You forward your lab reports and prescriptions, and it organises them for you and your family and reminds you when a retest is due. No app to download, and it never gives a diagnosis.
It's early and I'm sharing it with friends first. I'd love to hear how you currently manage health records for yourself or your parents, and what would make this more useful. Thanks for taking a look!
Spinachi wouldn't have launched this fast without GCP. We're two engineers, and we went from first commit to a live WhatsApp health product in under three weeks. That only worked because we never had to think about infrastructure.
Cloud Run let us ship every idea the day we built it: push a container, and it's live. No servers to manage, no ops work, no DevOps hire. Scale-to-zero kept our costs close to nothing while we were testing with friends, which mattered a lot for an unfunded team.
It also gave us confidence. We handle people's medical reports, so it mattered that our services are private by default and that all health data stays in India, in the Mumbai region. And on launch day we're not worried about a traffic spike, because Cloud Run scales on its own.
GCP took care of the infrastructure, so our time went into the product.
Report
@chinmay3199 I couldn't agree more. I have built on Google Cloud Infrastructure and it was a breeze. GCP offers granular security controls that make configuration much easier.
Quick question: keeping health data in Mumbai region covers data residency, but how did you handle privacy beyond that? WhatsApp sits in the data path, so what stays on WhatsApp / Meta versus your own infrastructure, and do reports or data reach external APIs?
@richatsealedvault Thanks, Richard. That’s an important distinction, medical records are highly sensitive personal information, and protecting them is a core engineering priority.
We keeps a user’s reports and prescriptions together so they can retrieve records and track changes over time. Their dashboard presents those records, with a verification code sent to their WhatsApp making sure only the legit user gets the access.
We don’t use users’ health records to train models. However, that’s separate from processing, WhatsApp/Meta handles the messages and attachments exchanged with us. We are using Claude Haiku to process relevant information to provide the service. We store health facts like smoking, drinking etc to maintain continuity across conversations, those facts can form part of the context provided to our AI services.
Would love to take your insights on what you think more on this. Cheers
Report
@chinmay3199 Thanks for the quick response, Chinmay. I appreciate your openness about the WhatsApp messaging boundary, the model usage, and the authentication trade-off. This kind of transparency builds trust.
Personally, I think balancing privacy with accessibility is genuinely hard, and I think you've built something unique. Once the data flow and retention are clearly explained to users, I expect anyone trying the product to feel confident. Congratulations and good luck with the launch.
Replies
@chinmay3199 I couldn't agree more. I have built on Google Cloud Infrastructure and it was a breeze. GCP offers granular security controls that make configuration much easier.
Quick question: keeping health data in Mumbai region covers data residency, but how did you handle privacy beyond that? WhatsApp sits in the data path, so what stays on WhatsApp / Meta versus your own infrastructure, and do reports or data reach external APIs?
@richatsealedvault Thanks, Richard. That’s an important distinction, medical records are highly sensitive personal information, and protecting them is a core engineering priority.
We keeps a user’s reports and prescriptions together so they can retrieve records and track changes over time. Their dashboard presents those records, with a verification code sent to their WhatsApp making sure only the legit user gets the access.
We don’t use users’ health records to train models. However, that’s separate from processing, WhatsApp/Meta handles the messages and attachments exchanged with us. We are using Claude Haiku to process relevant information to provide the service. We store health facts like smoking, drinking etc to maintain continuity across conversations, those facts can form part of the context provided to our AI services.
Would love to take your insights on what you think more on this. Cheers
@chinmay3199 Thanks for the quick response, Chinmay. I appreciate your openness about the WhatsApp messaging boundary, the model usage, and the authentication trade-off. This kind of transparency builds trust.
Personally, I think balancing privacy with accessibility is genuinely hard, and I think you've built something unique. Once the data flow and retention are clearly explained to users, I expect anyone trying the product to feel confident. Congratulations and good luck with the launch.