OneDev is a self-hosted, MIT-licensed development platform written in Java that unifies Git hosting, code review, issue tracking, Kanban boards, service desk, time tracking, packages, and CI/CD in one system, aimed at teams that run the whole development lifecycle on their own infrastructure.

What it is

OneDev calls itself the "Unified and Autonomous Development Platform" and lives in the self-hosted DevOps and Git-based development ecosystem, implemented in Java under the MIT licence. Its topic list — ai, ci-cd, devops, git, kanban, packages, self-hosted, workspaces — defines that scope. Development happens at code.onedev.io for the sake of dogfooding, so the GitHub repository (15,249 stars, 979 forks) is a mirror; issues and pull requests are submitted at code.onedev.io instead.

The concrete problem it solves is tool sprawl. Rather than running a standalone Git host, a separate CI/CD server, another issue tracker, a Kanban tool, a customer support mailbox system, and a time-tracking spreadsheet, a team gets one platform where those concerns share the same commits and pull requests. Discussions attach to specific code or diffs and stay there; coverage information and problems found in the CI/CD pipeline are annotated onto code during review; Kanban tasks move automatically when related work is committed, tested, released, or deployed. That coupling is the product — the individual features exist elsewhere, the shared state does not.

Key capabilities

• Out-of-box code search and navigation: language-aware symbol search and navigation in any commit, click a symbol to show its occurrences in the current file, and regular-expression code search.
• Renovate integration that updates project dependencies through pull requests, merging automatically once required reviewers approve or required tests pass.
• Code annotation with coverage information and problems discovered in the CI/CD pipeline, surfaced directly during code review.
• Code discussion anywhere: select any code or diff to start a discussion, suggest and apply changes, and keep the discussion attached to the code.
• Code protection rules that require review or CI/CD verification when certain users touch certain files in certain branches.
• Automated Kanban and customizable issue workflow: manual or rule-driven state transitions, custom issue states and fields, state-syncing issue links, and confidential issues inside public projects.
• CI/CD as code without writing code: a GUI for creating jobs, templates for typical frameworks, typed parameters, matrix jobs, logic reuse, cache management, executors from containers and bare metal to Kubernetes and agent farms, plus debugging through a command to pause job execution, a web terminal, and local runs against uncommitted changes.

Who uses it and how

• Teams required to keep source and pipelines inside their own network; self-hosting is the default deployment shape, under an MIT licence.
• Support organizations using the service desk to turn customer emails into issues without requiring customer accounts, assigning different support contacts per project or customer.
• Engineering groups scaling CI/CD with Kubernetes or agent farms to run massive jobs concurrently.
• Review-heavy teams using protection rules, required reviewers, and coverage or problem annotations as merge gates.
• Groups reporting or billing on effort through time tracking, with subtask time aggregated automatically into time sheets.

Getting started

The README points to a "Get Started" entry point and the project homepage at https://onedev.io, with tutorials at docs.onedev.io, and OneDev runs out of the box in a container or on bare metal. Source, issues, and pull requests live at code.onedev.io rather than the GitHub mirror.

How it compares

The supplied facts name no paid products that OneDev replaces and no comparable tools, so it stands alone in this registry on that axis. Everything the data supports is internal to the project: MIT licence, Java implementation, and self-hosting as a first-class topic.

When to use it — and when not to

A self-hoster operates the platform, and getting full CI/CD value means running Kubernetes or an agent farm; the service desk depends on mail infrastructure, since it links incoming customer email to issues. Anyone who wants a managed service with no operational surface, or who expects GitHub to be the project's issue tracker, should look elsewhere — the mirror reports zero open issues precisely because development is hosted at code.onedev.io. The README excerpt is also feature-oriented rather than operational, so database, storage, and backup requirements have to be worked out from the documentation.