2383 applications
Omnibus screenshot thumbnail

Omnibus

Omnibus runs your whole comic habit from one shelf: discover a series, request the missing issues, and read them in the browser when they land. Discovery starts with ComicVine or Metron metadata (high-resolution covers, synopses, and creator credits) and a release calendar that flags what you own and what is still missing across your monitored series. Requests are one click for a single issue or a whole run; Omnibus searches your indexers, hands the release to qBittorrent or SABnzbd, then imports, renames, and shelves the file with metadata embedded into the archive itself. Loose files that match nothing meet the Smart Matcher, which proposes the right series and applies every confident match in one pass. The built-in reader opens CBZ, natively read CBR and EPUB files in left-to-right, right-to-left manga, or continuous webtoon modes, with double-page spreads, brightness and contrast controls, page preloading, and preferences remembered per series; an offline button caches a full issue for the road. Reading lists assemble themselves from a pasted event ID or arrive by import from CBL files, League of Comic Geeks CSVs, AniList, or MyAnimeList, always showing how far through them you are. Everyone gets their own account, reading progress, follows, and an Updates feed, while OPDS, KOReader sync, and a Komga-compatible endpoint feed Panels, Mihon, and Paperback on the side. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
VolumeVault screenshot thumbnail

VolumeVault

VolumeVault turns Docker volume backups into a routine you can prove: it schedules them, stores them off the box, and restores them into brand-new volumes so original data is never the test subject. A guided web dashboard discovers every Docker volume on the host and shows backup coverage per volume or per Compose and Swarm stack, including the size of the latest known backup, so gaps are visible before they matter. Each job runs on an hourly, daily, weekly or cron schedule with retention by days or archive count, include and exclude filters, and a choice of whether containers stop during the run. Archives land where you keep them: AWS S3, Cloudflare R2, any S3-compatible store, WebDAV, SFTP, Azure Blob, Dropbox, Google Drive or a local path, with credentials encrypted at rest. Restores download and verify the archive first, then unpack it into a new volume by default; overwriting the original demands an explicit confirmation. Several volumes can ride one grouped schedule that reports once for the whole set, and containers can volunteer themselves for backup through Docker labels. Small agent containers extend the same jobs to other Docker hosts, including encrypted cross-host restores into fresh volumes, while API tokens let scripts and dashboards drive everything the UI can. 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.

Deploy
Lurker screenshot thumbnail

Lurker

Lurker keeps you present in every IRC channel you care about, holding your connections open around the clock and recording everything said so a retro, searchable web client can hand it all back whenever you return. Invite your friends and each person gets their own set of networks under one roof, while admins decide which networks members may join and which channels newcomers are pointed at. Nothing said while you were away is lost: the full history is searchable by nick, channel or network, and clicking a result jumps straight to that moment, whether it happened an hour or a year ago. The everyday annoyances are handled too, with drafts that follow you between devices, a highlight and ignore system that cuts noise, bookmarks and private notes on users, reactions, replies, and image uploads that are optimized, stripped of metadata and stored on your own disk or S3. If you prefer your old client, the built-in bouncer speaks the soju and ZNC dialects with SASL, network discovery, on-demand scrollback and read markers that stay in sync everywhere, and DCC file transfers with an XDCC queue still work. Optional companion containers generate inline link previews in isolation and keep your IRC connections alive across restarts of the main service. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MPL-2.0 licensed.

Deploy
InfraCanvas screenshot thumbnail

InfraCanvas

InfraCanvas draws the picture ten terminal commands cannot: a live map in your browser of every container, pod, service, volume and network on a machine, showing what runs where, what talks to what, and what is broken in one glance. Nodes turn green, amber or red from real state, including container health, pod phases, ready replicas, zombie processes and host thresholds, and real connection edges appear between processes, like your app server talking to Postgres on port 5432, read straight from the machine. It works where workloads already live: Docker and Podman containers, full Kubernetes object graphs from nodes to ingresses, LXD and Incus containers, and plain systemd or PM2 services on VMs with no container runtime. From any node you can shell into the container, pod or host, tail logs, restart or stop a service, scale a deployment, run a rolling restart, change an image or kill a process, with secrets masked before anything reaches the screen. A second machine joins through an outbound-only agent, and clusters connect by dropping in a kubeconfig with nothing installed inside them. The self-hosted binary needs no account, sends no telemetry and opens no inbound port: it binds localhost on port 7777 behind a random per-install token, with an optional read-only mode, and every action is audit-logged. 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.

Deploy
Jarvis screenshot thumbnail

Jarvis

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.

Deploy
Docker Updater screenshot thumbnail

Docker Updater

Docker Updater puts you back in charge of container updates: it watches your registries for newer images, and nothing updates until you approve it, so no database restarts itself at dinner. Polls run on a schedule you set, and each container card shows the newer image waiting before anything is pulled. The check costs nothing: it compares the digest your container runs against the registry manifest without pulling a byte, across Docker Hub, GHCR and other Bearer-token registries. Read the last five GitHub releases for an image before committing, update one container or a batch, and watch the pull percentage, layer count and recreation step stream live on the card. If the new container fails to start, the old one returns automatically, and you can keep a backup even after a clean update. Not ready? Defer an update for 7, 14, 30 or 90 days, or indefinitely, and it leaves your notifications alone until then. Several Docker hosts join the same dashboard over SSH or TCP with health indicators, and Compose stacks restart together so services find new addresses. Notifications arrive through an auto-generated ntfy topic or your own Apprise URL, every update keeps a persistent log, and a reclaimable-images view shows what disk space old images hold. The dashboard serves on port 9090 in English or Simplified Chinese, with optional login. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Runwisp screenshot thumbnail

Runwisp

Cron ran the job, or maybe it did not; Runwisp makes the answer impossible to miss. One small binary replaces both crond and your process supervisor: list scheduled jobs and long-running services in a single runwisp.toml, and it runs the jobs on time, restarts services when they crash, and keeps every line they print. Every run leaves evidence: exit code, duration, timestamps and full stdout and stderr, searchable across a task's whole history, with CPU and memory shown next to what that task usually uses. When a run fails, the dashboard shows why, with stderr and the end reason beside the retry button, and alerts head to Slack, Discord, Telegram, ntfy, Gotify, Pushover, email or a webhook before you find out the hard way. Missed runs catch up after downtime, overlapping runs queue, skip or kill by policy, and services get restart backoff and graceful shutdown. Manual runs take typed parameters, so the dashboard generates a form with choices and defaults from your config. Long output streams live with progress bars redrawing in place, and the same history opens in a terminal UI over SSH. The config file stays the source of truth: interfaces trigger and inspect, they never edit your TOML. No database to run, no runtime to install, just the binary and its embedded storage. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
Zimi screenshot thumbnail

Zimi

When the internet goes away, your library does not have to: Zimi serves Kiwix ZIM archives of Wikipedia, books, videos and forums through a rich web interface, with one search box querying every archive across more than 100 million articles. Each content type gets its own app: Zimipedia for wikis, the Dictionary for Wiktionary, Bookshelf for books, ZimiTube for video, ZimiExchange for Q&A, Reddot for subreddits and offline street Maps. Bookmarks, lists, likes and highlights live in every app and sync across devices when you sign in, and any article can switch into whichever language edition you hold. The library manages itself: browse the Kiwix catalog of over 1,000 archives, download with one click, let auto-updates keep editions fresh, and seed downloads over BitTorrent with a ratio cap you set. Zimi servers on the same network find each other and pass archives at LAN speed, and one offline switch turns off every internet-bound feature for air-gapped rooms. You can also make your own ZIMs from a web page, a whole site, a video playlist or a folder of files. Access ranges from public to sign-in only with per-archive allowlists, and the JSON API plus MCP server let AI agents search the same library. Docker runs Zimi on port 8899 with your ZIM files and config mounted as volumes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
Ether screenshot thumbnail

Ether

One Ether install puts the TMDB catalogue inside your TV apps and streams titles on demand from your own accounts, holding no media files at all. It appears as a normal server inside the Plex, Jellyfin, Emby, Infuse and Stremio apps your household uses, with the whole catalogue browsable as if it were local. Press Play and Ether resolves the best release across your sources, health checks it, and streams only the byte ranges the player asks for, so scrubbing lands at the right keyframe instead of restarting a download. Pull titles from Real-Debrid, TorBox, AllDebrid and Premiumize accounts, Usenet providers through a built-in Newznab and Torznab manager, Cardigann definitions, or Stremio stream addons pasted in as sources. Released titles need no request queue: each viewer's Plex and Trakt watchlists sync in, and newly playable titles surface in a Now Available row on their home screen. A poster studio renders 4K, Dolby Vision, Atmos and rating badges onto artwork in the browser, and rule-based collections can run as 24/7 virtual channels in the Live TV guide. Subtitles arrive matched and retimed to the cut playing, with skip markers. A self-evicting cache keeps replays instant and preloads the next episode as you watch. Local playback needs no Plex Pass, and Docker runs Ether on port 32400 beside your library rather than replacing it. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Deploy
Romarr screenshot thumbnail

Romarr

Name a game and Romarr goes and finds a copy you can prove is good. Search every indexer at once, through Prowlarr or directly, and each release comes back scored with the reasons written out: seeders, the right region, a plausible size, points off for hacks, betas, and repacks. The winner goes to whichever client speaks its protocol, from thirteen torrent daemons and eight debrid services to SABnzbd or a plain watched folder, and within a minute of finishing, the ROM itself is picked out of its archive, multi-track discs kept together as a set. Then comes the part no other library manager does: every import is checksummed against your No-Intro and Redump DATs and stamped verified, bad dump, or unknown. A verified dump is byte-for-byte the published one, a bad dump is refused unless you force it, and homebrew or translations import without ceremony as unknown. A verified copy automatically upgrades an unverified one, collections compare against a DAT to show exactly what you are missing, and duplicates are audited before anything moves. Finished games land in RomM, Gaseous, Retrom, or a simple folder, routed per platform, and your library server is told to rescan so the game appears with its art. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
MirrorProxy screenshot thumbnail

MirrorProxy

Stop hunting for a public mirror that still works this week: MirrorProxy puts every software source your builds depend on behind one domain you control, so GitHub releases, container images, npm and PyPI packages, and operating-system repositories all come from the same stable gateway. Point it at a source and it fetches and caches on demand, with no full mirror to store or sync, and when an upstream times out or starts rate-limiting, it fails over to the next endpoint and keeps your builds moving. Around thirty adapter types cover the everyday sprawl: Docker Hub and nine other registries, Cargo and Go modules, Maven and NuGet, Homebrew and WinGet, and more than thirty Linux and BSD distributions, plus custom static repositories you define yourself. Sharing the gateway is safe: invite users, set monthly quotas per person or team, restrict which sources each team may use, and gate access with rate limits and IP rules, while the console shows traffic trends, visitor regions, cache behavior, and the health of every source. Email and webhook alerts warn you before a quota runs out or an upstream outage drags on, and the cross-platform client switches a workstation's sources to your gateway and back. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
BankMCP screenshot thumbnail

BankMCP

Ask your assistant what you spent on groceries last month, and let it answer from your actual bank accounts instead of a spreadsheet you never update. BankMCP is a small server you run yourself that connects your European banks to Claude, ChatGPT, Cursor, or any MCP client, so questions about balances and spending get real answers. Ask for a balance and it fetches the booked and available figures live; ask where the money went and it searches transactions across every connected account by merchant or invoice number; ask for the month and it totals money in and out while leaving transfers between your own accounts out of the picture. Background watches keep an eye out between conversations: get a webhook when a balance crosses a line, a large debit lands, a named payment arrives, or an expected payment has not shown up by its date. Ready-made prompts cover connecting a bank, building a budget, scanning savings, auditing subscriptions, and spotting unusual transactions. The server is deliberately boring about your data: it keeps consents, account labels, watches, and your login, fetches balances and transactions only when asked, and stores none of them. It is read-only by design, with no payment tools to abuse. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
PhreshOS screenshot thumbnail

PhreshOS

Your server already runs your apps; PhreshOS gives it a desktop. Install the System once and every Program you add gets a window on a real browser desktop, complete with taskbar, start menu, and a plane of views you can spread work across. Close the browser and nothing stops: each Program's server keeps running on the machine, holding its data and state, and when you open the Desktop again the windows are exactly where you left them. The System handles the groundwork every small web tool normally rebuilds for itself: one sign-in for the owner, permissions that decide what each Program may reach, storage and uploads, logs, and messaging between Programs, so a new tool only brings its own logic. Everyday pieces like the file manager, Settings, and even the wallpaper are Programs too, and an appearance changes colors and motion across the whole desktop at once. The same Desktop opens in several browsers simultaneously, each with its own view and scale, and AI agents work alongside you through the same Programs and APIs you use. When you want another tool, you create it as a small web project and its window appears on your desktop. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
FoxProfile screenshot thumbnail

FoxProfile

Every account you run deserves its own browser identity, and FoxProfile keeps those identities permanently separate instead of letting them bleed into one another. Create a profile once and it remembers its device: screen, GPU, CPU cores, fonts, and canvas noise are generated on first launch and reused on every later one, so the fingerprint a site saw yesterday is the fingerprint it sees tomorrow. Sessions stick too: history, cookies, and logins live in the profile directory, and the tabs you left open reopen where you left them. Each profile carries its own proxy (HTTP, HTTPS, SOCKS4, or SOCKS5, with a built-in checker) while timezone and locale follow the exit IP automatically or stay pinned to your choice, and the Check IP button compares the exit address across three services and flags mismatches or datacenter addresses. Cookies move in and out as standard editor JSON or Netscape files, whole profiles travel as ZIP archives, and bulk actions launch, stop, or delete fleets at once. On a server, the web panel runs profiles headlessly so you can manage them and view their screens from anywhere, the REST API scripts everything, and the MCP server lets AI agents drive the browsers directly. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Roamgate screenshot thumbnail

Roamgate

Close the laptop, keep the agents: Roamgate brings the Herdr workspace running on your server into any browser, so the terminal session you left mid-task is waiting on your phone exactly as you left it. Every workspace and recognized agent sits in one view: check what each agent is doing, read its conversation, and take over a real terminal with streaming output, split panes, scrollback, multiline paste, and clickable links. When the agent finishes, the review happens in the same place: inspect staged, unstaged, untracked, and branch changes, annotate exact diff lines, preview rendered Markdown, and send compiled feedback back into the agent pane without pre-filling a submission you did not approve. Files browse beside the terminals, and session history survives disconnects because Herdr owns the sessions, not your browser tab. Connections stay flexible: run the bridge beside Herdr on one machine, save SSH profiles to reach remote hosts, and install the whole thing as a PWA for an app window without tabs. Login is required even on loopback, push notifications flag agents waiting for input, and themes, accents, and terminal fonts make the cockpit yours. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
LearnBuddy screenshot thumbnail

LearnBuddy

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.

Deploy
EcomGen screenshot thumbnail

EcomGen

Your next product listing does not need a photo studio, because EcomGen turns the product facts and photos you already have into a complete image suite you approve shot by shot. Each product becomes a project that remembers its verified facts, banned claims, brand rules, target market, and platform requirements, so generation starts from what is true about the item rather than a fresh guess every time. An agent reads the template library and drafts a storyboard with a role for every image: hero, pain point, comparison, scene, detail, trust, variant, and conversion, and you edit and confirm each final prompt before anything renders. Twenty-five built-in templates and more than 1,100 reusable suites across 24 top-level categories keep a catalog visually consistent, and the Suite Forge can reverse-engineer a winning competitor set into a reusable template of your own. Product-truth pixel protection keeps the real item intact instead of letting the model improvise a different product. Finished shots can be masked, repainted, outpainted, and split into editable PNG and PSD layers, reviewed one by one, then exported as a ZIP with a manifest, while the model library keeps virtual models consistent across poses and scenes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Astrum Repository screenshot thumbnail

Astrum Repository

One server can hold every package your builds pull, publish, and cache, so the team stops juggling a different registry for every language. Astrum Repository hosts your own artifacts, proxies public registries so builds keep working when an upstream is down, and groups both behind a single address your tools already understand. Thirty-nine formats share that address: Docker and OCI images, Maven, npm, PyPI, Cargo, Go modules, Helm charts, NuGet, Terraform modules, APT and Yum packages, Hugging Face models, browser extensions, Git LFS, and even remote caches for Nx and Turborepo. Blob storage grows with you, moving between disk, S3, and agent-connected stores that combine into groups without relocating data. Access stays deliberate through users, roles, privileges, and content selectors, with LDAP and OpenID Connect sign-in and access tokens minted for CI pipelines. Day-to-day operations are visible rather than guessed: health endpoints, Prometheus metrics, scheduled tasks, cleanup policies, audit trails, and backups are built in, and several servers can share one database when a single node is no longer enough. The web interface speaks twelve languages, so a platform team spread across regions still works in one console. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy