Home

MowDeck

MowDeck is a self-hosted control centre for robotic mowers: live status and map, starting a job with your own settings, spot mowing that MowDeck steers itself, weather-aware schedules, the cameras, notifications and an optional AI assistant, for one household or several accounts, with the data kept at home. It is made of small, separately scalable services and runs on a mini PC at home (Docker Compose) as well as on Kubernetes with the same images. It is not tied to one manufacturer: the services use the mowdeck-control interface, and each manufacturer is an adapter package behind it. The first adapter is for Mammotion (LUBA, YUKA), built on PyMammotion; a simulator implements the same interface.

Status: Phases 1 to 4 are done (foundation, web app, scheduler and integrations, fleet and entitlements); the camera, spot-mowing and AI features of Phases 5 and 6 are in use. See Phases and gates.

Where to go next

• Phases and gates: roadmap and the Phase 1 acceptance criterion
• Architecture (arc42): goals, context, building blocks, runtime, deployment
• Generated architecture diagrams: services, routes, NATS subjects, API surface and data ownership, derived from the code and never stale
• Architecture decisions: ADRs
• Getting started and the service template
• Web app: developer guide of the PWA and the design system
• Operating the Compose stack
• Spikes: research documents
• Original project plan (German), the authoritative source this documentation condenses

---

Mirrored from docs/index.md at commit b52cccfea2503c98301131b99958abd10233e00a. Edit the file in the repository, not this wiki page.