Readings are stored, not borrowed.
When a device sends a night of sleep or a resting heart rate, EVORA writes the value into your record and keeps it. It is not a window into the manufacturer's app, it is your copy, held by you.
Devices and wearables
Devices come and go. Your history stays.
A wearable is the most consistent health measurement most people will ever have, night after night, for years. That is exactly why it should not live inside one company’s app. Today you bring those years in yourself, as an export file, and EVORA writes them into your own record. Automatic sync is a separate claim, and its real state for every connector is published further down this page.
Device continuity
Change the band. Keep the history.
Readings live in your record, not in a manufacturer's app, and they are stored in one shape. Pick a situation to see what happens to the series when a device changes, stops or comes back.
Why it matters
Four years of sleep data should survive changing your ring.
Wearable data is only valuable over long spans. A month tells you almost nothing; four years tells you how you actually age. That is only possible if the history is device-independent.
Every device writes into the same shape.
Sleep duration is sleep duration whether it came from a ring, a strap or a watch. Values are normalized to one set of canonical measures before they are stored, so a five-year history reads as one continuous line instead of four separate app graphs.
Switching devices does not restart your history.
Move from a WHOOP to an Oura, or stop wearing anything for a year, and the earlier readings are still there. The record notes which device a value came from, so a change in hardware never looks like a change in your health.
Leaving a device does not mean leaving the data.
Cancel a wearable subscription and the manufacturer's history usually goes with it. Anything that reached EVORA before then remains in your record, and remains exportable.
Claim one · what you can do now
You can bring your own device history in today.
Oura and WHOOP both let a member export their own history, and Apple Health produces an export on the iPhone. EVORA reads those files, normalizes the readings to one shape and writes them into your record. This is present tense because it works now.
01
Export from the app you already use
Ask Oura, WHOOP or Apple Health for your own data. Each of them gives a member a file; none of them requires anything from EVORA to do it.
02
Import the file on Connections
Upload it and EVORA shows you what it found before anything is saved. Sleep, resting heart rate, variability, steps and active minutes are read where the file contains them.
03
The readings become part of your record
Values are stored under your record with the file they came from named as the source, and they stay after you stop using the device.
Naming Oura, WHOOP, Apple Health or Garmin here describes what you do with your own export. It is not an endorsement, an agreement or a connection with any of them.
Claim two · what the platform supports, and where it stands
Every connector, with its current state, read from the registry.
This list is generated from the same record the product itself reads. Automatic sync for Oura and WHOOP is applied for and waiting on the manufacturer. Nothing here is syncing today.
Device export file
Working today
Export a file from your device and EVORA reads it into your record.
No provider authorization needed
Hand-entered readings
Working today
Readings you enter yourself sit in the same timeline.
No provider authorization needed
Oura
Waiting on the manufacturer
Developer access applied for. Waiting on the manufacturer.
Authorization: oauth2
WHOOP
Waiting on the manufacturer
Developer access applied for. Waiting on the manufacturer.
Authorization: oauth2
Apple Health import
Working today
Export your Apple Health data on your iPhone and bring the file in: the ZIP, export.xml, a workout GPX or a CSV.
Enters by file export
Garmin
Planned
Planned. No application submitted yet.
Authorization: oauth2
Fitbit
Planned
Planned. No application submitted yet.
Authorization: oauth2
Continuous glucose monitor
Planned
Planned. Architecture is ready; no provider is connected.
Authorization: oauth2
“Working today” is used only where readings actually reach a record. “Waiting on the manufacturer” means EVORA has applied for developer access and has had no decision. “In build” and “Planned” mean no connection exists. No page on this site may state more than the row above says.
In the meantime
The record is worth starting before your device connects.
Device sync fills in the daily texture. Everything underneath it, labs, vitals, medications, documents, and the plain-language readings over them, already works today.
01
Start with what you have
Upload past lab PDFs, enter a blood pressure or weight reading, list your medications. The history begins the moment you add the first thing.
02
Enter readings by hand
Sleep, weight and vitals can be logged manually. Hand-entered values sit in the same timeline as device values and are labelled as yours.
03
Connect when approval lands
When a manufacturer grants access, connecting is one authorization and your earlier history stays exactly where it is.