HACS, the community store most people use to install custom integrations and dashboard cards, stops being a separate download. From Home Assistant 2026.11, due in November, it ships with Home Assistant as a built-in integration called the Marketplace, found under Settings > Marketplace. Franck Nijhof's core pull request was merged on 1 October 2026. The HACS side followed this week: on 16 October maintainer Joakim Sørensen (ludeeus) opened an issue announcing the move, and on 17 October the HACS documentation gained a page explaining it, with a banner on every page. The same day the HACS download script started refusing to install on 2026.11 or newer.

What the upgrade does

There is nothing to do by hand. On the first start after the update, the Marketplace takes over the HACS configuration entry:

  • everything installed with HACS stays installed and keeps getting updates, except custom repositories without a hacs.json file, which stay but can no longer be updated;
  • custom repositories and update entities carry over with their names, areas and labels, and the update entities keep their entity IDs, so automations and dashboards built on them keep working;
  • the HACS integration and its files are removed, and bookmarks to /hacs open the Marketplace.

From 2026.11 on, Home Assistant blocks the HACS custom integration, so it cannot be put back.

What works differently

The Marketplace lives under Settings rather than in the sidebar, and the HACS options for the sidebar title and icon are gone. AppDaemon apps and Python scripts are no longer managed. Their files stay and keep running, but they get no updates, and a repair lists the affected ones. Dashboard resources are now served from /local/community/. The old /hacsfiles/ paths still work, and anyone who defines resources in YAML gets a repair asking them to switch.

People who scripted around HACS have a little more to change. integration_entities('hacs') returns nothing and has to become integration_entities('marketplace'). The restart hint HACS kept in the release_summary attribute becomes a repair. Tools that call hacs/ WebSocket commands get an unknown-command error and need the new marketplace/ commands, which use a different format. Custom integrations that read the hacs.* files in .storage or hass.data["hacs"] lose that data.

What stays the same

The catalog is still the hacs/default repository, and the Marketplace reads the same data and the same hacs.json files. Authors submit repositories exactly as before. Browsing, installing and updating catalog content needs no GitHub account, and the Marketplace checks the catalog for new versions every 6 hours. Adding a custom repository does need a GitHub connection, made through GitHub's device sign-in; it asks for no access to private repositories, and with it custom repositories are checked every 48 hours.

The first time an administrator opens the Marketplace (nobody else can), it shows a warning that community content is not tested, audited or supported by the Home Assistant project. Nothing installs or updates until someone accepts it. If the catalog marks a repository as critical, the Marketplace uninstalls it and restarts Home Assistant. The core pull request is also frank about the limits: files come from GitHub over HTTPS, with no signatures or checksums on what gets installed.

Work on HACS itself has stopped in the hacs/integration repository. Feature requests now go to the Marketplace category of the Home Assistant discussions and bugs to the core repository. Until 2026.11 is out, HACS on 2026.10 and older keeps working as it does today.