Case Study: Building iZalud, a Patient-Owned Health Records Platform

iZalud set out to do something deceptively hard: give people real ownership of their medical history. Its promise — “Tu historia clínica, con vos” (your medical history, with you) — means sensitive health data has to be portable, private, and correct. That leaves no room for the shortcuts that work fine in a throwaway MVP and quietly turn into liabilities in a health product.

Fluxa Labs built the platform from scratch: architecture, backend, the admin panel, and the production setup.

What we built

The product has two surfaces:

• A patient-facing application where people access and own their clinical history.
• An admin panel, built with React + Vite, for managing patients, clinical records, and the documents attached to them — with role-based access for the team operating the platform.

The architecture — and why

For a small team building a health product, the right call was a lean, security-first stack with as little undifferentiated infrastructure to babysit as possible.

• Supabase as the backbone — managed Postgres, authentication, file storage, and, critically, row-level security (RLS). RLS lets data isolation be enforced inside the database itself: a patient can only ever read their own records, regardless of what the application layer does. For health data, moving access control down to the data layer is the difference between “we hope the API is correct” and “the database guarantees it.”
• Vercel for hosting and deployment — preview deploys on every change, a global edge network, and zero servers to maintain. The focus stays on the product, not on ops.
• React + Vite for the admin panel — a fast build and a tight developer loop for the internal tooling that day-to-day operations depend on.

The discipline that matters here isn’t the logos in the stack — it’s the decisions behind them: modeling the data so privacy is structural rather than bolted on, keeping the number of moving parts small, and leaning on managed services so a small team ships features instead of maintaining plumbing.

The result

iZalud launched as a privacy-first platform where patients genuinely own their records — on a foundation a small team can operate and extend with confidence, rather than one that needs a rescue sprint twelve months later.

Hear it from iZalud’s CEO, Natalia Blanco:

The takeaway

You don’t need a large team to build a serious product. You need the right architecture, decided early, by someone who has carried systems into production before — so the decisions that are expensive to reverse get made correctly the first time.

That is the entire idea behind Fluxa Labs. If you’re building something where the technical bar matters, let’s talk.