Kaneo

Kaneo was written in reaction to project management platforms that pull attention away from the work. Its argument is that most tools fail by having too many features rather than too few, so every notification and button has to earn its place.

The application runs as a single container beside PostgreSQL, which keeps deployment close to trivial. Images are published to a container registry, and a Compose file with a handful of environment variables is the whole setup.

Several deployment routes are documented for teams with different appetites for configuration.

• One-command install: a CLI called drim sets up HTTPS, the database, and every service in a single step.
• Docker Compose: the bundled container plus PostgreSQL, configured through an env file.
• Coolify: a dedicated compose file, with the auth secret and database password generated for you.
• Kubernetes: a Helm chart covers cluster installs, production configuration, and TLS setup.
• Split images: advanced setups can still run separate API and web images.

Configuration comes down to a client URL, an auth secret, and a database password, and the documentation covers the CORS and hostname mistakes that trip up first installs. Kaneo is MIT licensed and self-hosted, so project data stays on the team's own infrastructure, and a hosted version exists for anyone who would rather not run it.