Deploy from Git.
Control it with Dockly.

A lightweight deployment platform for your own server — build with Docker, watch every release, and roll back with confidence.

View Dockly on GitHubStart self-hosting

Open source · single Go binary · Docker-native · no database or queue

Dockly
Dockly deployment dashboard showing healthy applications and recent releases
Features

Everything you need to ship.

Connect a repository, build an image, release it, and keep the operational context close. Dockly handles the useful path without turning one server into a platform team.

Git to Docker

Deploy from Git,
not a pipeline maze.

Choose a repository and branch. Dockly clones the exact revision, builds its Dockerfile, starts the container, and records the image and commit as one release.

  • Immutable release images tied to the Git commit.
  • Server-side environment values kept out of API responses.
  • Manual or webhook deploys from the same release path.
Read the deployment guide →
Dockly deployment pipeline moving from repository clone through image build, health check, and release
Health and logs

It checks what
it ships.

Dockly waits for your HTTP health endpoint before considering a release ready. Container state and recent output stay one click away in the application view.

  • HTTP health probes against the published service.
  • Recent Docker logs without leaving the dashboard.
  • Accurate engine status so failures are visible, not implied away.
Dockly service health panel showing three healthy applications and uptime monitoring
Release history

Every release has
a way back.

Dockly keeps the commit, image, trigger, timing, output, and result for every deployment. Select a successful release and put that image back into service.

  • Automatic recovery when a new health check fails.
  • One-action rollback to a retained successful image.
  • A release trail that shows what ran and when.
Dockly deployment history with a previous image selected as a rollback target
API and webhooks

Works with the tools
you already use.

The dashboard uses the same JSON API exposed to your scripts. Use bearer authentication for automation and a dedicated token for Git provider webhooks.

  • Documented JSON API for applications and releases.
  • Push-triggered deploys with a scoped webhook token.
  • No proprietary build file beyond Git and Docker.
Open the API reference →
Dockly API deployment request and token-authenticated webhook response
Open source

Own the platform, not another bill.

Dockly is MIT licensed and built for one trusted Docker host. The code, state, and running containers stay on infrastructure you control.

Community

The complete Dockly deployment platform.

$0open source, forever

Included:

  • Git and Docker deployments
  • Health checks, logs, and monitoring
  • Release history and rollbacks
  • Environment values, API, and webhooks
  • Responsive embedded dashboard
Clone Dockly →

Small by design

Useful operations without a cluster behind the dashboard.

One host

Bring:

  • A Linux server
  • Docker Engine and Compose
  • A Git repository with a Dockerfile
  • An HTTPS proxy for production access
Read operations guide
No token billing or hosted control planeState is portable and inspectableBuilt with the Go standard library
Questions

Frequently asked questions.

What does Dockly run on?

Dockly targets a single trusted Linux host with Docker Engine. The provided Compose file mounts the Docker socket and stores state in a named volume.

Does it need Kubernetes or a database?

No. Dockly is one Go binary with an embedded dashboard and an atomic JSON state file. Git and the Docker CLI are its runtime contracts.

What happens when a release is unhealthy?

Dockly removes the unhealthy container and attempts to restore the image that was running before the deployment. The failed release remains in history with its error and output.

Can Dockly deploy private repositories?

Private repositories work when Git credentials are already available inside the Dockly runtime. First-class deploy-key management and encrypted-at-rest secrets are intentionally beyond the current MVP.

Read the project status →

Ship without surrendering the server.

Deploy from Git, run with Docker, and keep every release within reach.

View Dockly on GitHubQuick start