Your household's health records, together on your device.
Lab reports, medication routines, and records to take to your next appointment.
Offline records and OCR · English, Portuguese, and Spanish
See the app · How it works · Build or contribute · Privacy
Keep a separate profile for each person in your household. Bring in a lab report, check the extracted values, and follow confirmed results over time. When it's time for an appointment, prepare a PDF or CSV to share.
Vezuna is open source and in release preparation, with Android as the first-release priority and a native iOS app in development. There is no stable release or public store download yet. See the release guide for the remaining checks.
These are real screens from the Android development app. Select an image to view it at full size.
Unmodified Android emulator captures from 2026-10-31, with synthetic profiles and records. These development screenshots do not establish physical-device behavior, iOS behavior, or store readiness. Screenshot provenance.
- Keep household records separate. Switch profiles without mixing one person's reports with another's.
- Keep reports and everyday care together. Organize lab results, stored documents, and medication schedules with local reminders and dose history.
- Compare what you have checked. Trends use confirmed results and group compatible units together.
- Take a copy with you. Prepare PDF reports with tables and charts, export CSVs, or create a passphrase-protected backup. Records, backup, and export do not require AI or a store license.
- Import a report. Choose a PDF, select an image, or use the camera. Vezuna extracts embedded text or uses offline OCR.
- Check the details. Review the draft against the original report. Correct values, units, dates, and reference ranges before confirming them.
- Compare over time. Open the profile's confirmed results and trends. Results with incompatible units stay in separate series.
- Export for a visit. Prepare a PDF or CSV and choose where to send it through the system share sheet. Lab exports use confirmed results.
Vezuna organizes your records. It does not diagnose, recommend treatment, or change doses. OCR can make mistakes, so always check imported values against the original report.
Health records are encrypted locally and separated by profile. The app has no account system or Vezuna application server, and app-owned code has no analytics, ads, or health-data HTTP client. Android removes the app's Internet permission.
Platform and store services have their own terms. A PDF or CSV you export is plaintext, and copies you share leave the app's protection. Keep backup passphrases safe; Vezuna cannot recover them.
Read Privacy for Android Keystore and iOS Keychain storage, legacy-key migration and fallback, backup limits, and third-party behavior. The project makes no independent security-audit or clinical-validation claim. Report vulnerabilities through Security, without posting health records publicly.
Vezuna uses Kotlin Multiplatform and Compose, with native Android integrations and an Xcode iOS app. You can help with import edge cases, translations, accessibility, documentation, or platform testing.
- Read the contribution guide. Use fictional data in issues, fixtures, and screenshots, and keep private health records out of the repository.
- Follow development setup for SDKs and platform builds. For Android host-test Java requirements and local verification, use Local CI checks.
- Start with the architecture guide, or discuss a proposed change in a GitHub issue.
For a first source check, run these from the repository root with Python 3:
python3 tools/localization/check_localization.py
python3 tools/branding/check_brand.py
python3 tools/lab_importer/test_importer.pyThese checks cover catalogs, brand assets, and the synthetic importer. Native builds, Android host tests, device tests, and release gates are separate. See Development checks for suite-specific requirements, including the verified model fixture for inference tests.
Find your way around the native project
| Path | What's here |
|---|---|
shared/ |
Domain logic, Compose UI, localization, import review, trends, vault contracts, and exporters. |
composeApp/ |
Android app, encrypted storage, OCR, Health Connect, reminders, and native sharing. |
iosApp/ |
Xcode app, SwiftUI integration, encrypted storage, Vision/PDFKit, HealthKit, and native sharing. |
tools/ |
Importer, localization, branding, and release checks. |
fixtures/lab_importer/ |
Synthetic importer examples and regression fixtures. |
Local inference code is present, but first-release AI remains under validation. The shared model catalog is currently [], so the default app has no model available. No production model memory budget or native build identity has been approved. Store model delivery, licensing, and physical-device performance still need validation.
Signed release candidates and development tests do not establish store availability or physical-device readiness. Follow the release guide and store review drafts for signing, model delivery, permissions, and remaining platform checks. Read the tester-build identity transition before moving data from an older build.
- Architecture and data flow and local verification
- Release and EAS submission and changelog
- Website and public documentation brief
- Privacy and local storage and third-party notices
Vezuna source code is MIT licensed. The original Vezuna artwork is also MIT licensed, without trademark rights. The license does not permit presenting a fork as the official Vezuna app or implying endorsement.
Fonts, dependencies, SDKs, and model files retain their own licenses and terms; the full app payload is not all MIT. Read the third-party notices before distributing a build. Open-source licensing and any future paid store distribution are separate.



