Gitea
With over 57,000 GitHub stars and deployment across thousands of organizations worldwide, Gitea is the most popular self-hosted Git service, delivering a complete software development platform in a single Go binary that runs on as little as 512MB of RAM. The platform provides full repository management with pull requests featuring inline code review, branch protection rules, merge strategies including squash, rebase, and merge commit, and automated status checks through Gitea Actions. The built-in CI/CD system uses the same YAML workflow syntax as GitHub Actions and can directly reuse over 20,000 existing Actions plugins, allowing teams to migrate from GitHub with minimal pipeline rewrites using the open-source act_runner executor. The integrated package registry supports over 20 formats including npm, PyPI, Maven, NuGet, Cargo, Helm, Composer, Conda, RubyGems, Pub, and an OCI-compatible Container registry for Docker images with no additional configuration required. Project management features include issue tracking with labels, milestones, dependencies, and time tracking, alongside kanban project boards for visual workflow management. Gitea supports LFS for large file storage, built-in wiki pages per repository, webhook integrations with Slack, Discord, Telegram, Microsoft Teams, and custom HTTP endpoints, and OAuth2 authentication with LDAP, SAML, and PAM backend support. Repository mirroring enables bidirectional synchronization with GitHub, GitLab, and Bitbucket, while the comprehensive REST and GraphQL APIs power external integrations and the official tea CLI tool. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
GitLab
Used by over 100,000 organizations and ranked first in the Gartner Magic Quadrant for DevOps Platforms, GitLab is the open-core DevSecOps platform that delivers the complete software development lifecycle — from planning and source code management through CI/CD, security scanning, and monitoring — in a single self-managed application. The built-in CI/CD engine executes pipelines defined in YAML with parallel jobs, directed acyclic graph scheduling, multi-project pipelines, and auto-scaling runners on Docker, Kubernetes, or bare metal. Merge requests provide inline code review with approval rules, code owners, merge trains for serialized merging, and five merge strategies including fast-forward and semi-linear history. The integrated container registry stores Docker images alongside code, while the package registry supports npm, Maven, NuGet, PyPI, Conan, Go, and generic packages. Issue boards with epics, milestones, and labels enable agile planning, while the built-in wiki and GitLab Pages provide documentation hosting and static site publishing. Security scanning in the Community Edition includes basic SAST, secret detection, and container scanning running as pipeline jobs. The Omnibus installer bundles Rails, Puma, Gitaly, Workhorse, Nginx, PostgreSQL, Redis, Sidekiq, and Prometheus into a single package installable in minutes, while Docker and Helm chart options support containerized and Kubernetes deployments. GitLab Duo AI assists with code suggestions, merge request summaries, and vulnerability resolution. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Tapflow
Tapflow puts your team's iOS simulators and Android emulators in every teammate's browser, so QA stops queueing for the one Mac that happens to have the right build installed. A relay server you host serves the dashboard and API, stores your builds and recordings, and keeps accounts and device control on infrastructure you own. Agents on your Macs connect out to the relay and drive the simulators already installed there, injecting touches directly without WebDriverAgent or any cloud device pool. From the browser you tap, swipe, and pinch at about 30 frames per second, open deeplinks from the QA toolbar, sync the clipboard both ways, hear device audio, and cut the network to see how the app copes offline. The App Center takes .app.zip and .apk uploads and tracks each build from backlog to done, and sessions can be recorded and shared before the relay purges them after about 72 hours. CI pipelines and AI agents get a screenshot endpoint and scoped access tokens, deterministic YAML flows replay checks with a JUnit report, and roles keep viewers, QA, developers, and admins in their lanes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Harbor
The first container registry to reach CNCF graduated status with over 29,000 GitHub stars since VMware open-sourced it in 2016, Harbor transforms the basic Docker Distribution into a hardened enterprise registry with vulnerability scanning, supply chain signing, multi-datacenter replication, and project-level access control out of the box. Trivy scans every pushed image against the NVD, GitHub Advisory Database, and distribution-specific vulnerability feeds, with scan-on-push policies that block deployment of images exceeding configurable severity thresholds. Artifact signing through Cosign keyless signatures and Notation enforces content trust policies ensuring only cryptographically verified images reach production clusters. Policy-based replication synchronizes images and Helm charts between Harbor instances across multiple datacenters using repository, tag, and label filters with automatic retry and bandwidth throttling — enabling hybrid-cloud and disaster-recovery topologies. The RBAC model isolates projects with per-project quotas, robot accounts for CI/CD automation, webhook notifications, and audit logging that tracks every pull, push, delete, and configuration change. LDAP, Active Directory, and OIDC authentication integrate with existing identity providers, while the proxy cache transparently caches images from Docker Hub, Quay, and other upstream registries to reduce pull latency and rate-limit exposure. The RESTful API with embedded Swagger UI, tag retention policies, garbage collection scheduling, and immutable artifact rules complete the lifecycle management. Deploy via Docker Compose or Helm Chart on Kubernetes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.
Levelrail
Push to git, watch the deploy go live over HTTPS, and roll back in one click, all on servers you own: Levelrail is a self-hosted platform for running apps and databases without Kubernetes. Deploys start from GitHub, GitLab, Bitbucket, or Gitea webhooks and build from a Dockerfile, Compose file, image, or framework preset such as Next.js, Go, React, or Spring Boot, with preview environments per pull request, canary and blue-green rollouts, approvals, and freezes. Embedded Caddy gives every app a domain with HTTPS: self-signed by default, Let's Encrypt with one toggle, a free sslip.io address when no domain exists, or your own uploaded certificate. Provision Postgres, MySQL, MariaDB, MongoDB, Redis, ClickHouse, and more with scheduled backups that are re-downloaded and verified, Postgres point-in-time recovery, and password rotation. Metrics with deploy markers, searchable live logs, alerts, and a public status page need no separate monitoring stack. Roughly 360 one-click templates and a Cmd+K search across apps, databases, and nodes speed up daily work. Extra servers enroll with a one-time token and a reverse-dialed agent that needs no inbound ports. Sign in with passkeys, TOTP, OAuth from 20 providers, or OIDC, then scope access with IAM policies, encrypted secrets, and a tamper-evident audit log. A CLI, HTTP API, and MCP server let scripts and coding agents deploy and roll back. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Argo CD
A CNCF Graduated project with over 23,700 GitHub stars and adoption by organizations including Intuit, Adobe, Capital One, and Red Hat, Argo CD has become the industry standard for GitOps-based Kubernetes deployments since its creation at Intuit in 2018, treating Git repositories as the single source of truth for application configurations and automatically reconciling live cluster state with declared desired state. The platform supports Helm charts including Helm 4, Kustomize overlays, Jsonnet, and plain Kubernetes YAML manifests, rendering templates and applying resources through configurable sync policies with automated or manual reconciliation, pruning of orphaned resources, and self-healing that reverts unauthorized cluster changes. ApplicationSets enable templated generation of applications across multiple clusters, environments, and Git repositories using generators for pull requests, Git directories, cluster lists, and merge strategies. The web UI provides a real-time application topology view with resource health status, sync state indicators, log streaming, and a network view supporting Gateway API and Ingress visualization. Version 3.5 introduced mTLS for internal component communication, graduated user impersonation and source hydrator to beta, added native ApplicationSet management with preview applications in the UI, and delivered source integrity validation. Multi-cluster management deploys applications across development, staging, and production environments from a single Argo CD instance with RBAC, SSO via OIDC and SAML, and audit logging. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.
GoCD
GoCD treats delivery as a pipeline you can see: every commit enters a sequence of stages, passes or fails in the open, and travels from first build to production deployment along one visible, traceable path. Stages split work into jobs that run in parallel on a fleet of agents, so unit tests, integration suites, packaging, and security scans finish together instead of queueing behind each other. Pipelines connect with fan-in and fan-out dependencies, meaning a release pipeline waits for every upstream component to pass before it assembles them, and one library build can feed a dozen services. The value stream map draws that whole web on one screen, from the triggering commit through every stage to deployment, and any run can be compared with another to spot exactly what changed. Materials watch Git, Subversion, or Mercurial repositories and start pipelines on new commits, while artifacts produced by one stage are fetched, versioned, and promoted by the stages after it. Environments group pipelines and agents so test and production stay isolated, resources tag agents by capability, and elastic agents appear on Docker, Kubernetes, or cloud hosts only while work exists. Pipeline definitions can live in YAML or JSON inside a repository, changing through code review like the software they deliver, and templates keep repeated release patterns consistent across teams. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
OneDev
With over 15,100 GitHub stars and seven years of battle-tested production use, OneDev replaces entire DevOps toolchains — GitLab, Jenkins, Jira, Artifactory — with a single Java application that runs comfortably on a 1-core 2GB server for medium-sized projects. The platform unifies Git hosting with ANTLR-powered language-aware code search and symbol navigation, pull request workflows with configurable branch protection rules and required reviewers, and customizable issue tracking with scripted state transitions that automatically advance issues when code is committed, builds pass, or deployments complete. The GUI-based CI/CD editor creates pipelines without writing YAML, supporting typed parameters, matrix builds, job templates, cache management, and artifact publishing in a single visual interface. Jobs execute via Docker containers, bare metal shell, Kubernetes pods, or distributed agent pools, with web terminal access for live debugging and the ability to pause running jobs for inspection. Built-in package registries handle Docker images, npm packages, Maven artifacts, NuGet libraries, PyPI wheels, and RubyGems without external infrastructure. AI users can be assigned to issues and pull requests to autonomously implement features, review code, fix CI/CD failures, and resolve merge conflicts. The automated Kanban board supports rule-based card movement, time tracking, timesheets, and service desk ticket creation via email. Cluster deployment enables project replication across servers for high availability and horizontal distribution for scalability. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Atlantis
Every Terraform change becomes a pull request with Atlantis, which runs the plan on your server, posts the output for review, and applies only the exact change reviewers approved. Open a pull request that touches Terraform code and Atlantis automatically runs terraform plan, posting the full output as a comment and a commit status your reviewers can inspect line by line. When the change looks right, a teammate comments atlantis apply and Atlantis executes the exact plan that was reviewed, then reports the result back on the same pull request. Each directory and workspace is locked while a pull request is open, preventing two changes from applying out of order, and locks can be inspected or discarded from the web interface. Apply requirements let you demand an approved review or a mergeable branch before anything runs, and optional policy checks evaluate plans against your rules before they can proceed. Repositories describe their projects, workspaces, and custom workflows in an atlantis.yaml file, including pinned Terraform versions, execution order groups, and parallel planning or applying across projects. Because Atlantis runs inside your infrastructure, cloud credentials never leave your network, and every plan, approval, and apply is preserved on the pull request as an audit trail. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Artifact Keeper
Artifact Keeper serves as a self-hosted universal software artifact repository that consolidates container images, application libraries, and infrastructure bundles under a unified management control plane. Software development teams can publish and resolve dependencies using their existing build tools, including Docker, Helm, npm, PyPI, Maven, Cargo, NuGet, and Terraform without installing proprietary client plugins. Remote repositories act as transparent pull-through caching proxies for public upstreams like Docker Hub and PyPI, accelerating internal CI/CD build speeds while insulating production pipelines from external registry outages. Virtual repositories combine multiple local, remote, and third-party endpoints into single URLs, resolving packages across prioritized internal teams and public registries automatically. Automated security scanners evaluate incoming packages for Common Vulnerabilities and Exposures using Trivy and Grype engines, assigning letter grades and enforcing quarantine policies to block vulnerable binaries before production release. Administrators can sign package metadata with cryptographic GPG keys, configure peer mesh replication across geographic regions, and manage team permissions using OpenID Connect, SAML, and granular access tokens. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Kubero
With over 4,300 GitHub stars and a v3 release adding built-in user management, team views, and multi-language support, Kubero has established itself as the most feature-complete open-source Heroku alternative running natively on Kubernetes. The platform operates as a Kubernetes operator with two containers — kubero-ui and the operator — storing all state in etcd without an external database. Developers push code via Git integration with GitHub, GitLab, Bitea, or Gitea, and Kubero automatically builds using Buildpacks, Nixpacks, Runpacks, or Dockerfiles, then deploys to the configured domain with SSL via cert-manager. CI/CD pipelines support up to four staging environments — review, test, staging, and production — with per-stage environment variable isolation and ephemeral review apps that spin up on pull request open and tear down on close. The template catalog includes over 170 pre-configured applications like WordPress, Grafana, and PostgreSQL deployable in one click, while managed add-ons provide highly available PostgreSQL, Redis, MySQL, Kafka, CouchDB, Elasticsearch, and MongoDB alongside your applications. Security features include Trivy vulnerability scanning, GitHub and OAuth2 single sign-on, basic auth, and a role-based permission system with API tokens. The NestJS backend with Vue.js and Vuetify frontend provides application metrics, real-time logs, a built-in web console for container access, scheduled cronjob management, and deployment notifications via Discord, Slack, or webhooks. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.
Concourse
When a commit lands, a timer fires, or a pull request opens, Concourse runs the matching jobs in fresh containers and draws the entire CI/CD pipeline as a live graph you can read at a glance. Pipelines are plain YAML files that tie resources such as git repositories, registries, and buckets to jobs made of get, put, and task steps, so the same file behaves the same on every installation. Resources are checked continuously for new versions, webhooks can request an immediate check, and a version can be pinned when something needs to stay put. The dashboard lists every pipeline by team with status colors, a filter box, favorites, and a high-density view, while build pages stream colored logs and let you rerun a build with the exact same inputs. The fly command line sets pipelines, runs one-off tasks against local files from your laptop, and opens a shell inside the container of a failed step. A set_pipeline step lets pipelines configure other pipelines, and instance vars create a family of related pipelines, such as one per pull request. Teams keep projects separate and can be tied to a GitHub organization, credentials arrive at run time from Vault, CredHub, AWS, or Kubernetes, and policy rules can block disallowed images. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
docat
Hosting finished documentation for many projects at once, Docat leaves every uploaded version online for the readers still on version 2. Zip the static HTML that MkDocs, Sphinx, or mdBook produced. Send it to a project and version with curl or the docatl command line client. Tag the newest build as latest, and links get a stable address. Readers land on a home page that opens on starred favourites. A search box narrows the list, and its queries can be shared as links. Instance statistics report documents, versions, and storage. Inside any docs page, a version dropdown with a latest label moves between releases. Uploads are open at first. Claim a project and it returns a token that must accompany every later version upload or deletion. The same token hides versions from the dropdown and from search, and each project can carry its own icon. Operators can mount a small config file for custom header and footer HTML, raise the 100 MB default archive limit with an environment variable, and put nginx basic authentication in front of the write endpoints. Swagger UI and ReDoc pages at /api/docs and /api/redoc document the HTTP API for pipeline authors. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Stormkit
Stormkit delivers a self-hostable PaaS that eliminates vendor lock-in while providing Vercel-class deployment workflows. The Go backend handles build orchestration, hosting, and background job processing while the React frontend provides a complete management dashboard for applications, environments, and team collaboration. Git integration with GitHub, GitLab, and Bitbucket enables push-to-deploy workflows where every commit triggers automated builds with preview links posted directly to pull requests. Serverless functions use filesystem-based routing — each TypeScript or Node.js file in the API directory becomes an endpoint automatically, deploying to AWS Lambda with configurable timeouts. PostgreSQL database schemas ship with automatic migrations, isolated credentials per environment, and secure environment variable injection preventing credential leakage between staging and production. Custom domains provision TLS certificates automatically through Let's Encrypt with support for custom certificates and headers. The environment system creates isolated deployment contexts for production, staging, and development with independent variables, domain bindings, and auto-publish rules per branch. Privacy-respecting server-side analytics track visitors, referrers, and top paths without client cookies or third-party scripts. Role-based access control manages team permissions across applications. Docker Compose deployment provisions the full stack including the API server, hosting service, build runner, and worker server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Forgejo
Governed by the non-profit Codeberg e.V. with over 150 contributors and quarterly major releases reaching v16.0 in July 2026, Forgejo delivers a complete code collaboration platform in a single Go binary that runs comfortably on 512 MB of RAM — providing full Git hosting with SSH and HTTPS, pull requests with inline code review, issue tracking with labels and milestones, kanban project boards, wikis, and an integrated package registry supporting Docker, npm, PyPI, Maven, NuGet, and Cargo. Forgejo Actions provides GitHub Actions-compatible CI/CD with reusable workflows, OpenID Connect for secure third-party access, ephemeral runners for autoscaling, and dynamic matrix support for complex build pipelines. The platform implements ActivityPub-based forge federation allowing issues, pull requests, and stars to work across independent instances — enabling a decentralized development ecosystem similar to how Mastodon federates social networks. Organizations and team permissions provide fine-grained access control, while LDAP, OAuth2, and OpenID authentication integrate with existing identity infrastructure. Code search indexes repositories for fast discovery, LFS handles large files efficiently, and mirror synchronization imports repositories from GitHub, GitLab, and other forges. Deploy via a single static binary, Docker container, or official Helm charts with SQLite for small instances or PostgreSQL and MySQL for production workloads. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3+ licensed.