| SmartKitten |
B2B platform product name (microservices + React frontend). |
| Organisation (org) |
Tenant; isolates users, devices, and billing. Joined via unique tagline. |
| Station |
Edge node at customer premises; polls sync commands and shuttles files to/from tablet. Often implemented on a mini-server (e.g. Raspberry Pi). |
| Device |
Registered tablet (e.g. reMarkable) with manufacturer, model, serial; may link to a station. |
| Device assignment |
Binding between a user and a device (is_current marks active assignment). |
| reMarkable |
E-ink tablet brand; source of .rm notes and screenshots. |
.rm file |
reMarkable stroke/note format; converted to SVG/PNG in Remarkable service. |
| Extract / insert / restore |
Command types for moving note data cloud ↔ tablet via station. |
| KittenSafe |
User file storage abstraction (paths, directories); legacy name retained in Document service. |
| MCP |
Model Context Protocol; Document service exposes tools for AI agents. |
| Entitlement |
Key/value capability granted by subscription (Billing). |
| Quota state |
Remaining limits (tokens, storage, etc.) for a subject. |
| Spending |
Token usage ledger and balance (separate from plan definition in Billing). |
| Playground |
Frontend area for AI chat and file exploration. |
| Board |
Collaborative canvas with sticky notes and realtime operations. |
| JWT |
JSON Web Token; carries user id, org id, role across services. |
| Namespaced API |
Routes like /api/v1/account/*, /api/v1/device/* (preferred over legacy /api/v1/*). |