selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Drone CI logo

Self-host Drone CI

v2.28.2

Open-source Git hosting, CI/CD pipelines, and registries

ReleaseOpen SourceApache-2.0
docker run -d -p 3000:3000 -p 3022:3022 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/harness:/data --name opensource --restart always harness/harness
Updated6 months ago
LanguageGo
Setup difficultyEasy
Stars
38 916
Ports
3000 (Web UI and API (container mapping -p 3000:3000)), 3022
Requires
Docker
Docker
harness/harness
Repository view in the Harness Open Source interfaceArtifact registries list with types, sizes and artifact counts

What is Drone CI?

Drone CI alternatives

Should you self-host Drone CI?

Drone CI scores 78/100 on selfhost.directory (how scoring works) and ranks #4 of 28 in CI/CD. It has 38 916 GitHub stars, +395 in the last 30 days.

It shipped 6 stable releases in the past year. The latest, v2.28.2, came out on 20 April 2026. New versions land roughly every 2 weeks.

Setup is easy: most people get it running in one sitting. An official Docker image is available. It is Apache-2.0-licensed and written mostly in Go.

Its closest alternative on selfhost.directory is jenkins (83/100, 26 776 stars). It scores higher overall, so compare the two before you pick. See Drone CI vs jenkins side by side.

Features

  • Artifact Registry
  • CI/CD Pipelines
  • CLI
  • Git repository hosting
  • Hosted development environments
  • Notifications and alerts
  • One-click migration from other forges
  • Pipeline templates
  • Protected branches
  • Quality Gates
  • REST API
  • Secrets encryptionOff by default; without a key secrets are kept in plaintext.
  • Upstream registry proxy
  • Webhooks

Drone CI README

Harness

Harness Open Source is an open source development platform packed with the power of code hosting, automated DevOps pipelines, hosted development environments (Gitspaces), and artifact registries.

Overview

Harness Open source is an open source development platform packed with the power of code hosting, automated DevOps pipelines, Gitspaces, and artifact registries.

Running Harness locally

How to install Drone CI

Install Drone CI with Docker

Environment variables
GITNESS_HTTP_PORT, GITNESS_DATABASE_DRIVER, GITNESS_DATABASE_DATASOURCE, GITNESS_PRINCIPAL_ADMIN_EMAIL, GITNESS_PRINCIPAL_ADMIN_PASSWORD, GITNESS_USER_SIGNUP_ENABLED, GITNESS_CI_PARALLEL_WORKERS, GITNESS_ENCRYPTER_SECRET
docker run -d \
  -p 3000:3000 -p 3022:3022 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /tmp/harness:/data \
  --name opensource \
  --restart always \
  harness/harness

Instance data lives under /data; the docs recommend a bind mount or named volume so data survives container restarts.

How to configure Drone CI

  • GITNESS_CI_CONTAINER_NETWORKSOptional comma separated list of Docker networks attached to every pipeline step; must be set together with GITNESS_URL_CONTAINER.
  • GITNESS_CI_PARALLEL_WORKERS2Optional number of parallel workers; each worker can run a single pipeline.
  • GITNESS_DATABASE_DATASOURCEdatabase.sqlite3Database connection string; defaults to the bundled sqlite database file, or a Postgres URI / key-value string when using your own database.

    values: sqlite file path, postgres:// URI, or libpq key-value string

  • GITNESS_DATABASE_DRIVERsqlite3Database driver name; set to postgres when using your own Postgres database.

    values: sqlite3, postgres

  • GITNESS_DEBUGfalseSet DEBUG log level.

    values: true, false

Drone CI releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

FAQ

How can I handle SSL errors when using the default clone task?

You can bypass SSL errors by setting clone.insecure to true, or keep SSL enabled by making your Docker environment trust the relevant certificates.

Can I override the default cloning task image used by Harness?

Yes: make the image you want available in the local Docker cache, or route pulls through a Docker registry mirror, and Harness will use the locally cached image.

How can I avoid Harness from pulling the :latest tag of an image?

Reference a specific version tag instead of :latest, and add pull: if-not-exists to the pipeline step so the image is only fetched when it is not already present locally.

What images are required to run Harness Open Source offline?

Only the drone/git image is essential for running pipelines; plugin images exist but are optional.

How can I run Harness Open Source in an offline environment without internet access?

Pre-pull the images the pipelines need on a connected machine, export them with docker save and load them into the offline Docker cache, or point the Docker daemon at a local registry mirror.

More in CI/CD

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…