documentation

Running your own instance.

sardinetracker is meant to live on your machine, which means the parts nobody else can do for you — getting to it from outside the house, and working out what broke when it stops answering — are documented here rather than assumed.

Remote access

Reaching your own instance from outside the house — a Cloudflare Tunnel or a Tailscale VPS, with the trade-offs of each spelled out.

read →

Troubleshooting

Symptom-first triage for a deployed instance. What to check, in what order, when the site won't load or a device stops syncing.

read →

Using sardinetracker

The in-app help, on the web: what each view is for, what the numbers mean, and how to log a day without it becoming a chore.

read →

Features

Everything the tracker does, one area at a time: daily logging, the flare model, interventions, the clinical record and the clinician portal.

read →

Importing your data

Bringing in history you already have: Apple Health exports, cycle data, a spreadsheet tracker, lab results, and backfilled UV.

read →