Capability
One installation, one facility, one operator
Administration, notification, reporting, and licensing serve a single facility. There is no shared control plane above you and no other tenant beside you.
Analytics that stay proportionate
- Privacy-limited capture
- Product events are captured within defined limits rather than collected because they might be useful later.
- Durable daily projections
- Course and institution reporting is built from durable daily projections, so a figure can be recomputed and explained.
- Retention and export
- Retention is a defined boundary, and the data is exportable. Reporting you cannot take with you is not reporting you own.
Notifications
In-app notification carries read state, protected attachments, and optional email delivery. Administrators get delivery metrics, and automated events are part of the same contract as the ones a person triggers.
Licensing without a phone home
The licence boundary is offline by design.
- One licence is issued to one stable installation identity, held for the life of that installation.
- The identity is not regenerated by an upgrade or by disaster recovery.
- Verification uses a key embedded in the application, so no network call decides whether your facility can teach today.
- Administrators can see licence status from inside the product.
Do it, step by step.
The manual covers this as a task, with prerequisites, what finishing looks like, and what to do when it does not work.
Bring Mirket to your facility.
Run it on your own infrastructure or let us host it for you. Both licences ship the same product; the difference is who operates the data plane.