NexusDesk is a self-hosted agent platform whose first complete application turns customer support conversations into retrieved answers, tool calls, and confirmed tickets on your own infrastructure. An agent takes a request, retrieves context from your knowledge base, decides what to do, calls business tools, asks a human to confirm consequential actions, executes, records everything, and feeds evaluation, all as one visible loop rather than a black-box chat. The Harness around that loop is the engineering control layer: it governs permissions and execution boundaries, manages agent memory, routes human handoffs, and keeps an audit trail, so autonomy stays inside lines you drew. You configure, publish, and roll back agents, manage documents, chunks, indexes, and published knowledge versions, and connect Chat, Embedding, Rerank, OCR, and speech models through versioned profiles. Business APIs plug in as tools with their own credentials, parameters, and permissions, and support staff can take over a conversation, draft a ticket from it, and confirm follow-up work without leaving the flow. Channels and application APIs with server-sent events expose the same capabilities to your other systems, while execution records, model and tool call logs, and evaluation results show what the agent actually did. One PostgreSQL handles storage, job queues, and cross-process messaging, and one Compose file starts the stack. 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.

Alertmanager forgets an alert the moment it resolves; Jarvis remembers everything. This web frontend watches all your Alertmanager clusters at once and streams firing alerts into one live view over WebSocket, no refresh as problems appear or clear. Every alert's lifecycle is stored, so the resolved view answers how often something fired and how long it burned, and a grace period keeps a missed poll from being recorded as a phantom resolution. When an alert lands, claim it so the team sees who is on it, and leave comments bound to that alert fingerprint; notes survive restarts and re-fires, so the next person inherits the context. Silencing gets a rehearsal: preview exactly which alerts a silence will hit before creating it, fire a one-click Fast-Silence from the list, and save templates for recurring maintenance. Filters use the Alertmanager matchers you already know, save as named sets, ride in shareable URLs, and one can be your default view. Point Jarvis at every member of an HA gossip cluster and duplicates collapse by fingerprint, while protected upstreams authenticate with OAuth2, bearer tokens or basic auth per cluster. Sign-in is optional through built-in accounts or any OIDC provider, and it runs as one hardened container on port 8080, with PostgreSQL available when you want replicas. Keep it behind your VPN or an authenticating proxy, as its own docs insist. 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.

Tell LearnBuddy what you want to learn, in one conversation, and it works out where to start, what to do each day, and when yesterday's material needs another look. You describe the goal, whether that is a language, programming, nutrition, writing, or a career change, and three to five adaptive questions measure your actual baseline instead of making you pick a level from a dropdown. From there it builds a personalized path of four to twenty-four weeks and tells you daily what to study and what to review, so opening the app answers the question instead of raising it. Forgetting is treated as a scheduling problem: reviews resurface at spaced intervals, weekly self-checks test whether the plan still fits, and the roadmap replans dynamically when you race ahead or fall behind. Two editions run from the same codebase: try the hosted Cloud experience, or settle into Personal mode with your own model API key and your learning data stored on your own server. Optional OpenClaw and Feishu integration can bring the daily guidance into the chat tools you already live in. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Saki Panel is a self-hosted operations console that manages your game servers, containers, and background processes across multiple Linux machines, with an AI assistant sitting inside the workspace when something breaks. Start, stop, restart, and monitor nine kinds of instances, from Minecraft and Steam game servers to Docker containers, Compose stacks, Node and Python apps, and plain shell commands. Remote nodes connect over SSH and report CPU, memory, and disk metrics to a cluster dashboard, so every machine is visible in one place. When an instance crashes, Saki Watch records the exit and its error fingerprint, then helps diagnose the cause from live logs, files, and metrics instead of making you copy text between a terminal and a chat window. Proposed fixes appear as diffs that need your approval, are graded by risk level, and can roll back automatically if verification fails after a patch. Day to day work happens in the same console: a web terminal, a file manager with an editor and archive support, database tools for SQLite, MySQL, PostgreSQL, and Redis, and cron-scheduled tasks with full run history. Role-based access with dozens of permission codes, audit logs, and incident notifications through webhooks or Telegram keep a small team in control. 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.

Email discussion lists - the venerable listserv pattern where one address relays to a whole group - without the notorious setup pain of Mailman or Sympa: that is Gray Duck Mail. Its architectural trick is requiring no mail server of your own: the C#/ASP.NET Core app monitors a POP3 inbox at any external email host supporting POP3/SMTP and aliasing, relays each incoming message to all list members via SMTP, and archives it for browsing in the web interface. Replies route back to the entire group automatically. The tedious parts of list management are handled by convention: dedicated aliases process join requests, subscription confirmations, and unsubscribes, while a bounce alias in the return-path catches delivery failures so dead addresses get handled instead of silently rotting. The web administration interface creates and removes lists, manages contacts, browses message archives, and imports or exports the local database for backup. GPLv3-licensed, Docker-distributed, and fully code-documented, it targets exactly the groups email still serves best - neighborhoods, schools, congregations, workplaces, and families - where one message keeping everyone in the loop beats yet another app nobody wants to install.

Codex LB Enhanced is a session-aware gateway that pools your ChatGPT accounts so a long Codex session survives quota limits, dropped connections, and paused accounts without losing the conversation. It serves Codex desktop, CLI, and IDE clients through the native Responses protocol and WebSocket transport, and answers any OpenAI-compatible client through the familiar /v1 endpoints. When an account runs out of quota, gets suspended, times out, or drops mid-stream, the gateway classifies the failure, removes that account from the current request, and selects the next one through your load-balancing policy. Verified request history, including interrupted tool-call context, is replayed across the account switch when it is safe, so the client sees a slower answer instead of a dead stream. Every API key carries its own policy: time windows from five hours to monthly, limits by credits, tokens, or cost, and model-specific rules. Usage appears in native Codex quota headers and in a /v1/usage view backed by the same data, so editors and automation agree on what is left. Diagnostics correlate each request with its upstream account, transport, failover stage, and retry count, and a web dashboard manages accounts, keys, usage windows, request logs, and recovery reports. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

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.

BlogFactory is the first open-source agent control plane purpose-built for multi-site content operations, shipping 16 distinct capabilities across four operational pillars — Operate, Grow, Control, and Deliver — in its v0.1.0 release. The platform keeps source evidence, AI-generated drafts, revisions, SEO metadata, human review, preflight checks, and CMS delivery destinations in one workspace while enforcing a server-side authority ceiling that prevents agents from ever publishing live content, accessing credentials, or performing administrative actions. AI agents connect through a Streamable HTTP MCP endpoint with OAuth authentication and site-scoped tool discovery, compatible with Codex, ChatGPT, and any MCP-capable client. Content creation supports single articles from keywords, titles, URLs, PDFs, text, or YouTube sources, batch campaigns, and programmatic content via reusable templates with structured data rows. The Search Growth module connects Google Search Console complete-day data to ranked optimization opportunities, 30-day growth plans, content classification by signal type (growing, low-CTR, almost-ranking, page-two, zero-click), indexing checks, and semantic internal-link suggestions. Brand Voice separates global voice rules, writer profiles, knowledge context, and brand guidelines from article mechanics. Approved drafts are delivered as CMS drafts to WordPress, Ghost, Wix, or Framer through idempotent, optimistic-locking-protected handoffs with explicit destination selection and preflight validation. The stack runs on React/Vite, a Hono/TypeScript API, PostgreSQL, and MinIO via Docker Compose, with providers including OpenRouter, OpenAI, and Google services under a bring-your-own-AI model. 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.

PandaDOS is a self-hosted control plane that turns Claude Code and Codex into long-running coding agents you direct through an issue queue from any browser, instead of babysitting a terminal. You file an issue with the outcome and acceptance criteria, and PandaDOS clarifies missing requirements, plans the work, picks the agent, and drives implementation, verification, and delivery in stages. Three approval levels, cautious, balanced, and automatic, decide which actions proceed alone; safe reversible steps continue automatically while destructive, irreversible, production, or secret-related decisions always come back to you. The browser workspace shows the real agent conversation, a native terminal, project files, Git history and diffs, and an execution summary, so you can inspect or intervene at any moment from a phone or laptop. Agents run on local or SSH-connected executor machines inside tmux sessions, and work sharing one repository is serialized while independent projects proceed in parallel without conflicting edits. Modules keep one assigned agent and durable project knowledge, so context from finished issues carries into the next task instead of evaporating when a chat ends. Teams can sign in through Feishu, ask the project manager questions in chat, and receive subscription notifications and approval cards on their phones. 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.

Which agent should answer a question that just arrived in your QQ group, and how much of the conversation should it see? RabiRoute is the self-hosted message gateway that answers those routing questions before your agent ever wakes up. Chat messages from QQ groups and direct chats (through NapCat and OneBot), webhooks, schedules, voice, desktop selections, and device events all arrive at one gateway, and message Routes decide which agent or local program receives each one. Every role keeps its own message history plus references to plans, memories, and skills, while each Route limits how many recent messages travel with a delivery. Roles can also fire agents on interval, time-window, daily, or one-time schedules, or run a configured local script, so recurring checks and reports happen without anyone typing a prompt. Replies to QQ, RabiLink, and other channels leave through a single sending API that validates targets, quoted messages, and sender identity, then records receipts for everything delivered. The Windows desktop side adds selected-text actions, screenshots, and annotations; speech, phone, glasses, wearable, and remote-computer clients connect as experimental integrations, and the Linux Host serves the Manager and browser WebGUI from a Node.js process. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.