Skip to content
Code Recycle
Free · open sourceAGPL-3.0Unclaimed listing

lila is by lichess-org — not by us.

We indexed this project so people can find it. We are not selling it, we host no copy of the code, and we are not affiliated with or endorsed by its authors — get it from them.

Indexed Aug 1, 2026 · 18,517 stars at index time. Maintainers: claiming verifies your identity and unlocks a higher assurance tier. Removal requests are honored.

game · for humans & their agents

lila

unclaimed listingactively maintainedFreeAGPL-3.0

♞ lichess.org: the forever free, adless and open source chess server ♞

by Open Source Community · New publisher

Get it from the authors ↗Open live demo ↗

Every claim on this page is refundable if it is untrue — refund policy.

☆ Save
lichess.org

**lichess-org/lila** is an open-source project by lichess-org: ♞ lichess.org: the forever free, adless and open source chess server ♞. Indexed here so it can be found — not resold.

It is free. Get it from the upstream repository: https://github.com/lichess-org/lila

AGPL-3.0 (AGPL §13): running a modified version as a network service obliges you to offer its source to users. List-only here — any hosted-trial or one-click-deploy feature needs a specific AGPL compliance review first.

From the project's own README (excerpt, reproduced for discovery under its AGPL-3.0 license):

lichess.org

Lila (li[chess in sca]la) is a free online chess game server focused on realtime gameplay and ease of use.

It features a search engine, computer analysis distributed with fishnet, tournaments, simuls, forums, teams, tactic trainer, a mobile app, and a shared analysis board. The UI is available in more than 140 languages thanks to the community.

Lichess is written in Scala 3, and relies on a modified Play 2.8 framework. scalatags is used for templating. Pure chess logic is contained in the scalachess submodule. The server is fully asynchronous, making heavy use of Scala Futures and Pekko streams. WebSocket connections are handled by a separate server that communicates using redis. Lichess talks to Stockfish deployed in an AI cluster of donated servers. It uses MongoDB to store more than 12 billion games, which are indexed by elasticsearch. HTTP requests and WebSocket connections can be proxied by nginx. The web client is written in TypeScript and snabbdom, using Sass to generate CSS. All rated games are published in a free PGN database. Browser testing done with Browserstack. Proxy detection done with IP2Proxy database. Please help us translate Lichess with Crowdin.

See lichess.org/source for a list of repositories.

Join us on Discord for more info. Use GitHub issues for bug reports and feature requests.

Installation

The Wiki describes how to setup a development environment.

HTTP API

Feel free to use the Lichess API in your applications and websites.

Supported browsers

Name Version Notes ----------------- ------- -------------------------- Firefox 115+ Full support (recommended) Chromium / Chrome 112+ Full support Edge 111+ Full support Opera 97+ Reasonable support Safari 16.2+ Reasonable support

Older browsers will…

Preview

See what it does before you commit. Previews show behavior, never source code.

01Capabilities

Does

  • + Search
  • + Programmatic API

Doesn’t

  • No exclusions declared

02Requirements & stack

Depends on

  • Authentication
  • PostgreSQL database

Credentials needed

None declared

Stack

scala

03Community

No endorsements yet

No verified confirmations yet — be the first.

Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.

Sign in to confirm — weight comes from verified usage, not vote count.

04Trust Passport

Full passport →
/100

0/0 automated components pass. An automated score is never a security guarantee.

This listing is unclaimed, so publisher identity cannot be verified and it stays below the “verified” tier by design — that is a statement about the listing, not about the project’s quality. Our automated scans still ran; a maintainer who claims it unlocks identity verification.

! Not verifiedreviewed Aug 1, 2026 · re-verification due Oct 30, 2026
  • publisher identity Publisher status verified; 0 verification(s) on file
  • malicious pattern scan No known malicious-behavior patterns detected in reviewed content
  • capability contract All 0 observed capability reference(s) match the declared manifest
  • agent safety scan No injection patterns in agent-readable content
  • provenance No release signature or provenance attestation
  • behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.

Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.

VersionChannelReleasedNotes
0.0.0stableAug 1, 2026Indexed listing — see the upstream repository for real release history.