Otter Wiki
Every page in Otter Wiki is a plain Markdown file and every save is a git commit, so a small team gets a simple wiki whose history never goes missing. The editor highlights Markdown as you type, offers a toolbar for headings, lists, tables, code, alerts, and images, and can show a live preview beside the source. Paste or drop an image into the editor and it is stored as a page attachment. History, blame, and changelog views, with RSS and Atom feeds, show who changed what and when. Beyond standard Markdown you get footnotes, task lists, math formulas, Mermaid diagrams, alert boxes, and spoiler or folded blocks, plus experimental embeddings such as sortable data tables, info boxes, image frames, videos, and included pages. A customizable sidebar shows a menu, a page index, or both. Search offers case-sensitive and regular expression options. Dark mode is built in. Admins decide whether anonymous visitors, registered users, or approved users may read, write, or upload, grant rights per user, close registration, or require email confirmation. An optional, experimental git web server lets people clone, pull, and push the wiki, and changes can be pushed to or pulled from a remote repository over SSH. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
OpenRun
OpenRun replaces the patchwork of CI/CD pipelines, reverse proxies, and identity providers that teams typically assemble when deploying internal tools, offering declarative GitOps-based deployment of web applications to Docker, Podman, or Kubernetes from a single self-hosted Go binary. Point it at a Git repository and it builds containers from AppSpec templates, routes requests by domain or URL path, provisions TLS certificates automatically, and scales idle applications to zero when unused. Blue-green staged deployments promote new versions through development, staging, and production environments with atomic rollback across multiple apps simultaneously. Every deployed application inherits SSO authentication through OAuth, OpenID Connect, or SAML providers alongside role-based access control, all configured once at the platform level rather than per app. Service bindings provision isolated PostgreSQL, MySQL, SQLite, or Redis credentials for each application, while Litestream integration replicates SQLite databases to S3 for automatic disaster recovery. The management console provides a web interface for monitoring containers, reviewing audit logs, configuring syncs, and managing server operations. AppSpec templates handle Streamlit, Gradio, FastAPI, Flask, and FastHTML projects out of the box, deploying existing Python applications without requiring custom Dockerfiles. 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.
Dolt
Dolt is a SQL database that versions your tables the way Git versions files, so every row carries a history you can branch, diff, merge, and roll back. The command line mirrors Git command for command: dolt init, add, commit, checkout, log, and blame operate on tables instead of files, and merges happen cell by cell, with conflicting cells landing in dolt_conflicts tables you resolve by choosing ours or theirs. Run dolt sql-server and the same database answers on the MySQL wire protocol, so the mysql client, TablePlus, DataGrip, and your existing application drivers connect unchanged, while stored procedures like DOLT_CHECKOUT and DOLT_MERGE and system tables like dolt_diff and dolt_log put version control inside SQL itself. Teams push and pull databases through remotes on DoltHub, S3, GCS, or a filesystem, fork a database to test a risky migration, and cherry-pick the good commits back. AI agents get their own branches to write into, and a human reviews the row-level diff before anything merges to main. Data publishers ship corrections as commits subscribers can pull, and analysts query any historical snapshot with AS OF instead of restoring backups. 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.
Gitness
With 37,400+ GitHub stars and active daily development by the Harness engineering team, Gitness is the open-source developer platform that ships Git hosting, container-native CI/CD pipelines, a Docker-compatible artifact registry, and cloud developer environments in a single Go binary consuming approximately 100 MB of RAM — compared to GitLab's 4+ GB minimum footprint. Born as the next generation of Drone CI, Gitness inherits Drone's battle-tested pipeline engine while adding complete source code management with pull requests featuring threaded code review comments, suggested changes, required reviewer approvals, and merge strategies including squash and rebase. Branch protection rules enforce mandatory pull requests, minimum peer reviews, passing status checks, and force-push blocking. Pipelines use Drone-compatible YAML syntax with stages, steps, and service containers, triggered automatically on code changes with results displayed directly in pull request checks. The built-in container registry eliminates the need for separate Harbor or Docker Registry deployments, supporting Docker image push and pull plus Helm chart storage. Gitspaces provide on-demand remote development environments configured via industry-standard devcontainer.json files. Encrypted secrets management with Gitleaks-powered secret scanning blocks commits containing hardcoded credentials. One-click migration imports existing GitHub Organizations and GitLab Groups, automatically converting GitHub Actions and GitLab CI pipelines to Gitness YAML. The REST API with OpenAPI specification enables programmatic management of all resources. 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.
Twigpine Node
Twigpine Node is a self-hosted git node that publishes repositories under cryptographic identities and replicates them across a peer-to-peer network. Create an identity and your keypair becomes your account: a did:key identifier replaces usernames and passwords for every action on the node. Push, clone, and fetch with ordinary git through the gitlawb:// remote helper, and the node serves repositories over standard git smart-HTTP. Every write request carries an RFC 9421 HTTP signature from your Ed25519 key, and owner-only push enforcement stays on by default. Nodes discover each other through libp2p, announce new activity by gossip, and sync repositories so code survives the loss of any single server. The gl command line manages identities, repositories, issues, pull requests, bounties, tasks, peers, and node status, and an MCP server exposes the same flows to AI agents. Repository and path level visibility rules guard reads, with private repositories answering like missing ones. Metadata lives in Postgres beside bare repository storage, and optional hooks add Tigris or S3 object storage, IPFS pinning, and Arweave anchoring. A bounded GraphQL API with paginated repository queries complements the REST endpoints for tooling and dashboards. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT and Apache-2.0 licensed.
Argo CD
A CNCF Graduated project with over 23,700 GitHub stars and adoption by organizations including Intuit, Adobe, Capital One, and Red Hat, Argo CD has become the industry standard for GitOps-based Kubernetes deployments since its creation at Intuit in 2018, treating Git repositories as the single source of truth for application configurations and automatically reconciling live cluster state with declared desired state. The platform supports Helm charts including Helm 4, Kustomize overlays, Jsonnet, and plain Kubernetes YAML manifests, rendering templates and applying resources through configurable sync policies with automated or manual reconciliation, pruning of orphaned resources, and self-healing that reverts unauthorized cluster changes. ApplicationSets enable templated generation of applications across multiple clusters, environments, and Git repositories using generators for pull requests, Git directories, cluster lists, and merge strategies. The web UI provides a real-time application topology view with resource health status, sync state indicators, log streaming, and a network view supporting Gateway API and Ingress visualization. Version 3.5 introduced mTLS for internal component communication, graduated user impersonation and source hydrator to beta, added native ApplicationSet management with preview applications in the UI, and delivered source integrity validation. Multi-cluster management deploys applications across development, staging, and production environments from a single Argo CD instance with RBAC, SSO via OIDC and SAML, and audit logging. 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.
CodeFever
Your team's code lives on someone else's server, under someone else's terms, until you decide it should not. CodeFever is a fully open-source, self-hosted Git hosting service that gives a small team unlimited repositories, branches and tags, merge requests, and branch protection on hardware as modest as one CPU core and a gigabyte of memory. Developers browse code with highlighted version comparisons, review changes through merge requests, and organize work with repository groups, member roles, and per-member permissions. Protected branches keep important history safe and make review the normal path to main, and webhooks connect pushes and merges to the other systems your team already runs. A super-admin backend manages every project and user on the instance, and the interface speaks Chinese and English natively. Installation is a single Docker command, updates preserve your data, and there are no repository counts, seat limits, or paid tiers waiting downstream. It suits a studio keeping client work private, a lab sharing models and notebooks, or a company that wants its source behind its own firewall. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
GitBucket
One downloadable WAR file gives your team a complete GitHub-style home for its code, with no per-seat bill and no repositories living on someone else's terms. You create public or private repositories and reach them over HTTP, HTTPS, or SSH, with Git LFS handling large binary assets alongside ordinary commits. The repository viewer includes an online file editor, so quick fixes and documentation tweaks happen in the browser without a local clone. Every repository carries its own issue tracker, pull request workflow, and wiki, keeping discussion, review, and project documentation next to the code they describe. Activity timelines and email notifications keep collaborators aware of new issues, comments, and merges as they happen. Administrators manage users and groups directly, connect account management to LDAP, and protect the instance with fine-grained repository visibility. A plug-in system extends the platform, and official plug-ins add gists, emoji, static Pages hosting, and richer notifications, while community plug-ins widen the menu further. Tools that already speak the GitHub API can point at your GitBucket instead, because its web API deliberately mirrors GitHub's. Upgrades stay simple: stop the process, replace the WAR, and restart with the same data directory. 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.
ghstats
GitHub forgets your traffic after fourteen days; ghstats remembers it for years. This self-hosted dashboard polls the GitHub API every hour and keeps views, clones, stars, forks, issues, and pull requests for every repository in its own database, long after the built-in traffic tab has rolled over. Open a repository to see its charts for stars, clones, and views next to top referrers and popular paths, filter the list by owner, name, forks, or archived status, and include private repositories when your token allows it. Public stats pages and portfolios reuse the same numbers through a JSON API, embeddable SVG badges for views, clones, and star velocity, and cards ranking your top repositories or showing star history across projects. Release download counts accumulate as daily snapshots too, so a launch spike stays visible months later. The whole service is one small Docker image on port 8080 with a single file for storage, easy to back up and easy to move. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Atlantis
Every Terraform change becomes a pull request with Atlantis, which runs the plan on your server, posts the output for review, and applies only the exact change reviewers approved. Open a pull request that touches Terraform code and Atlantis automatically runs terraform plan, posting the full output as a comment and a commit status your reviewers can inspect line by line. When the change looks right, a teammate comments atlantis apply and Atlantis executes the exact plan that was reviewed, then reports the result back on the same pull request. Each directory and workspace is locked while a pull request is open, preventing two changes from applying out of order, and locks can be inspected or discarded from the web interface. Apply requirements let you demand an approved review or a mergeable branch before anything runs, and optional policy checks evaluate plans against your rules before they can proceed. Repositories describe their projects, workspaces, and custom workflows in an atlantis.yaml file, including pinned Terraform versions, execution order groups, and parallel planning or applying across projects. Because Atlantis runs inside your infrastructure, cloud credentials never leave your network, and every plan, approval, and apply is preserved on the pull request as an audit trail. 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.
Codra
Your GitHub pull requests get reviewed by your own models, with inline findings posted in the merge flow: Codra is a self-hosted AI code review engine, so your diffs and credentials stay inside infrastructure you control. Connect a repository once and every opened, synchronized, ready-for-review, or reopened pull request starts a queued review job automatically; mention Codra for an on-demand pass instead. Findings arrive as inline GitHub comments, a summary review, and check run updates that fit the normal merge flow. Each repository gets its own review personality: triggers, skipped paths, draft handling, mention reviews, labels, custom rules, and a review budget are all tuned from the dashboard, and model routing follows global defaults, per-repository chains, fallbacks, and size-based overrides for larger pull requests. Providers from OpenAI, OpenRouter, Anthropic, Google, NVIDIA, and Cloudflare are managed behind GitHub OAuth sign-in. The operator dashboard tracks totals for reviews, input and output tokens, and comments posted, then drills into job history, webhook deliveries, failed queue runs, and model usage, so a stalled review is debuggable instead of invisible. Deploy the whole loop (GitHub App, web server, queue, database, and dashboard) on Cloudflare Workers, on Node.js 24, or with Docker on your own server. 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.
Octobox
What Gmail did for email, Octobox does for GitHub notifications: an ephemeral, unmanageable stream becomes an inbox you can actually triage. GitHub marks notifications read the moment you glance at them and lets old ones vanish days later; heavy maintainers end up building elaborate Gmail filter systems just to cope. Octobox - a Ruby on Rails app over PostgreSQL - syncs your notifications into a persistent inbox with an explicit archived state: mark a thread done, and if the issue or PR sees new activity, it pops back automatically, so nothing silently falls through. Triage is keyboard-driven with Gmail-style shortcuts (j/k to navigate, e to archive, m to mute, s to star), and multi-select clears noisy repositories in bulk. Filtering is where it earns its keep: slice by repository, organization, type, action, state, reason, CI status, labels, author, assignee, or bot origin, combine prefix search filters, and pin favorite searches to the sidebar. The optional GitHub App enriches entries with live PR/CI status and labels so you can decide without clicking through. Auto-archive rules clear merged PRs and closed issues; muting and snoozing silence the rest. A REST API supports integrations. Self-hosting keeps your notification metadata - a map of everything you work on - on your own server.
Single Server
Point it at your GitHub repos and every push goes live in under five seconds: one Linux box becomes the deployment platform for every app you have ever shipped, with no build queue, no per-app bills, and no pile of YAML. An interactive installer wires the box up once, creating a GitHub App for limited, revocable repo access, Cloudflare DNS records and a tunnel so visitors get TLS and CDN at the edge while your server IP stays hidden, and Tailscale access so you SSH in without exposing SSH to the public internet. From then on you just push: the daemon receives the webhook through a Tailscale Funnel, verifies its signature, fetches the commit, builds the image on the server from your Dockerfile or a generated one, and swaps traffic only after the new container passes its health check, so a failed deploy leaves the previous version serving. Each app runs in its own container with its own environment variables and persistent storage, and one CLI on the box handles the rest: add or remove apps, attach a domain in one command, roll back to an earlier commit, stream logs, check status, take backups, or run doctor to diagnose every layer from daemon to DNS. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Zoomies
Zoomies converts servers you already own into an ephemeral GitHub Actions runner fleet, creating a clean runner for every queued job and destroying it the moment that job ends. Why rent CI minutes by the second while those machines sit idle? Point it at a GitHub organisation or a repository on a personal account and it watches for queued work through workflow_job webhooks, with polling as a fallback, then provisions capacity only on hosts matching the labels your workflow requested. One controller drives any number of agents across Ubuntu, Debian, Fedora, and Rocky Linux on amd64 and arm64, and agents connect outbound only, so a host behind NAT needs no inbound firewall rule. Registration needs no pasted tokens: Zoomies signs in as a GitHub App and mints single-use just-in-time runner registrations itself. Busy runners can borrow idle CPU and memory from quieter neighbours under rules you set. The live web UI shows pools, jobs, queue waits, and streaming logs in place, with a command palette for jumping anywhere and an audit row recorded for every change. Nightly backups seal themselves with your passphrase and ship to S3-compatible storage, restores are staged from the same tab, and you can ask the built-in assistant about your builds or connect your own tools through MCP. 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.
Shep
Type one sentence about a feature, and Shep spins up an AI coding agent on its own branch and worktree, then carries the work through commit, push, CI, and a draft pull request. Run three features, five, or ten at once, with Claude Code, Codex, Copilot, Cursor, Gemini, Kimi Code, Cline, or local models picked per feature. A control center draws every repository and feature as a live graph with a fleet bar that counts what is cruising, queued, waiting on you, or failed. When an agent is unsure it asks a blocking question with a recommended answer and a deadline, and you reply from the web, the CLI, chat, or the terminal console. Optional spec-driven mode writes requirements, research, and a plan as YAML for you to approve before any code exists. CI watch reads failing logs and pushes fixes, a checkpoint follows every agent step so you can diff or restore it, and nothing merges without your approval. Tool pages, skills, plugins, webhooks, project memory, and per-feature chat round out the workspace, and an app starter plans a brand new project from a prompt. State stays in a local SQLite database, and usage metrics can be switched off. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
GitSave
A deleted account or a force-pushed branch should not erase your code history: GitSave copies your Git repositories to storage you control, on a schedule you set. Add a repository link, pick a routine (every few minutes, hours, or days), and GitSave copies the repository and refreshes the copy in the background. It works with GitHub, GitLab, and other Git platforms, and you decide how many backups to keep before older copies are pruned. Schedules can be paused and resumed from each repository card, and a Backup now action starts an immediate copy when you want one before a risky change. The history page records every run with its time and result, and the overview shows the last backup state of each repository at a glance. Backups can land on a local volume or an SMB share, and sign-in supports your own authentication provider for shared servers. 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.
Daily Stars Explorer
From a one-day Hacker News spike to a decade of steady growth, Daily Stars Explorer charts any GitHub repository's star history day by day, next to the releases and mentions that explain it. Type an owner and repository name, and daily and cumulative stars appear. Range shortcuts: 10Y, 5Y, YTD, QTD, MTD, and All. Zoom with a draggable lower navigator, switch to a Log Y axis, and read the stars gained inside the selected window. Transforms reshape the series. A trend line projects 30 days ahead. Yearly, monthly, or weekly grouping. Peak normalization. LOESS smoothing. Running average and median. First and second derivatives. Weekly growth rate. Feed overlays, enabled by optional provider credentials, mark releases and mentions from Hacker News, Reddit, GitHub, and YouTube right on the curve. Compare two already-fetched repositories on shared axes, with an aggregate selector, Log Y, and optional star milestones, then copy the link. With a GitHub token, separate pages chart commits, with the longest gap highlighted on demand, plus pull requests, issues, forks, and contributors. Global activity counts the public repositories or pull requests created on GitHub each day. Featured repos lists Hacker News and Reddit posts that link to GitHub projects, sortable by points, comments, or date. Star history, commit, and activity charts export to CSV or JSON. Favorite repositories can be pinned. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
GitArena
GitArena gives your team its own place to host code, combining repository hosting, issue tracking, and code review in one lightweight service you run yourself. Push and pull over HTTP or SSH, browse code in the browser with syntax highlighting, blame, and raw views, and follow commit history with diffs branch by branch. Repositories can be forked, archived, tagged, and released with downloadable assets, and every project gets an issue tracker with labels, milestones, assignees, and a kanban board. Issues are stored natively in Git using the git-bug format, so they travel with the repository and remain readable offline with the git-bug CLI. Merge requests collect changes for review before they land, while organizations and teams control who can see and change each project. Search spans code, repositories, issues, and users from one box, profiles show contribution graphs and activity, and sign-in supports passwords, SSH keys, passkeys, and OAuth single sign-on. A REST API exposes the platform to your own tooling, and the whole service runs from a single Docker Compose stack or a compiled binary with a separate frontend build. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.