Licensing
Draft pending legal review. The terms below reflect the decision that has been taken and the notices that ship in the source; the wording should be confirmed by a qualified advisor before it is relied upon commercially. It supersedes the previous per-seat developer-license page — see Licenses bought under the old terms.
Two different questions
People arrive here with one question and it is usually two:
- Can I see the source? That is the membership. A membership pays for access to the full write-ups and the downloadable sources.
- What may I do with the source once I have it? That is this page, and it is not the same thing. Paying for access does not grant the right to redistribute. Membership opens the door; the license says what you may carry out of it.
Most of the answer to question 2 is "anything you like".
The short version
Most of the example code is MIT. Copy it, change it, ship it in a commercial product, sell what you build with it. No attribution required, no conditions worth thinking about, no fee. That covers the demos written to teach a technique — the data-binding examples, the routing examples, the grids, the invoicing and changeset and orders apps, in every framework they appear in.
A small number of examples are working components rather than illustrations, and those are dual-licensed: free under the GNU AGPL v3, or commercial for a one-time fee. Today that is:
- Localization without a rebuild — the
i18n/system for Ext JS - Theme colors at runtime — runtime theming for Ext JS, and its React, Vue, Angular and Svelte counterparts
Both are published later in the release schedule; this page will link them once they are live. A licence is not needed — and cannot be bought — before then.
Every file in those carries a header saying so, and each ships a LICENSE beside the code.
Which one do I need?
| What you want to do | What you need |
|---|---|
| Read the code, learn from it, follow the write-up | Nothing |
| Copy a few lines into your own app to solve a problem | Nothing |
| Use any MIT example in anything at all, including a product you sell | Nothing |
| Use a dual-licensed component in an internal tool that never leaves your company | Nothing |
| Use a dual-licensed component in something you release under the AGPL | The AGPL — free |
| Use a dual-licensed component in a closed-source product you ship or host | A commercial license |
| Put a dual-licensed component in a template, starter kit, component library or paid course | A commercial license, redistribution tier |
If you are unsure, ask. The answer is free and it is usually "nothing".
What the AGPL actually asks
It is not a trap, and it is three things:
- Keep the credit. Don't strip the file headers. If you ship a bundled or minified build where nobody can read the source files, put a line somewhere a user can find it saying what you used and where it came from.
- If you give it out, give the source out too. Anyone who receives your application, or uses it over a network, can ask you for its complete source under the AGPL — your parts included, not only ours. That is the copyleft, and it is the part that matters.
- Don't pretend it is yours. Modify it freely, but mark your changes as yours.
Point 2 is not limited to our files. These components compile into your application bundle, so in practice the obligation reaches your application. If that does not work for your business, that is exactly what the commercial license is for.
Commercial licenses
One-time fee, perpetual, for the thing you are building. No royalty, no revenue share, no per-seat metering, no phone-home.
| Tier | What it covers | Price |
|---|---|---|
| Open source | Your work is itself AGPL, or you only use it internally | Free |
| Application | One application you ship or host, closed-source. Unlimited developers, unlimited end users | $XXX |
| Unlimited | Every application your company builds, in perpetuity | $XXXX |
| Redistribution / OEM | You are including it in something you sell to other developers — a library, template, starter kit, framework or course | Contact |
Perpetual means the version you license stays licensed to you forever, with no renewal and no expiry. A commercial license includes one year of updates; after that your copy keeps working under the same terms and renewing is optional.
To buy one, email licensing@learnfromsaki.com with the component, the tier, and the legal name of the company the license should be issued to. You get an invoice and, on payment, a signed license document naming your company, the component and the version — the document your own compliance review will ask for.
Already shipping something and only now realize the AGPL applied? Say so. That is a normal conversation and it ends with an invoice, not a lawyer.
Who you are licensing from
Cognare holds the copyright and is the party to the license. Saki is the author, and holds a majority of Cognare — so the person who wrote the code controls the company that licenses it. There is one decision-maker, which is the answer to the question every procurement review asks.
Where an example was written by someone else, they are credited by name in the source. Nothing authored by anyone other than Saki is inside a dual-licensed component; that is deliberate, because offering a commercial license requires owning all of what is being licensed.
Ext JS is licensed separately
You must have your own license from Sencha, Inc. to use Ext JS. Nothing on this page grants one, in any direction — the MIT grant, the AGPL grant and the commercial license all cover our code only. The framework is not ours to give and is not included in any download from this site.
The same applies to React, Vue, Angular, Svelte and their dependencies, which carry their own licenses from their own authors.
Licenses bought under the old terms
The previous version of this page offered per-seat developer licenses (1, 5 or 25 developers, one year of updates) for extensions and plugins sold on the earlier site. Those licenses remain valid on the terms they were bought under. Nothing here withdraws or narrows a license already granted. If you hold one and want to know how it maps onto the terms above, write to licensing@learnfromsaki.com and it will be confirmed in writing.
Questions
Email licensing@learnfromsaki.com. Asking whether you need a license costs nothing, and the answer is usually that you don't.