Hoppscotch Community Edition — Self-Hosted, Open-Source

Features

• GET - Requests retrieve resource information
• POST - The server creates a new entry in a database
• PUT - Updates an existing resource
• PATCH - Very similar to PUT but makes a partial update on a resource
• DELETE - Deletes resource or related component
• HEAD - Retrieve response headers identical to those of a GET request, but without the response body.
• CONNECT - Establishes a tunnel to the server identified by the target resource
• OPTIONS - Describe the communication options for the target resource
• TRACE - Performs a message loop-back test along the path to the target resource
• - Some APIs use custom request methods such as LIST. Type in your custom methods.

Installation

See official install docs: https://docs.hoppscotch.io

Why self-host Hoppscotch Community Edition

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

What hardware do you need

Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Hoppscotch Community Edition. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.

Where to go from here

• Browse the full self-hosted app directory
• Compare self-hosted alternatives side-by-side
• DevOps roadmap — learn the skills to run your own server