We self-host a backend on Hetzner using Docker Swarm, with PostgreSQL on a separate VM. GitLab CI builds the images, pro
Solo founders and small teams self-hosting a backend on Docker Swarm (Hetzner, PostgreSQL on a separate VM) with GitLab CI building images, who publish releases from a pipeline and feel the gap between image, config, and migration state.
A CLI plus a small state store that runs in the GitLab CI publish step: it records the commit, image digest, config hash, and migration image tag as one release record. On deploy it checks the record against the running Swarm services and the database migration version, refuses to deploy a mismatched migration image, and on a mid-release service failure prints the exact rollback steps for the services already updated. The dashboard is a read-only view of these records.
The only evidence project is the Reddit thread itself (score=3), which is a question, not a tool. No existing project in the evidence covers this gap: nothing pins migration images to the app commit, nothing defines a complete release across image, config, and DB, and nothing handles recovery when only part of a release applies. The gap is the atomic release record and its rollback path.
Platform: Docker Swarm with GitLab CI and PostgreSQL on a separate VM, publishing to ECR. Hardest problem: making the database migration and the multi-service update behave as one atomic unit when Swarm has no native cross-service transaction, so the tool must track applied state and drive rollback itself. Reusable open-source pieces are not named in the evidence, so the state store and CLI are built from scratch.
One-time license for self-hosters, with an optional subscription for hosted release-state history. No prices set.
The tool depends on the team's CI and Swarm setup, and rollback of a succeeded migration is inherently limited; if the database cannot be reverted, the tool can only report and guide recovery rather than undo. Adoption also requires changing the publish step in GitLab CI.
Only the Reddit thread (score=3) raises the problem. No project in the evidence ships a solution, so the space is open.
A CI step that writes one release record pinning commit, image digest, config hash, and migration image tag, plus a pre-deploy check that blocks a mismatched migration image.
Atomicity across services and the database. Swarm updates services one by one and PostgreSQL migrations are not automatically reversible, so the tool must track partial state and drive recovery.
The thread shows teams patch it by hand: the publisher pins app versions from the commit but still grabs the newest migration image from ECR, and nobody has defined what a complete release is or how to recover when only part applies.
Every quote on this page was matched against its original post on Hacker News, GitHub, DEV.to or Product Hunt, and each claim links to that thread. Unverifiable items are discarded before publication.
See all 20 evidence-backed needs this week — updated daily, every trend traced to original posts and exact quotes.
Subscribe $19.99/mo →Not sure what to build first? See the ten worth a look →