# Install ignite with Homebrew
Build, launch, and maintain any crypto application with Ignite CLI. Version 29.10.1 via Homebrew; verified 2026-07-26.
## Install
```sh
sudo av install brew:ignite
```
Additional install commands:
### macOS
- Homebrew (100%):
```sh
brew install ignite
```
Evidence: local Homebrew formula metadata
## Package facts
- **Package key:** brew:ignite
- **Package manager:** Homebrew
- **Version:** 29.10.1
- **Source summary:** Build, launch, and maintain any crypto application with Ignite CLI
- **Homepage:**
- **Repository:**
- **Last updated:** 2026-07-26T04:07:47+02:00
- **Generated:** 2026-08-03T19:37:03+00:00
## Executables
- ignite (alias)
## Install behavior
- Bottle: not available
## Freshness
- Page generated: 2026-08-03
- Package-manager version: 29.10.1
## Project history and usage
Ignite CLI is a Go command-line tool for scaffolding, running, and maintaining Cosmos SDK application blockchains. It packages a large amount of Cosmos boilerplate into commands such as `ignite scaffold chain` and `ignite chain serve`.
### Project history
The repository was created in 2020 and built its early identity around fast application-chain scaffolding for the Cosmos ecosystem. The project later moved through a Starport-to-Ignite rebrand; an official issue from April 2022 tracks replacing Starport naming with Ignite and Ignite CLI across docs and commands.
The README frames Ignite CLI as a developer-friendly interface to Cosmos SDK and records a compatibility table that ties Ignite versions to Cosmos SDK and IBC versions. That table is part of the tool's history: as Cosmos SDK evolved, Ignite became not just a generator but also a version-aligned workflow tool for chain developers.
### Adoption history
Ignite's adoption is tied to Cosmos SDK education and bootstrapping. The official tutorials present Ignite as the starting point for a first Cosmos blockchain, while the README documents Homebrew, Snap, manual installation, GitHub Discussions, and a bounty/contribution process around the CLI.
### How it is used
The canonical workflow is to install the binary, run `ignite scaffold chain `, enter the generated project, and run `ignite chain serve`. Follow-on scaffold commands create modules, messages, queries, and app structure while preserving placeholder markers so generated code can continue to be extended.
### Why package nerds care
Ignite is significant because it exposes blockchain-framework churn directly as package metadata and generated code. For package maintainers, the CLI's value depends on matching Go, Cosmos SDK, IBC, and generated project layouts, which is why the version compatibility table matters as much as the executable itself.
### Timeline
- 2020: Public GitHub releases began under the Starport-era project lineage.
- 2022: The project tracked a Starport-to-Ignite rebrand across source and docs.
- 2022: Ignite CLI v0.23.0 aligned with Cosmos SDK v0.45.5 and IBC v3.0.1.
- 2024: Version 28 introduced support for Cosmos SDK v0.50 and v0.53 lines.
- 2025: Version 29 continued the v0.50/v0.53 compatibility line and IBC v10.2.0 support.
### Related projects
- Ignite is closely related to Cosmos SDK, IBC, Tendermint/CometBFT-era chain development, the Ignite Apps marketplace, and the generated web/front-end templates referenced by the project docs.
### Sources
-
-
-
-
-
## Security Notes
narrow executable package without higher-risk signals.
- **Geiger risk:** green / low
- narrow executable package without higher-risk signals
## Combined YAML source
View the package source record on GitHub. [combined/ignite.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ignite.yml)
## Sources
- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph