zrok puts services that live behind NAT and firewalls onto the public internet with a shareable URL, without opening a single inbound port. The machine being shared dials out to an OpenZiti overlay network, so a web app on your desk, a Raspberry Pi at home, or a staging box inside a corporate network becomes reachable through your instance while its firewall stays closed. One command shares an HTTP service publicly; add a name from one of your namespaces and the URL stays stable even when you move the backend to a different machine, and an ephemeral name can be promoted to a reserved one when a quick demo turns into a keeper. Private shares skip the public internet entirely and reach only the users you grant, including raw TCP and UDP services, while web and drive backend modes publish static sites or whole folders, with OAuth, password auth, and an interstitial warning page available on public shares. The long-running agent keeps every share and access under one process, restarts the named ones after a reboot, and offers a localhost console for point-and-click sharing; the account-wide web console maps your environments, shares, and accesses as a navigable graph or a sortable table with live activity. Operators get invite-based accounts, InfluxDB-backed usage metrics, and configurable limits that warn or cut off accounts that exceed their quotas. 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.

Every page in a DokuWiki knowledge base is just a plain text file on disk, so a team wiki can run for years on modest hardware with no database to feed, ever. Writers edit pages in a clean, readable syntax, fix just one section of a long document at a time, and lean on the toolbar, breadcrumbs, automatic tables of contents, and conflict locking to keep collaboration painless. Every change is kept as a revision with colored side-by-side diffs, recent-changes feeds go out over RSS, and an index-based full-text search finds content across thousands of pages in milliseconds. Namespaces organize content into a browsable tree, while built-in access control lists decide per page or per branch who may read, edit, upload, or administer, with logins checked against LDAP and other backends. Media uploads embed straight into pages, configuration happens in the browser, and the whole installation backs up by copying a folder, which makes migrations and disaster recovery almost boringly simple. When the basics stop being enough, more than twelve hundred community plugins and a hundred templates add galleries, multilingual structures, diagrams, and data tables without changing how the wiki itself works. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0 licensed.

Page views, referrers, browsers, and screen sizes - Ackee delivers the analytics developers actually check, from a deliberately minimal Node.js and MongoDB stack that skips both Matomo's weight and Google Analytics' cloud dependency. Its defining constraint is anonymization: no cookies, no unique user tracking, and a multi-step anonymization process that keeps visitors unidentifiable while the aggregate numbers stay useful. In its default anonymous mode Ackee collects no personally identifiable information at all, which means GDPR and CCPA compliance out of the box and no cookie consent banner on your sites. A detailed mode adds screen size, language, and per-visit referrers - still without cookies or fingerprinting. Integration mirrors the Google Analytics pattern: create a domain in settings, drop the generated ackee-tracker snippet into your pages, and data appears in a clean single-page dashboard. One instance tracks multiple domains, and custom events capture button clicks, signups, and conversions. The distinctive engineering choice is the fully documented GraphQL API: everything the dashboard shows comes from that API, so you can query active visitors, average duration, and view statistics programmatically, feed data in from apps and services beyond websites, or build an entirely custom interface on top. If you want bare-minimum analytics with a real API and zero privacy anxiety, this is the tool.

jshERP lets a small or midsize business, from a shop to a wholesaler, run purchasing, stock, sales, and money from one place instead of scattered spreadsheets. A purchase requisition becomes a purchase order, then a receipt that raises stock. A sales order becomes an outbound delivery that lowers it, or a purchase order when more must be bought in. Retail sales, returns, and serial-number scanning run through the same stock. Products sit in a category tree up to three levels deep, with barcodes, images, multiple attributes, customer-specific prices, and a base unit plus up to three secondary units. Transfers move goods between warehouses, assembly and disassembly merge and split products, and shelf locations record where each item sits. Other receipts and issues cover opening stock, stocktake corrections, and scrapped goods, while moving-average cost keeps valuation current. Finance logs income, expenses, receipts, payments, transfers, and prepayments against settlement accounts, and customer and supplier reconciliation reports export to Excel. Reports track stock levels, low-stock alerts, in-out statistics, and purchase and sales summaries, and the home page totals yesterday's and retail sales. Roles limit access down to single menus and buttons and can mask prices. A tenant model runs several businesses on one installation, and the interface switches among 73 languages. 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.

Consolidate fragmented collections of digital novels, graphic novels, manga, and audiobooks into Grimmory, an open-source media library server that combines automated file sorting with rich in-browser reading environments. The server indexes diverse media formats including EPUB, MOBI, AZW3, FB2, PDF, CBZ, CBR, CB7, M4B, and MP3 files across isolated storage directories. Readers explore literature through specialized browser viewports that provide customizable typography, CFI highlight annotations, two-page comic spreads with right-to-left manga modes, and chapter-based audiobook playback with sleep timers. Automated BookDrop watch folders ingest incoming files, retrieving book covers, author biographies, and community ratings from Google Books, Open Library, and Amazon APIs. Dynamic Magic Shelves organize catalogs automatically using nested boolean rule trees that filter books by page counts, genres, release dates, or narrator identities without server reload overhead. External e-readers access media catalogs through standard OPDS feeds or native Kobo and KOReader synchronization endpoints that match documents by binary content hashes. Built-in email delivery sends formatted books directly to Kindle devices with a single click, while OpenID Connect authentication enforces granular multi-user library permissions. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GNU AGPLv3 licensed.

Cerbos decouples authorization logic from application code entirely, evaluating human-readable YAML policies in under one millisecond through a stateless Policy Decision Point that requires no application state synchronization or cross-network fan-out. Its custom decision engine benchmarks up to 17x faster than OPA-based alternatives. Access control policies use conditions expressed in Google's Common Expression Language, supporting role-based, attribute-based, and policy-based access control patterns including derived roles, scoped policies, and permissions-aware data filtering that pushes authorization predicates directly into database queries. The PDP exposes both gRPC and HTTP APIs with SDKs for JavaScript, Python, Go, Java, .NET, Rust, PHP, and Ruby, making integration a single function call regardless of tech stack. GitOps-native workflows treat policies as code with Git versioning, CI validation through GitHub Actions, coverage reports, breaking-change detection, and audit logs of every authorization decision for ISO27001, SOC2, and HIPAA compliance. Deployment flexibility spans Kubernetes sidecars, standalone services, systemd daemons, AWS Lambda functions, and WebAssembly-embedded PDPs that run authorization logic directly in browsers, serverless architectures, and edge devices. The Admin API manages policy lifecycle operations programmatically, while the built-in Playground and REPL provide interactive testing environments for policy authoring and debugging. 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.

pRESTd points at your PostgreSQL or MySQL database and instantly serves every table as a REST API, so the CRUD backend you were about to spend a week writing already exists. Every table answers at its own address with filtering, ordering, pagination, and column selection in the query string, and batch endpoints group several operations into one call. When a table endpoint is not enough, drop a SQL file into the queries folder and it becomes a named route with bound parameters, or store the scripts in the database and manage them through the admin API. Turn on the auth module and the server issues JWTs from your own users table, checks them on every route, and enforces table-level permissions so public tables stay open while payroll stays shut. The same database also appears as a read-only MCP endpoint, which lets Claude, Cursor, and other AI clients discover your tables and query them with your permissions instead of a copied export. One process can front several databases at once, Postgres and MySQL side by side, each under its own alias for tenants or reporting replicas. An embedded Studio in the same binary browses the catalog and rows, builds GET requests, and invokes MCP tools, so you can inspect everything from the browser before writing a line of client code. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Unlimited agents, unlimited tickets, unlimited mailboxes, forever, on a $4 VPS - FreeScout's pricing inversion is why it became the most popular self-hosted Help Scout alternative, a PHP/Laravel help desk and shared inbox developed from scratch over eight years. The inbox deliberately behaves like Gmail or Outlook, so new support agents need close to zero training. The email-support core is genuinely complete: seamless IMAP/SMTP integration including modern Microsoft Exchange authentication, collision detection that warns when two agents open the same conversation, canned responses, auto-replies, internal notes, open tracking, starring, forwarding, merging, and moving conversations between mailboxes, phone-call logging, push notifications, and an auto-refreshing conversation list - plus screenshot pasting straight from the clipboard into replies. It's 100% mobile-friendly, fully screen-reader accessible, and translated into 28 languages. Beyond the core, an ecosystem of 100+ modules (mostly one-time $12-20 purchases) adds knowledge base, workflows with Gmail-filter-style automation rules, satisfaction ratings, time tracking, tags, custom fields, LDAP, Slack, WhatsApp and Telegram channels, and an API with webhooks - pay only for what your team needs. Web installer and updater included. AGPL-licensed.

A video too large for Discord, a secret that should not live in a chat log, or a config file a headless server needs to fetch: MicroBin turns each into a short link with an animal name, served from your own machine. Paste text or code and it comes back with syntax highlighting, inline image and video embedding, and a QR code for moving it to a phone. Attach one file or several, then decide exactly who can see them: uploads can be public or private, editable or locked, set to expire on a schedule or to never expire. For sensitive material, server-side encryption and client-side end-to-end encryption keep contents unreadable without the password. Raw serving hands the plain bytes to curl, a browser, or another program, which makes the same box a tiny file endpoint for scripts and test rigs. A postbox mode lets people send you files and texts they cannot browse or delete afterwards, and a read-only mode with an uploader password turns the instance into a drop point with exactly one trusted sender. The admin console lists uploads and storage, and everything runs as one small binary backed by SQLite or a JSON file, comfortable in a few megabytes of memory. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. BSD-3-Clause licensed.

To explore years of personal music streaming habits without waiting for an annual year-end summary, Your Spotify continuously tracks your listening history and presents it inside a private analytics dashboard. Music enthusiasts use the interface to inspect daily, weekly, monthly, and custom date-range breakdowns of their most played tracks, top artists, favorite albums, and total listening duration. Listeners who want their complete historical archive from day one can upload official Spotify privacy data exports, including both past-year StreamingHistory JSON files and multi-year Extended Streaming History archives, directly through the settings panel. Friends and family sharing an instance can use the collaborative affinity view to compare overlapping listening habits across multiple accounts in intersection or union mode. From any historical table, top-tracks ranking, or multi-user affinity comparison, you can generate new playlists directly inside your Spotify account or trigger track playback on active devices. Administrators can manage user registrations, generate shareable public guest tokens for read-only dashboard access, blacklist specific artists from skewing statistics, and expose ingestion metrics to Prometheus. 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.

With over 3,700 GitHub stars and growing adoption among teams tired of managing complex orchestration platforms, Dagu delivers a complete workflow engine as a single Go binary that requires no external database, message broker, or framework installation. Define directed acyclic graphs in declarative YAML — specifying dependencies, schedules, retries, timeouts, approvals, and notifications — while keeping existing shell scripts, containers, and tools completely unchanged. The built-in Web UI provides live pipeline visualization, per-step log streaming, run history browsing, artifact previewing, manual retry controls, and workflow YAML editing without SSHing into servers. Execute steps as shell commands, Docker containers, Kubernetes Jobs, SSH remote commands, SQL queries, or HTTP requests, with conditional branching and parallel execution handled natively. The integrated Model Context Protocol server exposes dagu_read, dagu_change, and dagu_execute tools, enabling AI agents like Claude, Codex, and Cursor to inspect workflow state, preview YAML modifications, and control runs through authenticated endpoints. The harness.run executor lets external coding-agent CLIs operate inside DAG steps with full scheduling and approval gate support. Scale beyond a single machine with the distributed worker mode, which dispatches tasks to remote nodes via gRPC with automatic label-based routing and worker selection. Deploy with Docker, the official Helm chart for Kubernetes, or a simple binary download requiring only a Linux, macOS, or Windows host. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3 licensed.

To pull a team's skills, MCP servers, hooks, prompts, and agent files out of scattered Git repositories, Observal keeps them in one reviewed registry and traces real sessions to show which ones help. Build an agent visually, with a live config preview for every harness. Submissions wait in an admin review queue, where reviewers inspect side-by-side version diffs before approving a release. Teamspaces give each team its own namespace, and approved releases can be forked into independent drafts. One pull command then writes the right config for Claude Code, Cursor, Kiro, Codex, Copilot, Pi, OpenCode, Antigravity, or Goose. Every approved resource is discoverable through the open Agentic Resource Discovery standard, and a running agent can hand part of its task to another approved agent or a remote Agent2Agent service. Hooks record each session as a trace of prompts, tool calls, MCP round trips, tokens, and errors, with turn-by-turn replay for debugging and audits. Insight reports, generated through providers such as Anthropic, OpenAI, or Ollama, list what is working, what is hindering, and quick wins. A dashboard follows adoption, cost, and department usage, a leaderboard ranks agents by downloads, and audit logs, SAML single sign-on, and SCIM provisioning are included. 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.

Every team building with coding agents has the same drawer problem: the best Skill, MCP server, or agent file lives in one person's repo, undocumented, while three colleagues rebuild it from scratch. Agentic Resource Registry is the internal catalog that ends the duplication, a self-hosted registry where your organization publishes Skills, MCP servers, hooks, prompts, agent files, and sandboxes in one searchable place. Browse by teamspace, publisher, category, or harness and see at a glance what each resource supports and how often it has been pulled. Authors build agent files in a four-step builder with a live summary and draft readiness checks, then submit them into a review queue where admins inspect the full prompt and version diffs before approving. Forking an approved release creates your own draft with pinned components, and reviewers can compare it against upstream line by line. The companion CLI installs any approved resource into Claude Code, Cursor, Codex, Kiro, Copilot, OpenCode, Pi, and more, generating the correct config for each harness automatically. Approved resources are also discoverable over the open ARD standard, so a running agent can hand part of its task to another approved agent or a remote A2A service. 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.

Tracking over 50,000 fleet vehicles across production deployments, Fleetbase delivers a modular logistics operating system where each module—Fleet-Ops, Storefront, Pallet, and Ledger—works independently yet shares a unified data layer that eliminates middleware between ordering, dispatch, warehousing, and accounting. The Fleet-Ops core handles real-time driver tracking through a SocketCluster-based WebSocket event bus, interactive map-based dispatch with both directed and ad-hoc driver assignment, configurable order workflows with custom rules, automation triggers, and activity flows, plus a Kanban-style order board for visual pipeline management. Service zones let dispatchers define geographic operating areas, while proof-of-delivery capture and route optimization close the last-mile loop. The Storefront module provides headless e-commerce with products, carts, and checkout that feed directly into dispatch queues, and the Ledger module records invoices and financial journal entries across all operations. The Navigator driver app—also AGPL-3.0 licensed and fully white-label—delivers turn-by-turn navigation, live order communication, and fault reporting to drivers in the field. The extension architecture pairs backend Laravel Composer packages with frontend Ember Engine modules, enabling third-party developers to build first-class platform extensions without forking. A RESTful API with full documentation, webhook delivery via Redis-backed queues, and push notification support through APNs and FCM round out the integration surface. 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.

Every Redis client you already use connects to Kvrocks without a single code change, but instead of holding your entire dataset in RAM, data lives on SSD through RocksDB, turning terabytes of memory cost into pennies of disk. An Apache Software Foundation top-level project, Kvrocks supports strings, hashes, lists, sets, sorted sets, streams, bitmaps, JSON documents, TimeSeries data points, Bloom filters, Cuckoo filters, and HyperLogLog structures, all persisted to disk with in-memory caching for hot data access. Asynchronous replication using binlog similar to MySQL provides data durability across replicas, while Redis Sentinel integration enables automatic failover when master or replica nodes fail. The proxyless centralized cluster architecture distributes data across shards while remaining fully compatible with standard Redis cluster SDKs and clients. Token-based namespaces provide multi-tenant isolation with authentication per namespace, going beyond Redis SELECT's numbered database model. RocksDB's LSM-tree storage engine provides efficient compression through configurable compaction strategies, reducing disk footprint dramatically while maintaining sub-millisecond reads for cached keys. Migration tooling includes RedisShake for Redis-to-Kvrocks live migration and kvrocks2redis for reverse migration, enabling gradual adoption without service interruption. The kvrocks_exporter exposes Prometheus-compatible metrics for monitoring, and OpenTelemetry integration provides distributed tracing. 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.

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.

Service businesses get a booking page without per-booking commissions or monthly SaaS fees from Easy!Appointments, the self-hosted appointment scheduler. Customers pick a service, provider, and open time slot from a clean web form; the system enforces working plans, breaks, and booking rules you define per provider, then confirms by email to both sides. The structure fits real service organizations: multiple providers with individual schedules, multiple service types with their own durations and prices, and admin/secretary roles for front-desk management. Two-way Google Calendar synchronization keeps each provider's external calendar authoritative - book in Easy!Appointments and it appears in Google Calendar, block time in Google and the slot disappears from the booking form. Version 1.6 adds SMS notifications and payment support, and a REST API opens the scheduling data to custom integrations. Built on PHP (CodeIgniter) with MySQL, it installs in a single folder and can share a database with your existing site; a WordPress plugin embeds the booking form directly in pages or posts. The interface ships in dozens of languages with time-zone handling throughout. GPL-3.0 licensed and free for commercial use - a helpdesk, clinic, salon, or consultancy runs its whole booking workflow on its own server.

Its author, a student and WakaTime fan, didn't want to pay $9/month for data about his own keystrokes - so Wakapi was born, a self-hosted, WakaTime-compatible backend for coding statistics. The compatibility is the killer design decision: the official WakaTime plugins for VS Code, JetBrains IDEs, Vim, and dozens of other editors work unmodified - just point the plugin's API URL at your Wakapi instance with your personal key, and heartbeats flow to your server instead of a third party's. Duration inference matches WakaTime's own algorithm, with a configurable timeout (10 minutes by default). From that stream Wakapi builds statistics and plots across projects, languages, editors, hosts, and operating systems, plus the fun extras: public leaderboards (optionally login-gated, with configurable aggregation windows), badges for GitHub readmes, and weekly email reports. A REST API serves your data programmatically, Prometheus export feeds your existing Grafana, and a WakaTime relay mode can mirror heartbeats to both services during migration - with one-click import of historical WakaTime data. Written in Go, it is lightning fast and light enough for the smallest instance, storing to SQLite, PostgreSQL, or MySQL, with configurable data retention for GDPR peace of mind. Deliberately smaller than WakaTime, deliberately yours.