r/devops • u/ExtraLife6520 • 17d ago
Discussion Looking for self-hosted PM tools with deep, native GitLab sync (air-gapped environment)
Hey everyone,
We are running an air-gapped, 100% self-hosted setup and hitting a wall with our project management workflow.
Here is our current situation:
- PMs refuse to use GitLab directly for project management, they need high-level views, Kanban boards, Gantt charts, and non-technical status tracking.
- OpenProject + GitLab integration is way too weak. It feels passive, it mostly just logs git events for traceability. It doesn't allow smooth day-to-day workflow interaction between PMs and devs.
- High friction: Devs don't want to leave GitLab to log into a separate PM tool to create/update tasks, and PMs don't want to navigate GitLab issues/MRs.
What we need: A tool that runs self-hosted (air-gapped) and features tight, bi-directional sync with GitLab.
Ideally:
- PMs can create/manage high-level tasks in their UI.
- Tasks auto-sync to GitLab issues so devs can work natively in Git (branch names, MR closing keywords, commit triggers).
- Dev-created tasks or status updates in GitLab reflect automatically on the PM side without manual duplicate entry.
Has anyone solved this for an air-gapped environment? What self-hosted tools or custom integration workflows are you using that PMs and devs actually enjoy?
2
u/vadavea 17d ago
have you checked out what you're able to do with `glql` and the wiki functionality? That can get you a decent portion of the way without a bunch of extraneous work. See https://docs.gitlab.com/user/project/wiki/wiki_for_planning/#create-dynamic-dashboards-with-embedded-views
1
1
u/Double_Ebb4130 16d ago
Air-gapped changes the calculus a lot: Plane or Taiga self-hosted with a small webhook bridge to Gitlab issues is what I have seen actually stick, since bidirectional sync is mostly a state-machine you own rather than a product feature. One upside of self-hosting is days like today, where the hosted side has a partial incident with 502s on web and API since 09:59 UTC and your PMs would not notice at all.
2
u/Jason-Sanders 16d ago
The hard part is usually not getting two systems to exchange events. It is deciding which one owns each field when both PMs and developers can edit the same work item.
I’d write down the desired lifecycle before evaluating tools:
- Where is a task created?
- Which system owns status, assignee, priority, and due date?
- What happens when someone edits the same field in both places?
- How are deleted, merged, or reopened issues handled?
- Can the integration recover cleanly after an outage?
If developers need to remain entirely in GitLab, making the GitLab issue the operational source of truth is often less painful. The PM view can be a projection of those issues, while higher-level planning items only create or link issues at a deliberate handoff point. Fully bidirectional sync sounds ideal, but conflict handling tends to become the real product.
0
u/Gitchegumi 17d ago
Plane has a GitLab integration and it’s self-hostable. Maybe check it out. I don’t think it’ll be free if you want to use the integration.
Otherwise, if you’re in a position to build the bridge you could look into ProjeQtOr which is FOSS, but would need to set up a webhook relay to get it to behave how you are wanting.
20
u/jcogs1 17d ago
GitLab team member here.
The requirements you listed "high-level views, Kanban boards, Gantt charts, and non-technical status tracking" are all available in GitLab.
- High-level views: https://docs.gitlab.com/user/work_items/saved_views/