Harp solves the infrastructure problem—it removes the need for AWS or Azure.
HaRP serves as a modern replacement for the older , which will be deprecated by Nextcloud 35 . This article explores why HaRP is essential, how it works, and how you can implement it in your Nextcloud environment. Why Nextcloud Needs HaRP harp nextcloud
The technical realization of the Harp philosophy in a Nextcloud environment relies on three key tools, each acting as a different register on the harp: for fast, non-blocking transaction handling; Pusher or a similar WebSocket service for real-time notifications; and Cron with a proper job queue (like Redis Streams or RabbitMQ) for background processing. In a standard LAMP/LEMP stack, when a user edits a large document in Nextcloud’s Collabora Online or OnlyOffice integration, the server holds the connection open, waiting for the editing session to save. Under the Harp model, the save request is immediately acknowledged and pushed into a job queue. The user receives a near-instantaneous “save accepted” response, while a background worker processes the actual write to disk, versioning, and external sync. This is the first string of the harp: non-blocking responsiveness . Harp solves the infrastructure problem—it removes the need
