Vacuula revives cloud-abandoned Neato vacuums with a self-hosted server
After Neato wound down its cloud services, an independent developer launched Vacuula, an open-source server that restores maps, schedules, and app control to D3–D10 robots via Docker Compose or a Home Assistant addon. If you own a Gen3 or Gen4 Neato, it is now the only way to keep it working.
November 2026. Vacuula, an open-source server that replaces Neato’s cloud, is featured in the Self-Host Weekly of 13 November. The project, under an AGPL-3.0 license, already counts 256 stars and 220 commits on GitHub. It covers Gen3 (D3 through D7) and Gen4 (D800, D8, D9, D10) robots. Why it matters: after the vendor shut down its cloud, this is the only way to give mapping and scheduling back to vacuums that still work perfectly but have been silenced.
An orphaned robot: what the cloud shutdown actually breaks
Neato Robotics announced the phase-out of its cloud services in late 2025, leaving owners of connected robots without the infrastructure that makes them run. On these vacuums, a large part of the intelligence does not live in the robot at all: it lives server-side. Maps, no-go zones, schedules, and the mobile app all flow through the vendor’s cloud.
The result is brutal. A BotVac or a D7 whose hardware is in perfect shape gets reduced to a physical button: it vacuums, but it no longer knows where it already cleaned, when to start, or how to avoid a rug. For a community that paid several hundred euros for these devices, this is a textbook case of software-driven obsolescence — exactly the scenario self-hosting knows how to counter.
Vacuula answers by the classic self-hosting method: rebuild the missing server, and point the robot at it instead of the dead cloud. The name — a contraction of vacuum and Dracula — owns the tone: reviving “undead” machines.
What Vacuula reimplements
The project presents itself as an all-in-one solution to “repair and control” a Neato broken by the cloud’s disappearance. Model coverage is already broad: Gen3 (D3, D4, D5, D6, D7) and Gen4 (D800, D8, D9, D10) are supported. Two categories remain out of scope for now: the Gen1 units without Wi-Fi, and the Gen2 BotVac Connected, listed as “coming soon.”
The server restores the essential functions that used to live in the cloud. Setup and status, maps, run history, scheduling, settings, and zones / no-go lines are checked as working. Multi-zone is operational on Gen4, and in progress for the other generations. The still-under-construction pieces — notifications, the Home Assistant entity, drag-to-clean “here” — show a project that is alive and iterating fast.
The architecture is simple and readable in the ports. The server exposes a web app on port 8050, and listens to robots on two separate channels: 335 for Gen3 and 3443 for Gen4. That decoupling is what lets a single container drive several generations at once.
Deployment: Docker Compose, Home Assistant, or LXC
Setup follows self-hosting conventions, with three documented paths. The most direct is Docker Compose: download the docker-compose.yaml from the releases, then:
wget https://github.com/vacuula/vacuula/releases/latest/download/docker-compose.yaml
docker compose up -d The server is configured through environment variables: the GEN3_PORT, GEN4_PORT, and VACUULA_PORT ports, per-generation toggles (GEN3_ENABLED, GEN4_ENABLED), mDNS for auto-discovery, and the TZ timezone so schedules fire on time. The team says it has tested ARM 64-bit and x86 64-bit, with the ambition to cover ARM 32-bit so the server can run on older SBCs.
For Home Assistant users, a dedicated addon installs through the official repository — the integration badge opens the Supervisor directly. Finally, an LXC / standalone path exists for those who would rather skip Docker. Once the server is up, a graphical installer for Windows, Linux, and macOS configures the robot to point at your server instead of the cloud.
A repeating pattern: when the cloud dies, self-hosting takes over
Vacuula is not an isolated case: it joins a lineage of projects born from the same realization. When Insteon cut its servers in 2022, the community exhumed firmware and homebrew servers to relight millions of hubs; when Logitech pulled the plug on Harmony, local servers took over; MyQ gateways and some SpotCam cameras followed the same trajectory. The common thread is always the same: the object’s intelligence lives server-side, and when the server dies, the object becomes a paperweight — unless someone rebuilds the server.
What sets Vacuula apart in this family is its functional scope. It is not a mere connectivity bridge but a full reimplementation of the backend: maps, zones, schedules, history. The Neato community also benefits from robust hardware that is still widespread, which guarantees a user base large enough to sustain the project. That is the self-hosting virtuous circle: the longer the hardware survives, the longer the open server lives.
A word on security, because it matters. Handing your vacuum to a local server means moving the trust boundary into your network. Because the project is AGPL-3.0 and distributed via Docker or Home Assistant, the code stays auditable and updates follow the usual channels. But like any self-hosted service, treat it accordingly: put the web app behind an HTTPS reverse proxy, restrict access to the robot ports (335, 3443) to your local VLAN, and keep an eye on the releases — the project iterates fast and fixes continuously.
The constraint to understand: the server must stay on
The least glamorous point is also the most important to grasp before starting. Because Vacuula replaces a cloud service, it inherits its core constraint: the server must be available at all times for schedules, the app, and maps to work. A Raspberry Pi or a small always-on home server is the prerequisite, which the FAQ embraces by detailing recommended hardware.
That requirement is not a flaw in the project — it is the nature of self-hosting. Where Neato’s cloud promised zero maintenance in exchange for your data, Vacuula inverts the bargain: you get control and longevity back, in exchange for a machine to run. For a crowd already hosting Home Assistant, Frigate, or Pi-hole, the marginal cost is near zero.
The AGPL-3.0 license also deserves a read: any modified version served over a network must publish its source. That is a choice consistent with the project’s spirit — preventing a “cloud” successor from closing off what Vacuula just opened.
For Home Assistant households, the payoff is immediate: the addon drops the vacuum into the same control plane as every other device, and the promised entity will let a single automation switch the vacuum between its maps and zones — something the original cloud app never exposed to third-party control. Even before that lands, the web app already covers the day-to-day loop of schedules, maps, and history that most owners actually use.
The verdict
If you own a Gen3 or Gen4 Neato (D3 through D10) left mute by the cloud shutdown, deploy Vacuula now via Docker Compose or the Home Assistant addon: it is the only documented route back to maps, schedules, and app control. The cost boils down to a small always-on server, which most self-hosters already run.
But if your robot is a BotVac Connected (Gen2) or a Wi-Fi-less Gen1, wait: support is not there yet. And keep the structural constraint in mind — no server running, no scheduling. Those unwilling to maintain a dedicated box have no credible alternative: Valetudo does not cover this lineup, and Neato’s cloud is not coming back.