Home Now Projects Portfolio Socials Stats
tame.gg
Leaf / Purpur / Paper family

Keila for
faster servers.

Keila is a performance-optimized fork of Leaf and Purpur built for Minecraft servers that need Paper compatibility, sharper defaults, and less overhead in the paths players actually feel.

Java 21+ · Paper plugin ecosystem · GPL-3.0

patch stack
Paper stable plugin API and server baseline upstream
Purpur configurable gameplay behavior and server-owner controls fork layer
Leaf performance patches and modern runtime tuning perf layer
Keila tame.gg-owned defaults, polish, and network-focused optimization ship layer
Paper plugin compatible
Purpur configuration surface
Leaf performance base
Java 21+ runtime target

What's different

Paper-compatible,
but tuned for throughput.

🚀
Performance-first fork stack

Keila starts from the Leaf/Purpur lineage and keeps the server focused on practical wins: lower tick overhead, saner defaults, and optimization work that does not break the plugin surface.

hot-path focused
🧰
Familiar operations

Operators still get the Paper-family shape they know: existing plugin workflows, recognizable configuration, and a fork that can be evaluated without relearning the whole stack.

Paper ecosystem
⚙️
Tuned defaults

Defaults are selected for busy servers instead of blank test worlds, with tame.gg-owned patches sitting on top of the upstream stack.

📊
Built to measure

Changes are meant to be validated with real build and patch-apply proof, keeping Keila honest as upstream Paper-family patches move.

🔗
Open source

The code lives under the tame.gg organization so server owners can inspect the fork, follow patch history, and build it themselves.

Getting started

Clone, patch,
and benchmark.

01
Clone the repository

Keila is hosted under the tame.gg GitHub organization.

git clone https://github.com/tame-gg/keila.git cd keila
02
Apply and build

Use the repo's Gradle/paperweight workflow so upstream patches, generated sources, and the final server artifact stay in sync.

03
Test against your network

The point is practical performance. Validate the fork with your plugins, player load, and tick profile before rolling it out.