LinuxMice is Katteke’s direction for a Debian-based sovereign workplace platform: a practical, more accountable alternative to the Microsoft 365 operating model for EU and Dutch organizations first.
Current status: LinuxMice is an early private implementation and local-dogfood project. Narrow CLI, component-catalog, control-plane, packaging, and identity foundations now exist, but LinuxMice is not yet a publicly released product, managed service, certified platform, or production-ready identity provider.
The public marketing overview remains at katteke.com/linuxmice. This page is the canonical public documentation entry for product reasoning and status.
Product direction
- A Debian-based distribution and ecosystem, not merely a list of third-party applications.
- Independently useful modules that can also form a coherent workplace suite.
- Stable CLI and API primitives before graphical administration.
- Rust-first Katteke components where Rust is a good engineering fit.
- Open standards, exportable data, replaceable infrastructure, and auditable behavior.
- EU and Dutch sovereignty, privacy, accessibility, and operational accountability as default priorities.
- Administrative workflows suitable for people, scripts, and accountable automation.
Interface direction
The intended human command shape is:
lmice <service> <command>Normal workflows should use short, discoverable commands and safe defaults. Structured output and explicit automation controls may remain available for advanced use. The endpoint daemon name is lmd; the planned organization/control-plane service is lmhubd.
These names describe current product direction. Interfaces remain pre-release until a versioned public contract and compatibility policy are published.
Modularity boundary
A customer should be able to use one sellable module without operating the full suite. Optional integrations should improve the combined experience while preserving standalone operation. A bundle may install several modules, but should not silently merge their data or make a central catalog a hidden dependency.
Identity direction
LinuxMice intends to provide an in-house identity capability rather than adopt Kanidm or Rauthy as the product core. Identity work must use reviewed dependencies and established cryptographic implementations; “in-house” does not mean inventing cryptography.
No enterprise identity or protocol-conformance claim is made until implementation, recovery exercises, conformance testing, dependency review, penetration testing, and independent security review provide evidence.
Deployment direction
The first server profile should be operable on a single Ubuntu or Debian host, including a modest VPS, with documented TLS, backup, upgrade, rollback, recovery, and removal. The managed-node direction starts with Debian and Ubuntu. Browser access may serve other operating systems before native endpoint agents exist.
Public documentation still required
Before release, this entry must grow verified installation, configuration, architecture, CLI/API reference, security model, backup and recovery, lifecycle, compatibility, and support documentation. Until those pages exist and are tested, they are missing deliverables—not implied features.