Overview
PatientPath license and update status
Total Keys
—
Active
—
Activated
—
Expired
—
Revoked
—
PP Basic Active
—
PP Pro Active
—
LeafLedger Active
—
Current Builds
| Product | Windows | macOS |
|---|---|---|
| PatientPath | — | — |
| LeafLedger | — | — |
License Keys
Generate and manage activation keys
Generate New Key
New License Key
All Keys
| Key | Customer / Note | Product | Status | Machine | Expires | Days Left | Actions |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Industry Insights
Anonymised product trends from your user base
Trending Products
| Product | Category | Trend | Installs Reporting | Week |
|---|---|---|---|---|
| Click Refresh to load trending data. | ||||
Privacy Notes
• Installation hashes are one-way (HMAC-SHA256[:16]) — individual users cannot be identified.
• Product names only — no patient data, no quantities, no pricing is ever stored.
• Products seen by fewer than 2 installs are suppressed (k-anonymity floor).
• Data is automatically purged after 90 days.
Updates
Push new builds to Windows and macOS users
🔑 Patch Signing Public Key
Copy this into PATCH_PUBLIC_KEY_PEM in main.py before building.
Click "Load" to show the public key.
Upload New Build
Builds are pushed from the desktop app's Releases tool (LeafLedger Pro / PatientPath Pro admin builds). The desktop client uploads installer + blockmap direct to R2 via pre-signed URLs, then calls
This server-side dashboard is read-only for builds — see Build History below.
/api/admin/builds/finalize to write latest.yml.
This server-side dashboard is read-only for builds — see Build History below.
Build History
| Platform | Version | Patch File | Uploaded | Status |
|---|---|---|---|---|
| Loading… | ||||
Crash Reports
Automatically submitted by client apps
All Reports
| Time | Product | Version | Platform | Error | Key | Status | Actions |
|---|---|---|---|---|---|---|---|
| Click Refresh to load crash reports. | |||||||