# Kacky Docs

> How Kacky works — concepts, architecture, and the API. For humans and for LLMs.

## Docs

- [Kacky Docs](https://docs.kacky.gg/): How the Kacky platform works — written once, for **humans and for LLMs**.
- [API reference](https://docs.kacky.gg/api/): The Kacky backend exposes a REST API. **The OpenAPI spec is the single source of truth** — the
- [The backend and the data](https://docs.kacky.gg/architecture/backend-and-data/): One service holds all of Kacky's truth: the backend, a .NET / ASP.NET Core app (`src/KackyGG.Api`).
- [The game servers](https://docs.kacky.gg/architecture/game-servers/): Every time you're hunting a Kacky map, you're connected to a **Trackmania 2020 dedicated server** —
- [Architecture overview](https://docs.kacky.gg/architecture/overview/): How the pieces fit together — from a player finishing a map in-game to a number on the website.
- [How the game talks to the platform](https://docs.kacky.gg/architecture/redis-streams/): A Trackmania 2020 server doesn't call the backend directly. When you cross the finish line, the news
- [Events and editions](https://docs.kacky.gg/concepts/events-and-editions/): Everything in Kacky hangs off events. This page goes a level deeper than
- [Glossary](https://docs.kacky.gg/concepts/glossary/): The Kacky vocabulary in one place. For the most important distinction — *finish* vs *record* — see
- [How Kacky works](https://docs.kacky.gg/concepts/how-kacky-works/): Kacky is a community built around some of the hardest maps in Trackmania 2020. This page is the whole
- [Concepts](https://docs.kacky.gg/concepts/): The Kacky vocabulary, from plain-language to the details that actually bite.
- [Ranks and difficulty](https://docs.kacky.gg/concepts/ranks-and-difficulty/): Two different questions people ask about Kacky: how far did *I* get, and how hard is *this map*?
- [Records vs Finishes](https://docs.kacky.gg/concepts/records-vs-finishes/): This is the most important distinction on the platform, and the one that most often gets used