GitHub Release Monitor
GitHub Release Monitor turns release day into a notification instead of a discovery, watching GitHub, GitLab, Codeberg, and self-hosted Forgejo repositories in the background and reporting each new release to the channels you already read. Your watchlist is the whole interface. Add the projects your stack depends on, and scheduled checks compare what is published against what you have seen. Email carries the full notes over SMTP. Apprise carries them further, to Discord, Telegram, Slack, and dozens of other services, either one message per release or bundled into a digest for each check. Filtering happens at two levels. Global rules decide which release types count, and any repository can override them with its own channels, its own include and exclude regular expressions on tags, and its own choice of alpha, beta, or release candidate lines. A pattern the current engine no longer supports is flagged in settings rather than silently passing nothing. The list itself is portable JSON, ready to export from one install and import into another. When the alerts stop, the diagnostics page separates suspicion from evidence by testing forge connectivity, SMTP, and Apprise in one place. Accounts protect the app, dark mode and nineteen languages shape it, and the layout works on a phone. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Mycorrhiza
Most wikis bury your writing inside a database you can never quite export cleanly; Mycorrhiza keeps every page as a plain file you can open, edit, and back up with ordinary tools. Each unit of content is a hypha, a page that can be an article, an image, or a video, and hyphae transclude and link to one another so related notes weave into a dense hypertext network instead of a stack of isolated pages. You write in Mycomarkup, a markup language designed to stay unambiguous while remaining quick to type, and categories organize pages without forcing a rigid hierarchy, although nested hyphae are there when you want one. Every edit is committed to Git automatically, giving the wiki a complete, inspectable history, and recent changes flow out as RSS, Atom, and JSON feeds. Keyboard shortcuts drive navigation for people who live in the editor, authorization supports plain accounts or Telegram login, and Open Graph metadata makes shared pages preview properly elsewhere. Interwiki links connect your wiki to others, and because there is no database to provision, a single small binary serves the whole site. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Middleware
Middleware turns the pull request history your team already has into live DORA metrics, so engineering leads can see deployment frequency, lead time, recovery time, and change failure rate without building a reporting pipeline. Connect GitHub with a personal access token, group repositories into teams, and the dashboard starts charting how often you ship and how long changes take to reach production. Lead time is not one opaque number; it breaks into first commit to pull request, first response time, rework time, merge time, and merge to deploy, so the actual bottleneck is visible instead of guessed at. Merged pull requests count as deployments and revert pull requests count as incidents, which means recovery time and change failure rate appear even if your team has no separate incident tool wired up. You can exclude bot and dependency pull requests, define which branches count as production, and filter incidents in settings, so the metrics match how your team actually ships rather than how a generic template assumes. Bring it to a weekly engineering review to catch a review queue quietly doubling merge times, or open it after an incident to see if failure rate is trending the wrong way across a team. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Forgejo
Governed by the non-profit Codeberg e.V. with over 150 contributors and quarterly major releases reaching v16.0 in July 2026, Forgejo delivers a complete code collaboration platform in a single Go binary that runs comfortably on 512 MB of RAM — providing full Git hosting with SSH and HTTPS, pull requests with inline code review, issue tracking with labels and milestones, kanban project boards, wikis, and an integrated package registry supporting Docker, npm, PyPI, Maven, NuGet, and Cargo. Forgejo Actions provides GitHub Actions-compatible CI/CD with reusable workflows, OpenID Connect for secure third-party access, ephemeral runners for autoscaling, and dynamic matrix support for complex build pipelines. The platform implements ActivityPub-based forge federation allowing issues, pull requests, and stars to work across independent instances — enabling a decentralized development ecosystem similar to how Mastodon federates social networks. Organizations and team permissions provide fine-grained access control, while LDAP, OAuth2, and OpenID authentication integrate with existing identity infrastructure. Code search indexes repositories for fast discovery, LFS handles large files efficiently, and mirror synchronization imports repositories from GitHub, GitLab, and other forges. Deploy via a single static binary, Docker container, or official Helm charts with SQLite for small instances or PostgreSQL and MySQL for production workloads. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3+ licensed.
Githome
Point the gh CLI at your private Githome server and it works identically to github.com, because every REST v3 and GraphQL v4 endpoint returns byte-for-byte compatible JSON shapes, headers, Link pagination, and ETag caching. A single compiled Go binary serves the REST API under /api/v3, GraphQL under /api/graphql, git smart-HTTP transport, and a server-rendered web UI implementing the GitHub Primer design system with full functionality when JavaScript is disabled. The web interface provides repository browsing with Markdown rendering and syntax highlighting, issue tracking, pull requests with unified diffs and inline code review threads, full-text search, user profiles, and a notifications inbox. Authentication supports personal access tokens with prefix-based identification, OAuth device and web flows, and scoped permissions on every response header with only token hashes stored. The pull request system implements the complete lifecycle including async mergeable state computation, squash, merge, and rebase strategies, commit statuses, check runs, and statusCheckRollup fields. Webhooks deliver events with X-Hub-Signature-256 verification, SSRF protection, and at-least-once retry semantics. Storage supports SQLite for single-node deployments or PostgreSQL for production configurations. Performance optimizations include batch loaders replacing N+1 queries, keyset pagination, FTS-backed search, and GraphQL dataloaders. Docker deployment pulls the official multi-arch container image from GitHub Container Registry. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.