Our Story

Why KAEVO exists.

KAEVO started the way most bots do: a server that needed one, and every existing option almost fitting. The moderation bot hardcoded its messages. The ticket bot wanted its own category names. The logging bot decided for itself what was worth recording. Running a server meant bending your community around your tools.

So KAEVO was built on one stubborn idea: the bot adapts to the server, never the other way around. Every category, role, channel, message and permission comes from your configuration. If you've ever read "this cannot be changed" in a bot's documentation — that sentence is what KAEVO was built against.

Built in the open

The command reference is generated from KAEVO's own source, so the docs always match what's actually running. The status page shows real health, live. The privacy policy says plainly what is stored and what isn't — including the parts that aren't finished yet.

Where it's going

97 commands and counting, a growing public library of commands and flows, and a directory of communities running it. All of it free.