Marketplace
Share what you build with everyone who runs Home Assistant. Publish custom integrations, dashboard cards, themes, template macros, and blueprints, and keep them up to date.
Not everything people build for Home Assistant belongs in Home Assistant itself. A card for one specific device, a theme in your favorite colors, an integration for a service only a few people use, an automation that solved a problem in your home: they are all worth sharing, and thousands of people do.
Sharing is a big part of what makes Home Assistant, Home Assistant. Someone builds a card for their own wall tablet and shares it. Someone else uses it in their home, finds a bug, and sends a fix. A third person sees it and gets an idea for something new. What you share inspires others and helps them along, and what they share does the same for you. That is the community: people who love Home Assistant, and love to share what they made with it.
The Marketplace is where users find and install that work. It is built into Home Assistant starting with 2026.11, under Settings > Marketplace. It grew out of HACS, the community store that people installed as a custom integration for years, and it uses the same catalog and the same hacs.json file. An integration, card, theme, or template that works with HACS today most likely works in the Marketplace too, though the Marketplace checks a few things more strictly before it installs. AppDaemon apps and Python scripts are the exception: the Marketplace does not handle them.
The Marketplace is also where a new integration or dashboard card starts. Publish it here, and once it has matured and has a user base, reach out to the maintainers to see whether it should ship built in. See does it belong in core.
| What | What it does | Shared through |
|---|---|---|
| Custom integration | Adds support for a device or service, like a built-in integration | The Marketplace |
| Dashboard card or plugin | Adds a card, a card feature, a badge, or another building block to dashboards | The Marketplace |
| Theme | Changes the colors and some sizes of the interface | The Marketplace |
| Template macros | Reusable Jinja macros that others import into their templates | The Marketplace |
| Blueprint | An automation, script, or template entity with blanks for others to fill in | An import link, and the Blueprint Exchange on the forum |
Blueprints are not in the Marketplace. Users import them from a link instead, and Home Assistant remembers that link to fetch updates. They are here because sharing them works the same way in spirit: you publish, others install, you keep it working.
This area is for you if you built something for your own Home Assistant and want others to use it too. What you need depends on what you share:
- A blueprint needs YAML and an automation that works in your own home. No programming.
- A theme needs YAML and an eye for color.
- A card or another dashboard plugin needs JavaScript.
- An integration needs Python.
Every type except blueprints lives in a public GitHub repository. You do not need to be a Git expert, but you need an account and to be able to publish a release.
Everything shared this way is made and supported by you, not by the Home Assistant project. Users see a warning that says so before they install anything from the Marketplace. Be ready to answer issues, and to update your work when Home Assistant changes.
- Your first contribution: turn an automation you already use into a blueprint, and share it.
- How it works: how the Marketplace finds, checks, installs, and updates what you publish, and how blueprints are shared and updated.
- Pick the guide for what you build, below.
- Custom integrations: what is different when your integration lives outside core.
- Dashboard cards and plugins: package a card, a card feature, or another JavaScript module.
- Themes: structure, the variables you can set, light and dark mode, and testing.
- Template macros: share Jinja macros as a template file.
- Blueprints: write, test, version, and share a blueprint.
- Releases and updates: how users get your new versions, and how to keep them working.
- Get into the catalog: add your repository to the catalog, so everyone finds it.
- hacs.json: every key of the file, and what the Marketplace does with it.
- Repository structure: where the files go, per type.
- Validation checks: what the HACS action checks, and what the Marketplace refuses to install.
- Core and integrations: how to build an integration, custom or not.
- Custom cards and more: how to build cards, card features, badges, views, strategies, and panels.
- Theming and design tokens: the CSS variables themes change, from the side of the frontend.
- Security: what to watch for in code that runs in other people's homes.
- The #developers channel on the Home Assistant Discord is where people who build integrations and cards help each other. Can't see the channel? Under Channels & Roles, choose I want to contribute dev skills to Home Assistant.
- Questions about the catalog,
hacs.json, or the HACS action: the HACS Discord server, and the issues of hacs/integration. - Blueprints are shared and discussed in the Blueprint Exchange on the community forum.
- Found a bug in the Marketplace itself? Open an issue in the core repository.