July 27, 2026
Push to main, pull from drama
Show HN: Trylle – The Next-Gen Git Platform for Modern Teams
New GitHub rival drops big promises, but commenters want proof not buzzwords
TLDR: Trylle is pitching itself as a one-stop Git platform where teams can review code, track work, and run automation in one place. Commenters weren’t sold: they blasted the buzzwords, questioned what makes it different from GitHub, and wanted proof the team and product are the real deal.
Trylle arrived on Hacker News promising to be the all-in-one place for planning, reviewing, automating, and shipping code without the endless tab-hopping. The pitch is simple enough for non-experts: keep code changes, comments, tasks, and automated checks in one place, with extras like stacked pull requests, branch-side triage, migration tools, and security updates meant to make team work smoother. On paper, it sounds like the dream setup for busy software teams.
But the real show was in the comments, where the launch got hit with a classic internet side-eye. The biggest complaint? The marketing copy. One commenter basically said the words “next-gen” and “modern” are an instant red flag, the kind of slogan that makes buyers clutch their wallets and assume there’s no real substance underneath. Ouch. Another looked at the feature list and went straight for the jugular: if this looks like GitHub in a different outfit, what exactly is the point?
The skepticism kept piling on. People wanted to know who the humans behind this thing actually are, which is the startup equivalent of “hard launch or soft launch?” And there was also a practical dunk: claims of GitHub-compatible automation were met with a big “sure, Jan,” with commenters warning that even established tools struggle to truly copy GitHub’s behavior. The vibe was less “welcome future of coding” and more “nice demo, now show receipts.”
Key Points
- •Trylle is presented as a Git platform that combines code review, stacked pull requests, issue triage, CI visibility, automation, and governance in one interface.
- •The article describes a new shell-completion feature for the `nimbus` command, adding support for bash and zsh.
- •Hidden CLI flags remain masked by default and can be revealed during completion generation by setting `NIMBUS_COMPLETE_HIDDEN=1`.
- •The completion implementation adds `completion.go`, includes a seed `GenBash()` function in `completion_gen.go`, and keeps the change backward-compatible.
- •The platform description also highlights repository-event automations, audit trails, JWT refresh tightening, rotating signing assertions, and staged operational controls for legacy session renewal callers.