Kestrix defines CI/CD pipelines in HCL and resolves them into a DAG. A task runs only when the repositories its trigger names have changed. Live task logs in a React Flow UI, and remote runners that only make outbound HTTPS requests.
I built it for myself, to keep my DevOps projects separate from my coding projects. Kestrix treats repositories as inputs rather than as owners of the pipeline, so one pipeline definition can react to changes in several repositories.
What it does:
1. Pipelines in HCL: Pipelines are declared with variables, dependencies, and trigger expressions instead of per-repository YAML.
2. DAG per run: Kestrix resolves a Directed Acyclic Graph for every run. A task runs when its trigger matches the changed repositories, and tasks that don't match are skipped.
3. Runners: Remote runners make only outbound HTTPS requests, so they need no inbound ports. In Docker mode, tasks run with `--cap-drop ALL` and `no-new-privileges`.
4. Terraform / OpenTofu: The provider (`terraform-provider-kestrix`) manages Kestrix projects.
Kestrix is self-hostable: one binary plus PostgreSQL, or Docker Compose. The source is public under PolyForm Noncommercial 1.0.0. It is free for non-commercial use, and commercial use needs a paid plan.
My free GitHub Actions minutes ran out this month so my CI now runs on my Mac at home. Can a Kestrix runner work behind a home router like that? And if three merges land during one run, does it run once on the newest commit?
The remote runners making only outbound HTTPS requests is the part I'd want to understand first — with no inbound ports, how do live task logs get back to the React Flow UI, and what happens to a run if that outbound connection drops mid-task?
Seeing why a task was skipped would matter as much as its logs here. With several repositories in one pipeline, the trigger needs to be easy to inspect.
About Kestrix on Product Hunt
“Repo-agnostic CI control plane with DAG-based triggers.”
Kestrix launched on Product Hunt on October 30th, 2026 and earned 77 upvotes and 7 comments, placing #18 on the daily leaderboard. Kestrix defines CI/CD pipelines in HCL and resolves them into a DAG. A task runs only when the repositories its trigger names have changed. Live task logs in a React Flow UI, and remote runners that only make outbound HTTPS requests.
Kestrix was featured in Developer Tools (523.2k followers) on Product Hunt. Together, these topics include over 94.2k products, making this a competitive space to launch in.
Who hunted Kestrix?
Kestrix was hunted by Damian Giebas. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Kestrix stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hi Product Hunt!
I'm Damian, the author of Kestrix.
I built it for myself, to keep my DevOps projects separate from my coding projects. Kestrix treats repositories as inputs rather than as owners of the pipeline, so one pipeline definition can react to changes in several repositories.
What it does:
1. Pipelines in HCL: Pipelines are declared with variables, dependencies, and trigger expressions instead of per-repository YAML.
2. DAG per run: Kestrix resolves a Directed Acyclic Graph for every run. A task runs when its trigger matches the changed repositories, and tasks that don't match are skipped.
3. Runners: Remote runners make only outbound HTTPS requests, so they need no inbound ports. In Docker mode, tasks run with `--cap-drop ALL` and `no-new-privileges`.
4. Terraform / OpenTofu: The provider (`terraform-provider-kestrix`) manages Kestrix projects.
Kestrix is self-hostable: one binary plus PostgreSQL, or Docker Compose. The source is public under PolyForm Noncommercial 1.0.0. It is free for non-commercial use, and commercial use needs a paid plan.
Repository: https://gitlab.com/kestrix/kestrix (GitHub mirror: https://github.com/Draqun/kestrix). Docs: https://kestrix.gitlab.io/kestrix/
Do you think this will catch on? Am I the only one who prefers to keep DevOps projects separate from strictly software development projects?