An open-source web application for implementing OKR (Objectives and Key Results) goal-setting methodology with focus, alignment, and transparency.
BurningOKR is an open-source web application for implementing the OKR (Objectives and Key Results) goal-setting methodology within organizations. It helps companies establish focus and alignment around strategic goals while fostering transparency in corporate culture. The platform provides tools to define, track, and visualize progress toward objectives across teams and departments.
Organizations, teams, and managers looking to adopt or improve their OKR implementation process, particularly those preferring self-hosted, customizable solutions over proprietary SaaS platforms.
Developers choose BurningOKR because it offers a fully open-source, self-hostable alternative to commercial OKR tools, with no vendor lock-in. It provides a complete web-based solution with modern technologies (Angular/Spring Boot) and easy Docker deployment for full control over data and customization.
Burning OKR
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Released under Apache 2.0, it allows full modification and avoids vendor lock-in, enabling organizations to tailor the OKR system to their specific workflows without licensing fees.
Provides a docker-compose file and detailed .env configuration, simplifying setup and ensuring consistent production environments, as highlighted in the installation steps.
Built with Angular and Spring Boot, it offers a responsive web interface and scalable backend, leveraging well-maintained frameworks for long-term viability and developer familiarity.
Designed specifically for the OKR methodology, it centralizes goal tracking and provides real-time visibility into progress, aligning with its core philosophy of embedding transparency into culture.
The FAQ explicitly states that only Docker deployments are supported, with no assistance for Tomcat or other setups, limiting flexibility for teams with existing infrastructure.
Requires downloading and editing multiple .env files for backend, Postgres, and optional services like Azure/SMTP, which can be error-prone and intimidating for non-developers.
The FAQ warns that npm install errors occur if not using the LTS version of Node, indicating potential compatibility headaches and a steeper setup curve for development or customization.