hypfer/valetudo

Cloud replacement for vacuum robots enabling local-only operation

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 6th, 2026
Created on July 12th, 2018
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 508
Total Stargazers: 9,622 (+0)
Total Subscribers: 114 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.6 hours
Mean response time: 17.3 days
90th percentile: 62.9 days
Tracked items: 17

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (4)
  • Task (2)
  • duplicate (2)
  • enhancement (2)
  • support request (2)
  • help wanted (1)
  • invalid (1)
  • wontfix (1)

Most active issues this week

Detailed Description

Valetudo is a cloud replacement for vacuum robots that enables local-only operation without replacing the vendor firmware.

The tool solves the problem of cloud dependency and data privacy concerns with robot vacuums by intercepting communication between the robot and vendor cloud services, acting as what users describe as a "brain parasite" for the vendor firmware. This approach allows the tool to leverage the extensive research and development embedded in manufacturer firmware while eliminating cloud requirements, account dependencies, and associated enshittification tactics like ads, upselling, and sudden subscriptions. It provides a responsive web interface for robot control across phones, tablets, and desktops, along with a REST API with integrated Swagger documentation and MQTT integration for home automation systems.

Valetudo suits users who prioritize data privacy and local control over feature parity with vendor applications. It works with a range of supported robot models from manufacturers including Roborock, Dreame, and Xiaomi. The tool deliberately avoids reimplementing every vendor app feature, instead focusing on essential modern functionality while avoiding inherited technical debt. For users seeking a less opinionated alternative that also achieves cloud-free operation with Home Assistant integration, the README names Roborock Local Server as an option.

The project operates as a hobby maintained by an individual with explicit intent not to commercialize, grow, or expand its audience. Development is published under the Apache-2.0 license with source availability, though governance follows a "freeware with source available" model rather than community-driven FOSS conventions. The maintainer has established clear boundaries around the project's scope and direction, prioritizing sustainability over expansion.