e2e8
Licences & credits
To the authors and maintainers whose work appears below,
e2e8 is built on top of things you made and gave away. Chess engines, piece artwork, opening data, typefaces, libraries. We did not have to pay for any of it, and in most cases we did not have to ask. We do not treat that as free money.
So here is our position, plainly. We do not ship anything we do not have the right to ship. Where a licence asks for credit, we give it. Where it asks that the source be reachable, we link it. Where a licence forbids commercial use, we do not use the work at all - not in a reduced form, not behind a free tier, not at all. That has cost us real things: sixteen piece sets we wanted, and a move-analysis component we had already built on and shipped, removed once we read its licence properly rather than argue our way around it.
If you think we have used something of yours incorrectly, or credited you wrongly, or missed you entirely - we want to hear it, and we will fix it. Not negotiate it. Write to kiterick123@gmail.com and a person will answer you.
Erick
Founder, e2e8
Chess engines we send to your browser
The engine runs in your browser, on your own CPU - never on our servers. (Your games themselves are a different question: completed analyses are saved and shareable by link, and positions go into a shared evaluation cache. That is a privacy matter rather than a licensing one, and we would rather say it here than let this sentence imply otherwise.) Because the engine runs on your machine, we distribute these binaries to you and their licences apply in full. Stockfish's own terms put it directly: whenever you distribute Stockfish you must include the licence and the full source code, or a pointer to where the source for the exact binary can be found. Both are below - and the licence texts ship next to the binaries themselves: AGPL-3.0, GPL-3.0, Stockfish AUTHORS.
An honest note on the source pointer: this package declares no repository or homepage of its own, so the link above goes to the exact published version we ship rather than to a source tree. The engine it builds is Stockfish, whose full source is linked below. If you maintain this build and would like us to point somewhere better, tell us and we will change it the same day.
Our own conversion of the authors' own release — format only, no retraining, from weights whose SHA-256 the authors publish. The notice above records the source, the converter and its version, the date, and both sets of hashes; running scripts/convert-maia2.py reproduces the file byte for byte. "It works" is not provenance: with the previous model we first tried pre-converted copies found online, found they carried a producer stamp from an unreleased build we could not identify, and deleted them.
Maia 1 — nine separate GPL-3.0 networks, one per rating — was the opponent here until 1 August 2026. No screen loads it any more, but its nine files are still served from /maia/ with their own GPL-3.0 licence and modification notice beside them. We switched because we could measure a reason: the two are indistinguishable at picking the single likeliest human reply, but this one puts more probability on the move a human actually played, and it is the only one whose own evaluation is honest enough to resign on. It costs 88.9 MB against 3.3, downloaded once and cached.
One thing worth saying plainly, because it is your disk and not ours: the first game against the bot downloads its network (88.9 MB) and keeps it in your browser's cache, so the next game starts at once and changing rating downloads nothing. The engine's own networks (74.9 MB and 3.5 MB) are kept the same way. Clearing your browser's site data removes them.
Artwork, type and sound
Copyright (c) Colin M.L. Burnett Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Chess data
Software libraries
e2e8 depends on a few dozen open-source packages. All but two are permissive - MIT, ISC, Apache-2.0 or BSD. The two are the Stockfish builds credited above, AGPL-3.0 and GPL-3.0; the only other copyleft files we serve are the Maia 1 networks, GPL-3.0, credited above with their licence beside them. The packages doing the most visible work: chess.js (BSD-2-Clause), which knows the rules of chess and is what our own analysis is built on; Next.js and React (MIT); Framer Motion, Recharts, Lucide, dnd-kit and ts-fsrs (MIT/ISC); LiveKit and hls.js (Apache-2.0). The complete list with versions is in package.json in our source tree.
Services we call
Lichess - opening explorer, cloud evaluations, endgame tablebases, study import and account linking, all through their public API. Chess.com - their documented public API, for importing your own games and ratings. Wikibooks - opening theory. Vercel hosts the site. Supabase, Stripe, LiveKit, Cloudflare and Resend - our database, payments, live classroom, video and domain, and email.
Lichess deserves a separate line. They publish billions of games under CC0 and tell people to use them for anything, including commercially. A great deal of what makes free chess software possible traces back to that decision.
What we deliberately do not use
A credits page only means something if it can say no. Ours has, three times, and each time it cost us something we wanted.
Sixteen piece sets. Most of the beautiful chess piece artwork in the open-source world is licensed CC BY-NC-SA - NonCommercial. e2e8 charges coaches a subscription, so that licence is a flat no for us. We could not use those sets by crediting harder, or by giving them away free, or by open-sourcing our own code. So we went and found artwork whose authors permit commercial use, and used that instead.
A move-analysis component we had already shipped. Part of how we detect sacrifices had been ported from another open-source project. When we checked its licence properly, it was CC BY-NC-SA as well. It was working, it was live, and our own comments admitted where it came from. We deleted it and wrote our own from the underlying algorithms, which are public knowledge and belong to nobody. That is recorded in our repository, dated, in a file called NOTICE-analysis.md - because the honest version of this page is the one that survives someone checking.
Maia 3. The newest and strongest version of the human-like opponent we do ship. Its code is openly licensed, but the weights themselves state no licence at all - and silence is not permission. The file is sitting there, downloadable, and we are not taking it. If the authors publish terms that allow it, we would like to; until then the human-like bot is Maia 2, credited above. It needs a cross-origin-isolated page, so on pages that embed video or a live class it is the plain engine that plays.
We also do not scrape any service that asks us not to, and we do not build on data whose terms forbid it - even where nothing technical stands in the way.
Something wrong or missing on this page? Write to kiterick123@gmail.com. If we got it wrong we would rather hear it from you than not know.