kaneo (minimalist kanban) fork to experiment adding a tangled integration
github.com/usekaneo/kaneo
1---
2title: "Why Kaneo"
3description: "Why Kaneo is built around focused planning and real execution"
4---
5
6Kaneo (`/kəˈneɪ.oʊ/`) is project management that stays out of your way.
7This docs site is built to get you from zero to a running instance fast, then help you operate it confidently.
8
9## Where to Begin
10
11- [Quick Start](/core/index) for the fastest path to a running instance
12- [Installation Guide](/core/installation/index) to choose drim vs Docker Compose
13- [GitHub Integration Setup](/core/integrations/github/setup) for repo sync
14- [Gitea Integration Setup](/core/integrations/gitea/setup) for self-hosted Gitea
15- [Outgoing webhooks](/core/integrations/outgoing-webhooks) for Slack, Discord, and custom HTTP notifications
16- [API Introduction](/api-reference/introduction) for authenticated API usage
17
18## Why Kaneo Exists
19
20Kaneo follows a simple idea: **all you need, nothing you don’t**.
21
22I'm Andrej, and I created Kaneo because I was tired of project management tools that got in the way more than they helped. After years of using bloated, overcomplicated platforms that distracted from actual work, I knew there had to be a better way.
23
24The problem wasn't that these tools lacked features—it was that they had too many. Every notification, every unnecessary button, every complex workflow was pulling my team away from what mattered: building great products.
25
26I believe the best tools are invisible. They should amplify your team's natural workflow, not force you to adapt to theirs. Kaneo is built on the principle that less is more—every feature exists because it solves a real problem, not because it looks impressive in a demo.
27
28## Planning in Kaneo
29
30Planning in Kaneo is intentionally lightweight: you define the work, assign clear ownership, and move forward without ceremony.
31
32Labels are central to that flow. Use labels to group initiatives, surface cross-cutting work, and keep prioritization clear across board and list views.
33
34- Use labels to represent streams like `onboarding`, `backend`, or `customer-feedback`
35- Combine labels with priority and due dates for sharper planning
36- Keep label naming consistent across the workspace so filtering stays useful
37
38## Continue
39
40- [Deployments](/core/deployments/railway)
41- [Authentication Providers](/core/social-providers/github)
42- [Migration Guide](/core/guide/migrating-from-v1)
43- [Kaneo on GitHub](https://github.com/usekaneo/kaneo)