Features in Detail
Broken down by the three roles: wearer, keyholder and operation.
Wearer — record & review
The wearer documents every phase of chastity, manages their own devices and keeps statistics, goals and status in view.
Time Tracking & Live Status
Locking, unlocking, inspection and orgasm are captured as events with photo, note and assigned device. The live status shows whether currently locked and runs an ongoing timer for the wear time. This builds a complete chronicle of every lock-up.
Device Management
Each chastity device is created with a photo and purchase price. From the recorded wear time the application calculates the total duration per device and the cost per wear-hour. Multiple devices can be kept side by side and compared.
Cleaning Openings
Cleaning breaks are recorded as separate openings and subtracted from the running wear duration. A lock stays active while the break time is correctly excluded. The actual net wear time remains traceable at all times.
Multi-Category Tracking
Beyond the classic cage, categories such as plug, collar or cuffs can be tracked separately. Each category keeps its own entries, goals and calendar. This keeps parallel wear dynamics cleanly separated.
Personal Statistics
A calendar heatmap, a monthly overview and goal progress summarize the recorded data. Trends across longer periods become visible at a glance. The analysis spans all categories and devices.
Orgasm Tracking
Orgasms are recorded as separate events with time, type and an optional note. Combined with the keyholder's requirements, this builds a complete picture of permissions and instructions. The history is available at any time.
Code Vault
The photo of a sealed key safe or code note is stored locked and stays hidden. Only after release by the keyholder can the image be viewed. This stores an emergency key code without it being visible ahead of time.
Notifications
Push and email notifications report due inspections, deadlines and directives. This ensures the keyholder's requirements are not missed. Delivery also works through the native apps.
Passkey Login
Sign-in is possible via passkey without a password. Access uses device biometrics or a security key. This simplifies login and increases account security.
Apps & Offline-First
The application is available as an installable PWA and as a native app for iOS and Android. Recorded data is available offline-first and syncs once a connection is restored. Recording therefore works reliably on the go.
Keyholder — direct & control
The keyholder sets lock periods, requests inspections, defines goals and keeps the penalty log — manually or assisted by an AI keyholder.
Pure Keyholder Role: No Own Tracker
A keyholder does not have to track themselves. The "No own tracker" mode hides your own tracker area and sends the login straight to the keyholder overview. No data is deleted, and the switch can be reversed at any time. This keeps the role honestly separate: control without wearing a device yourself.
Inspection Requests
The keyholder requests an inspection with a five-digit code and deadline, which the wearer confirms by photo. The system additionally schedules automatic inspections randomly across the day, respecting a defined sleep window. This creates a mix of planned and unpredictable control.
Automatic Inspections
Automatic inspections are triggered randomly across the day without the keyholder having to initiate each one. A sleep window prevents inspections at night. The frequency stays unpredictable.
Photo Verification
Every inspection is verified by photo, including a check of the recorded device. Local image recognition can match the device in the photo against reference images. This makes it traceable that the correct device is being worn.
Lock Requirements & Lock Periods
Lock periods are set as fixed or open-ended, with a minimum wear time and a required device. The application monitors compliance and reports deviations. Lock requirements define bindingly what is worn and for how long.
Training Goals
Training goals are set per day, week or month and per category. Progress is measured automatically against the recorded wear time. This allows a gradual increase to be steered.
Orgasm Requirements
Requirements distinguish between an instruction as an obligation and an opportunity as a permission, each with a time window and type. The wearer confirms execution in the tracker. This keeps when and how an orgasm occurs regulated.
Penalty Log with Verdict Loop
The system automatically detects offenses such as missed inspections or wear times falling short. The keyholder then rules in a loop: dismiss or penalize. Every decision is recorded in the penalty log.
Keyholder Relationships
A keyholder can manage multiple wearers, each cleanly scoped to its own relationship. Data and directives stay separate per relationship. This allows several dynamics to be run in parallel.
AI Keyholder via MCP
An AI assistant reads the current state via the MCP protocol and issues directives within human-defined free-text rules. Lock periods, inspections and verdicts remain bound to the given rules. Every action by the AI is fully audited.
Operation — host & set up
The self-hoster runs the application on their own hardware, sets up users and roles, and decides on local AI and hardware extension.
Self-Hosting with Docker
The application runs as a Docker container on your own server with its own SQLite database. All data stays under your own control, with no dependency on a third-party service. Updates are applied through the published container image.
Local AI
Image recognition runs via Ollama and CLIP directly on your own server. Photos never leave your own infrastructure and are processed exclusively locally. This keeps verification entirely in your own hands.
Automatic Device Detection
Using CLIP, the local AI matches photos against stored reference images and detects the worn device automatically. This supports photo verification during inspections. Detection runs without external services.
Heimdall Hardware Key Safe
Heimdall is a physical key safe that enforces a lock period at the hardware level and only opens once the time has elapsed. The box is at MVP stage and experimental. It complements the software-side management with a physical component.
User Management & Roles
The technical user management — creating, editing and deleting users and assigning roles such as wearer, keyholder or admin — is kept separate from the keyholder overview. The keyholder area shows sub cards, status and directives, while user management stays purely the instance admin's account administration. Anyone who only controls and wears nothing themselves works as a pure keyholder, with no own tracker to maintain.
Multilingual & Configuration
The interface is available in German and English. The environment can be fully adapted to your own setup through configuration and environment variables. This keeps operation flexibly controllable.