gitbundle

gitbundle: Self-Host Git Repositories and Automate Workflows

GitBundle is a self-hosted code hosting platform with a Rust-powered server and a workflow runner that supports much of GitHub Actions syntax. It may suit teams seeking control over their repositories and CI/CD, but its development is concentrated in one maintainer.

View on GitHub Compare
Stars
57
Forks
6
Stars, last 30 days
+1
Last commit
3 months ago
Contributors
1

Our take

Quietno commits in the last 90 days

Health score

23/100

How it is scored
Activity
47
Community
4
Issues
21
Pull requests
20

+1 stars in the last 30 days

  • Releases more often than 76% of the projects we track
  • Fewer contributors than 91% of the projects we track

GitBundle brings self-hosted code hosting and Actions-style automation together, but its quiet recent development and dependence on one contributor warrant careful evaluation before production adoption.

Good fit if

  • You need self-hosted repository hosting with an integrated workflow runner.
  • Your workflows use GitHub Actions syntax and event types that GitBundle supports.
  • You can evaluate and operate the server and runner yourself, including their stated software requirements.

Look elsewhere if

  • You need a project with recent commit activity or a broader contributor base; the measured data shows no commits in the last 90 days and most contributions come from one person.
  • Your workflows rely on features the README marks as not ready, such as scheduled workflows or some check and pull-request events.
  • You need a license with clearly established terms before adoption; review the repository's Elastic 2.0 license file and obligations first.
All health signals
Last commit2026-07-04 (3 months ago)
Commits, last 90 days0
Releases, last 12 months22 (latest server-v3.6.6-beta, 2026-06-30, pre-release)
Contributors1
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age2 years

Checked on 2026-10-08 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

58

Forks

7

Change since Nov 14, 2026: 0 stars·0 forks

Overview

GitBundle combines self-hosted code hosting with workflow automation. Teams can manage repositories on their own infrastructure and run CI/CD workflows through a separate runner, rather than relying entirely on a hosted code platform.

Its workflow engine aims for broad compatibility with GitHub Actions syntax, including jobs, steps, matrix expansion, expressions, and a range of event types. This may help teams reuse familiar workflow patterns while keeping the hosting and execution environment under their control.

Key Features

  • Self-hosted code hosting for repositories, groups, and user profiles.
  • Rust-powered server and a separate runner for executing workflows.
  • Workflow syntax compatible with many GitHub Actions constructs and contexts.
  • Workflow triggers for events such as pushes, pull requests, releases, and repository changes.
  • Runner registration using a server URL and token.
  • Container-based server deployment, with Docker Compose as a quickstart option.
  • Release tags distinguish stable and beta server and runner builds.

Use Cases

  • A team that wants to host repositories on its own infrastructure and run automation alongside them.
  • Developers migrating familiar GitHub Actions-style workflows to a self-hosted platform, after checking support for the events and features they depend on.
  • An organization that wants to separate workflow execution from repository hosting by placing the runner on a different machine.
  • A team evaluating a newer alternative for code hosting and CI/CD, especially if it can tolerate a concentrated maintainer base.

What you need

Detected in the repository

  • Slim (main language on GitHub)
  • A Compose file to run it with its related services

Getting Started

Clone the repository and start its Docker Compose setup:

git clone https://github.com/gitbundle/gitbundle
cd gitbundle
docker compose up -d

See the README for server configuration, container deployment, and runner registration details.

License in Plain Words

No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.

Considerations

The project is marked Quiet in the measured health data: there have been no commits in the last 90 days, despite releases during the past year, with the latest listed release a beta. Release activity therefore does not by itself establish that ongoing development or support is active. The measured contributor data shows the project depends on one person, and no issues were closed in the measured 90-day period.

The README lists Git, gitleaks, Node.js, and Docker among the requirements for both server and runner. It recommends deploying the server and runner on separate machines to avoid resource contention. The README also identifies several workflow events or event actions as not ready, including schedule, status, check events, and some pull-request actions. Confirm these gaps and inspect the license file before relying on the platform for production workflows.

Found this useful?

Share it with someone who would like gitbundle.

Comparisons