Your health data, yours to use
Sync, export, and control your Apple Health data. Bring it into the files, databases, and AI tools you choose.
Why it exists
Your health data should be useful beyond your phone. PulsHealth makes it easier to build a personal archive, create your own dashboards, and explore your history with AI, while choosing what you store and where it goes.
Who makes it
One person. I build and maintain the app, the database stack and this site, and I run it on my own data every day.
Open by default
The app, the database stack, the sync protocol and the knowledge base are Apache-2.0. The hosted PulsHealth database runs the same code, so you can always run it yourself.
How it compares
Other ways to get Apple Health data out of the iPhone.
| Open-source app | Open-source backend | License | Where data lives | Wire format specified | AI assistant access | Price | |
|---|---|---|---|---|---|---|---|
| PulsHealth | Apache-2.0 | Hosted for you, or your Postgres | Free app | ||||
| Health Auto Export | Community receivers | Closed | Your endpoint, Drive, MQTT… | Community-documented | Subscription | ||
| HealthSave | Source-available | Elastic 2.0 | Your TimescaleDB | One-time | |||
| FreeReps | MIT | Your server (Tailscale) | Free | ||||
| Apple's export | — | A zip of XML | Free |
Checked in September 2026 against each project's public site. If something here is out of date, open an issue.
How to help
Try it and report what breaks, fix a knowledge-base page that is wrong, or star the repository to follow along.