Horizontal scaling allows businesses to use commodity hardware or budget-friendly cloud instances rather than expensive, high-end servers.
Modern organizations require absolute control over their data without sacrificing the collaboration features popularized by public cloud giants. Nextcloud fills this gap perfectly, offering a self-hosted productivity platform that spans file sync, communication, and office automation. However, as user bases grow, a single-server Nextcloud instance inevitably faces performance bottlenecks and single-point-of-failure risks.
When scaling up, resource-heavy AI tasks or LLMs can be moved to dedicated GPU-equipped hardware. HaRP facilitates this by allowing an external Docker host to securely communicate back over WAN via FRP certificates generated automatically inside the primary /certs/frp storage path. Finalizing Integration inside Nextcloud Admin UI
As Nextcloud continues to evolve into a comprehensive ecosystem for collaboration and productivity, the ability to extend its functionality through external applications (ExApps) has become paramount. Introduced to enhance this experience, particularly for Nextcloud 32 and beyond, is a specialized proxy system designed to streamline the deployment, performance, and security of these external microservices . harp nextcloud
Edit config/config.php :
H(F_i) = SHA3-256( metadata_i || H(F_i-1) )
HaRP is designed for . It allows you to run resource-heavy applications—such as AI models requiring high-end GPUs—on separate physical hardware while maintaining a seamless user experience within the main Nextcloud interface. A single HaRP instance can even manage up to 99 different Docker Engines across your network. Why You Should Care However, as user bases grow, a single-server Nextcloud
Let me know how you'd like to . Docker Deploy Daemon (HaRP) - Nextcloud Documentation
CREATE DATABASE nextcloud_harp CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; CREATE USER 'harp_user'@'%.example.internal' IDENTIFIED BY 'YourSecurePassword'; GRANT ALL PRIVILEGES ON nextcloud_harp.* TO 'harp_user'@'%.example.internal'; FLUSH PRIVILEGES; Use code with caution. Step 2: Configure Shared Object Storage
I can help you with: The docker-compose configuration for a HaRP setup. Integrating ExApps on a remote GPU server. Configuring NGINX or Caddy to sit in front of HaRP. AIO and HARP for ExApp running remotely - ℹ️ Support slow remote access
HaRP direct-routes requests to ExApps. This means requests from the web UI to an external app do not need to pass through the main Nextcloud PHP stack, drastically reducing latency and freeing up server resources.
We implemented Harp as a Nextcloud app (PHP 8.2) with a companion daemon (Rust) for DAG operations and sync. The Rust component communicates via Unix sockets to avoid blocking PHP-FPM.
Version 0: 3f4c... (initial upload) Version 1: a1b9... (renamed from draft.pdf) Version 2: d7e2... (content updated)
If you are running a Nextcloud server and struggling with bandwidth bills, slow remote access, or central failure points, it is time to experiment with the Harp storage backend. The technology has matured from "experimental hack" to "production-ready adjunct."
tunnels, your app containers don't need to expose ports to the host or deal with complex NAT traversal. Boosts Performance: