English
OneDev Hosting
Host Git repositories with built-in CI/CD pipelines, code search, and issue tracking in one server.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- 1dev/server:latest
- Default port
- 6610
How OneDev works
OneDev hosts Git projects and connects code changes with pull requests, discussions, issues, builds, and packages. Language-aware search and navigation help developers find symbols or regular-expression matches, while branch rules can require reviews or successful jobs before selected changes are accepted.
Issue workflows include custom fields, states, links, confidential items, time tracking, queries, and Kanban boards that can move work manually or through rules. CI/CD pipelines are defined with jobs and reusable templates, and the product supports executors ranging from local containers or bare metal to separate agents and Kubernetes capacity.
Key OneDev features
Package registries keep build outputs close to the projects that create them, and cross-references connect issues, commits, pull requests, builds, and releases. Security scans can report dependency, binary, container-image, licence, or secret findings, while code annotations place coverage and problems directly beside review context.
The broad feature set does not mean every execution resource is included with a small application plan. Large builds, parallel jobs, container-image scans, package archives, and repository indexes can exceed the web service footprint. Separate agents, Kubernetes clusters, deployment targets, registries outside OneDev, and external AI services require their own infrastructure or accounts.
OneDev vs GitLab
OneDev unifies Git repositories, code search, reviews, issues, Kanban, CI/CD, security feedback, and package registries in a self-hosted product. GitLab provides a wider commercial DevSecOps platform with merge requests, pipelines, project planning, package and container registries, security features, governance controls, workspaces, and optional AI capabilities across paid tiers.
GitLab may be the stronger choice for organisations needing vendor support, detailed compliance controls, broad integrations, and a large established ecosystem. OneDev is attractive when a team wants an integrated development server and accepts responsibility for executors, package growth, identity configuration, upgrades, and operational troubleshooting.
Who uses OneDev
Development groups can use OneDev for source hosting, review, sprint boards, release pipelines, package distribution, and internal service-desk workflows. Teams with several related repositories may organise projects as a tree and inherit common settings from parent projects to reduce repetitive administration.
Projects with heavy build matrices, large binary packages, frequent scans, or many concurrent jobs require resources beyond an entry application plan. Email-linked service desk workflows, subscriptions, and recovery are also affected by the hosted platform’s disabled application-email policy.
Self-hosting OneDev: requirements and cost
Demand depends on repository size, clone and push activity, code indexing, concurrent reviews, issue history, CI job concurrency, caches, artifacts, scans, and package storage. The catalogue records PostgreSQL and MariaDB as Not required; project data, repositories, indexes, job records, and packages still form one persistent application system.
On AvaHost, OneDev uses Plan 1 at €2. The hosted OneDev package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so email-based service desk flows, notifications, subscriptions, and recovery are unavailable. Dedicated build agents, Kubernetes execution, deployment destinations, external registries, scanning services, and AI providers are not part of the hosting plan.
F.A.Q
OneDev is mapped to €2 on Plan 1 for a small development workspace. Repository growth, code indexes, concurrent reviews, CI jobs, caches, artifacts, security scans, and package archives can raise demand quickly. Teams intending to execute builds on the same installation should monitor resource use and plan additional capacity.
A custom hostname can serve the OneDev interface through automated HTTPS once DNS points to AvaHost. Update clone URLs, callbacks, package endpoints, webhooks, and build variables that contain the old address. Test repository access, pull requests, package publication, and any connected executor after the domain is changed.
The plan provides the OneDev application, not a managed executor fleet. OneDev supports container, bare-metal, agent, and Kubernetes execution models, but agents, clusters, deployment targets, external registries, and their compute are separate. Build concurrency and artifact size should be planned independently from ordinary repository and issue activity.
The hosted OneDev package cannot send application email. Email-based service desk intake, subscriptions, verification, notifications, and password recovery therefore cannot be used. Keep administrator access current and choose only supported non-email integrations with separate credentials, then test them before relying on event delivery. Keep administrator access current and choose only supported non-email integrations that can be configured with separate credentials, then test them before relying on event delivery.