The open-source AI brain for diabetes.
Lumose plugs into your CGM, your pump, Nightscout and the apps you already run, then turns that data into answers and daily briefs. On your server, with the AI you choose.
Because no one should manage diabetes alone.
Plugs into what you already run.
Sign in to a device cloud, pair over Bluetooth, or point Lumose at your Nightscout. Lumose is the AI layer on top of the platforms you trust.
- Cloud
Dexcom - Bluetooth + cloud
Tandem - Bluetooth + cloud
Medtronic - Cloud
Glooko - Bridge
Nightscout - Via Nightscout
FreeStyle Libre - Via Nightscout
Eversense - Via Nightscout
Loop - Via Nightscout
Trio - Via Nightscout
AndroidAPS - Via Nightscout
xDrip+
Product names and logos belong to their owners. Lumose is not affiliated with or endorsed by them. See device status →
Any model.You choose where your data goes.
Point Lumose at Claude, OpenAI, GitHub Copilot, or a local model through Ollama. Lumose doesn't host or resell AI. When you use an AI feature, your question and health data go to the provider you picked, under its terms. With a local model, they stay on your network.
- Use an AI subscription you already have, or your own API key
- Run fully local with Ollama
- Or any OpenAI-compatible endpoint
Why did I go high after breakfast?
What I see in your data: you rose about 75 mg/dL within an hour of eating.
- You were in range before breakfast, so the rise started after you ate.
Worth mentioning to your endo/CDE: how often this happens after breakfast.
Not medical advice. Consult your healthcare provider.
How much of the last 6 hours was I in range?
What I see in your data: 78% of your readings were in range (70-180 mg/dL).
- The rest were above 180, with a peak of 245 after lunch.
- None were below 70.
Worth mentioning to your endo/CDE: the time you spent above range after lunch.
Not medical advice. Consult your healthcare provider.
Did I come back down after lunch?
What I see in your data: you're at 210 mg/dL and trending down, after a peak of 245.
- That's 35 mg/dL below the peak, and still above 180, the top of your range.
Worth mentioning to your endo/CDE: how long you stay high after lunch.
Not medical advice. Consult your healthcare provider.
Give me a quick summary of my morning.
What I see in your data: over the last 6 hours you ranged from 98 to 185 mg/dL, with 94% of readings in range.
- Your highest reading came after breakfast.
- You're at 118 mg/dL and steady now.
Worth mentioning to your endo/CDE: the rise after breakfast.
Not medical advice. Consult your healthcare provider.
Not medical advice. Consult your healthcare provider.
Illustrative example. Answering with: Claude · Your Claude subscription
Claude, OpenAI, GitHub Copilot, Ollama and other product names and logos belong to their owners. Lumose is not affiliated with or endorsed by them.
No AI decides your alerts.
In development
Alerting is in active development and works only for some setups. Keep your CGM's own alerts on.
- Alerts are generated by fixed rules you can read in the code.
- No language model decides, words, or sends an alert.
- Alert logic makes no AI calls, so it doesn't depend on an AI provider.
- Lumose never sends a command to your pump.
- Urgent low: 52 mg/dL. Matched by a fixed rule.
- In-app alert.
- Caregiver escalation. In development
Your phone, your wrist, the web
AI chat, the Wear OS watch face and daily briefs, running together, plus a preview of caregiver alerts.
Demo content for illustration. Names and data are made up. Lumose is a monitoring and analysis tool, not medical advice. Always talk to your care team before changing how you manage diabetes.
Meets you where your data already is
Every connection is read-only. If we haven't tested something on real hardware, we say so.
Bluetooth · Android app
Direct connect
Pair your pump with the phone app. Readings stream straight to your server, no vendor cloud in between.
- Tandem t:slim X2: Supported
- Tandem Mobi: Untested
- Medtronic 780G: Beta
- Medtronic 680G / 770G: Untested
Cloud sync
Vendor clouds
Already uploading? Lumose pulls from the cloud you use today, on a schedule.
- Dexcom G7: Supported
- Dexcom G6: Beta
- Dexcom ONE+: Untested
- Tandem cloud: Supported
- Medtronic CareLink (US): Beta
- Medtronic CareLink (EU): Not working
- Glooko: smart pens: Supported
- Glooko: Omnipod 5: Untested
Bridge
Nightscout
Running Loop, AAPS, Trio or xDrip+? Point Lumose at your Nightscout site.
- Nightscout: Supported
- Libre / Eversense via Nightscout: Supported
- Loop, AAPS, Trio uploads: Supported
Beta: built, not fully checked against real hardware. Untested: no real-hardware testing yet. Not working: tracked on GitHub.
From device to dashboard, in real time
AI analysis and clinical knowledge retrieval are built into the platform core, which runs on your server.
Cloud sources like Dexcom, CareLink, Glooko and Nightscout connect to your server directly.
Up and running in minutes
Laptop, home server or a VPS. Then install the Android app if your pump connects over Bluetooth.
Docker
git clone https://github.com/lumose-health/lumose.gitcd lumose && cp .env.example .envdocker compose up -dThe defaults are for one computer. For an always-on server, set the secrets in .env first, as the setup guide shows.
Kubernetes
git clone https://github.com/lumose-health/lumose.gitcd lumose# First fill in k8s/base/secret.yaml and your domainkubectl apply -k k8s/overlays/prodThe Kubernetes guide covers secrets, your domain and HTTPS.
Built in the open.
Code, device drivers, design and testing from people across the diabetes community.
- Contributors
- 13
- GitHub stars
- 143
- Forks
- 14
- Latest release
- v0.16.0
Docs, community and support
Supported by
Run it yourself tonight
Free, open source and yours. Bring your devices and an AI provider you already use.