My Health Vault is our own product, a SaaS where people keep their medical records, test results and health data in one place and share them with providers on their own terms. Built on React and Node.js, it runs on our own infrastructure with Stripe subscriptions, and serves Latin America first with Australia as the second market.
- Client
- MyHealthVault
- Year
- 2025
- Timeline
- Ongoing
- Industry
- Health Tech
- Web
- Visit site ↗

Impact
- 0+Active UsersRegistered health vault users
- AUData SovereigntyAustralian-hosted, Australian data residency
- 0.0%UptimePlatform availability SLA
- LiveSubscription ModelStripe-powered recurring billing
Figures reported during the project; independent verification pending.
The challenge
Patients collect results from GPs, specialists, laboratories and hospital systems, and nothing joins them up. That is true in Colombia and in Australia. We wanted a consumer product that people would trust with the most sensitive data they own. It is our product, so the constraints are ours to set and to live with.
Security and privacy could not be traded away for ease of use, and ease of use could not be traded away either, because the audience is consumers rather than clinicians. In Colombia the product has to meet Law 1581 on personal data protection. And many users would be managing their own health records for the first time, often on a phone in a waiting room.
What we built
We built the product as a SaaS on React and Node.js with PostgreSQL, and it now runs on our own infrastructure. Users upload documents and file them by category: pathology, imaging, prescriptions, referrals, hospital summaries.
Sharing with a provider works through a time-limited link with controlled permissions. The provider does not need an account. Stripe handles the subscription billing and OAuth 2.0 handles sign-in, so we store no passwords. The interface was designed for people who are not technical and have never organised their own records before.
Key features
- Secure document upload and organisation by category
- Time-limited, permission-controlled provider sharing
- Australian data residency (AWS Sydney)
- Stripe subscription billing
- OAuth 2.0 authentication
- Mobile-responsive — built for use in waiting rooms
Results
The product is live at myhealthvault.io with expiring share links for providers and Stripe subscriptions, running on our own infrastructure. Colombia is the first market and Australia the second. Usage figures are not published.
Stack
- React
- Node.js
- PostgreSQL
- Docker
- Stripe
- OAuth 2.0
Gallery
The operator note
In health data, trust is the product. We own this one, so every security decision that costs convenience is ours to defend to the user: share links expire instead of giving persistent access, there are no third-party login integrations, and the data stays on infrastructure we run.
We have operated in Australia through CoffeeLink and we know that market walks away from a product it does not trust, whatever the feature list says. Colombia under Law 1581 is no more forgiving. The trade-off is real. An expiring link means a provider sometimes has to ask for a new one, and we accept that over an open door.