What It Does
Lubeno is an early-stage code hosting and collaboration platform built from the ground up to support Jujutsu (jj), the Git-compatible version control system. Unlike GitHub or GitLab which bolt jj support on top of Git-centric workflows, Lubeno treats jj’s change-centric model as a first-class citizen. Its primary differentiator is native support for stacked pull requests — breaking large changes into sequential, dependent PRs that can be reviewed and merged independently.
The platform aims to improve code review velocity by enabling atomic, small PRs that reduce reviewer cognitive load and allow developers to continue working on dependent changes without waiting for upstream reviews to land.
Key Features
- Native Jujutsu (jj) support — not a Git compatibility layer but built for jj’s change model
- Stacked pull request management — create and manage chains of dependent PRs
- Per-commit review routing — assign specific commits or stack layers to specialist reviewers
- Private repository support (public repos not yet documented)
- Web-based code review interface
Use Cases
- Teams already using jj who want a hosting platform that understands jj natively instead of translating to Git workflows
- Organizations adopting stacked diff workflows who want integrated hosting + review tooling
- Small teams experimenting with alternatives to GitHub’s PR model
Adoption Level Analysis
Small teams (<20 engineers): Potentially fits for jj-enthusiast teams willing to adopt an early-stage platform. However, the lack of CI integration, API, and mature tooling (noted by HN commenters) makes this risky even for small teams. Medium orgs (20-200 engineers): Does not fit. No documented production customers, no CI/CD integration, no API, immature UI. Medium orgs need reliability and ecosystem integration that Lubeno cannot yet provide. Enterprise (200+ engineers): Does not fit. No enterprise features, no compliance capabilities, no SLA, unknown security posture.
Alternatives
| Alternative | Key Difference | Prefer when… |
|---|---|---|
| GitHub + Graphite | Graphite adds stacked PR management to GitHub’s mature ecosystem | You need production-ready stacked PRs with existing GitHub workflows |
| GitLab | Full DevOps platform with CI/CD, security scanning, and mature review tooling | You need an integrated DevOps platform, not just code hosting |
| Gerrit | Google’s code review tool with native per-change review, used at massive scale | You need proven per-commit review at scale (Android, Chromium, etc.) |
| Forgejo/Gitea | Self-hosted lightweight Git forges | You need self-hosted Git with a simple, proven UI |
Evidence & Sources
- Lubeno homepage
- HN discussion: Lubeno with stacked PRs and JJ support
- HN discussion: Lubeno built on jj
- HN discussion: Reinventing the Pull Request
Notes & Caveats
- Extremely early stage: UI described as “rough” by early HN commenters. No CI integration, no API, no IDE plugins documented.
- No public customers: No case studies, testimonials, or documented production usage found.
- Private repos only: At time of review, only private repositories are supported, which limits discoverability and community building.
- Niche positioning risk: Building exclusively for jj users limits the addressable market significantly. jj itself has ~27k GitHub stars but very early enterprise adoption.
- Competitive threat: GitHub reportedly working on native stacked PR support (mentioned in HN discussions), which could undercut Lubeno’s primary differentiator. Graphite already has production deployments at Shopify and Asana.
- Unknown funding/team: No public information about funding, team size, or company structure found.