Home Assistant will rename its Home Assistant Cloud service to Home Assistant Link in the December release, framing the change as a rebuke to large cloud vendors while promising the same service and faster remote access.
What the change actually is and what the project said
Home Assistant is using a December rebrand of its paid cloud offering as a public rebuke to large cloud vendors while keeping the service's features and promising faster remote access. Nabu Casa announced that Home Assistant Cloud will be rebranded from Home Assistant Cloud → Home Assistant Link, calling the move a response to what it described as Big Tech “ruining the cloud” and saying the new name should make it clearer the service “does things differently” Nabu Casa said this in the Home Assistant release notes. The release notes, published with the 2026.10 release and signed by the Home Assistant release lead, present the change as a renaming only (“Same service, new name”) and set the implementation window as the December release, giving users and administrators time to prepare the release notes say the change is planned for the December release.
The project contrasts its own approach with large proprietary cloud models. The release quotes the team saying it “has never locked anyone in, harvested their data, or turned working devices into e-waste,” and that Home Assistant Link is “all about being clearer that it does things differently” the release notes describe it that way. Alongside the rebrand message, the team said it has been improving remote access performance by migrating servers to bare metal, adding capacity worldwide and adding a latency checker that pings multiple servers on boot and picks the best connection the release notes describe those infrastructure changes.
What this means for users and integrations
The project's public messaging repeats that the rename is a rebrand of the existing service and not a technical migration the release notes put it that way. The notes link the rebrand to improved remote-access performance (the server migration and the new latency checker are being rolled out to make remote connections faster) but they don't list account changes, URL changes, API changes or new subscription terms tied to the rename the release notes do not announce any account, URL or API changes.
The release describes the change as a renaming of the existing service. The project frames it as a branding and messaging decision; the only concrete technical promises are faster remote access and the latency checker that chooses lower-latency servers on boot the release notes describe those server and latency improvements. Neither the release notes nor public coverage list any requirement for users to change integrations, add-ons or credentials because of the rename, so there are no published instructions to edit integrations or rotate tokens before December.
Users shouldn't expect breaking changes to integrations. The project frames the move as continuity with a new name plus improved remote-access infrastructure. It doesn't list token rotations, URL edits or new subscription terms as consequences the release notes describe the move as “Same service, new name” and list the server work.
How the wider community and industry reacted, and why it matters
Commentators tie the rename and the platform’s broader October release to a larger industry moment. Mila Cohen argues that Home Assistant’s October release, which also integrated the Model Context Protocol so AI agents can speak to a local Home Assistant instance, positions the project as a free, local-first alternative to subscription agent services and could put pricing pressure on paid offerings such as a US$20/month Home MCP subscription that some big vendors are pushing Mila Cohen writes that Home Assistant’s MCP move exposes over 2,000 integrations to agents and presents a free alternative to a US$20/month model. Forkast describes the MCP setup in Home Assistant as a one-click MCP server that generates copyable URLs for AI apps and says the endpoint handles authentication with existing access tokens or OAuth, making agent access local, fast and free for users with a server Forkast explains the MCP endpoint and authentication workflow.
That reading treats the rebrand as partly symbolic and partly strategic. The new name aligns product branding with a message about openness and user control while the project rolls out agent-native features vendors could try to monetise. Forkast argues this combination could reshape the pricing debate and influence how big vendors approach agent access and subscriptions Mila Cohen places the move in the context of subscription and agent competition.
Commentary also flags a practical issue for users. Exposing local smart-home controls to third-party AI agents increases the need for vigilance about privacy and access controls; users will need to manage what agents can see and do on their home instance Forkast warns that MCP exposure requires new vigilance on privacy and access. No quoted responses from major smart-home vendors or platform owners were included in the published coverage.
For an Irish Home Assistant user in Dublin, the rename is a branding and messaging change scheduled for December, paired with infrastructure work to improve remote access now the release notes describe the server and latency improvements. The 2026.10 integration of the Model Context Protocol means you can point AI agents at a local Home Assistant instance and give them access to integrations without a separate subscription. That capability raises fresh privacy and access-control choices you will need to manage for yourself the release notes describe the model server UI and URLs, and Forkast highlights the privacy checklist implication.
