The Mosh Licensing Model: Freedom, Trust, and Responsibility

The Mosh licensing model is simple, deliberate, and built for both freedom and trust. Mosh (Mobile Shell) is released under the GNU General Public License (GPL) version 3. This means you can run it, study it, modify it, and share it. But if you distribute your modified version, you must also share your source code under the same license. This reciprocity is the backbone of the model.

GPLv3 protects Mosh from being turned into closed software. It’s a copyleft license, which forces derivative works to remain open. No dual licensing tricks. No hidden clauses. The terms are clear: share changes, respect the license, keep the ecosystem transparent.

For developers, this licensing model matters. It enables collaborative improvement while shielding against corporate lock-in. It aligns with long-term sustainability—every contribution is kept in the open, accessible to all future users. The model also gives legal protection against patent aggression through the GPLv3’s explicit patent clauses.

Distributing Mosh in a commercial product is allowed, but compliance is non‑negotiable. Include the license text, provide access to the full source code, and ensure any linked GPL-covered components remain under GPL. Static or dynamic linking to proprietary code will likely violate terms, so review legal implications before release.

From a governance perspective, the Mosh licensing model is lean. No contributor license agreements, no complicated governance boards—just the GPLv3, enforced by clear community norms and a transparent upstream. This keeps the project fast-moving, while protecting both contributors and users.

If you need a resilient, secure remote shell in your product or workflow, understand the license before deployment. The Mosh model gives you power and responsibility in equal measure.

See what’s possible—try it on hoop.dev and have it live in minutes.