Licensing models decide who wins and who disappears.

Zsh is free. But free does not mean ungoverned. Its licensing model is one of the reasons it has survived decades, powered countless developer workflows, and avoided the traps that break other open-source projects. Understanding that model means understanding the long-term stability of the tools you rely on.

Zsh is distributed under the MIT-like Zsh license, a permissive open-source license. It lets anyone use, copy, modify, and distribute code, with minimal restrictions. No copyleft. No requirement to open source your own modifications. This freedom fuels rapid adoption and wide support across operating systems. You can embed Zsh in commercial software. You can ship it in internal tools. You can fork it and make it your shell with tiny changes.

The license also ensures that the code stays accessible, that there’s no barrier to entry, and that maintainers can focus on features instead of legal disputes. This is why Zsh appears everywhere—from macOS defaults to containerized dev environments—without friction.

For teams choosing a shell, the licensing model is not background noise. It’s part of the product’s value. A stable, permissive license like Zsh’s keeps legal overhead low, speeds internal decision-making, and minimizes long-term risk. There are no surprises hidden in contributors’ agreements, and no shifting license terms to navigate after adoption.

The Zsh model is proof that open source and commercial needs can align when the license is permissive, predictable, and minimal. That’s why it has cemented its position alongside Bash as a default developer tool.

If you want to see a permissive licensing model in action—running live in minutes with a modern developer platform—check out hoop.dev. You can go from zero to working environment faster than reading this paragraph, and you’ll see how a great licensing foundation powers everything above it.