Get YAFFS

Download & licensing options

YAFFS is available under the GNU GPLv2 for open‑source use, and under straightforward commercial licences for proprietary products.

Licensing at a glance

The YAFFS code base is the same in both cases. The difference is which obligations and permissions best match your project.

GPLv2 licence Commercial licence
Open‑source

Use YAFFS in GPL‑licensed software at no monetary cost.

Proprietary‑friendly

Use YAFFS in closed‑source or proprietary products under a paid, commercial licence from Aleph One.

Key obligations
  • You must comply fully with the terms of GPLv2.
  • In practice this normally means that users of your product can obtain the complete corresponding source code.
Key properties
  • Non‑exclusive, perpetual and world‑wide.
  • Royalty‑free: a one‑time fee per product line, not per unit shipped.
  • Lets you keep your own source code proprietary.
Good fit when
  • Your entire project can happily be GPLv2 or compatible.
  • You are evaluating YAFFS or building an open‑source design.
Good fit when
  • You are shipping proprietary firmware or software.
  • You cannot or do not wish to disclose your full source code.
Important: This is a simplified overview. Please read the full GPLv2 text carefully and discuss commercial licensing terms with us if you plan to ship YAFFS in a product.
Download

Source code & quick start

Browse or download the source

Clone with Git

For most development work we recommend cloning the Git repository so you can easily track updates and contribute fixes where appropriate.

git clone https://github.com/Aleph-One-Ltd/yaffs2.git

Evaluating YAFFS?

If you are considering YAFFS for a new design, you can start under GPLv2, experiment with the source code and run your own tests without any commercial agreement.

When you are ready to ship a proprietary product, we can work with you to arrange a commercial licence and, if needed, additional consulting.

Discuss licensing & support

Questions about legal obligations?

The GPL has important practical consequences. We strongly recommend that your legal team review the licence text and, if you are unsure, consider a commercial licence.

We cannot give legal advice, but we can help you understand the technical implications and typical usage patterns we see in the field.