Self-Hosted / Projects / Hoppscotch Community Edition
Hoppscotch Community Edition
StableSpecs verified October 3, 2026 · against v2026.9.0
Overview
Self-hosted Postman alternative for browser-based API development and testing.
Hoppscotch Community Edition is a self-hosted API development platform for people who want a browser-based Postman alternative with control over their API requests, workspaces, and user data.
Why people choose Hoppscotch
The useful search angle is API testing without handing the whole workflow to a hosted SaaS. Hoppscotch combines a web client, desktop and CLI options, request collections, environments, and team workspaces, while the Community Edition can run on infrastructure you manage.
What is included
The official project and docs cover HTTP requests, REST, GraphQL, WebSockets, collections, environments, request history, real-time collaboration, admin controls, and integrations for authentication and SMTP. Community Edition adds an admin dashboard for workspace and user management.
What to know before deployment
Community Edition is not a single static web page. The official prerequisites cover a Docker-capable host, PostgreSQL, authentication-provider configuration, and SMTP for account workflows. You also own updates, secrets, backups, TLS, and the availability of the supporting services.
Best fit
Choose Hoppscotch when a developer or small team wants an open-source API client and a self-hosted workspace. Use a hosted tool when you want the provider to operate identity, upgrades, and availability, or a lighter local client when shared workspaces are unnecessary.
Interface previews
Screenshots of the Hoppscotch Community Edition interface.
Feature support
| Feature | Support |
|---|---|
| HTTP and REST API requestsCore API request building is the primary Hoppscotch workflow. | Supported |
| GraphQL requestsThe official project lists GraphQL support alongside REST tooling. | Supported |
| WebSocket testingWebSocket work is included in the open-source API development ecosystem. | Supported |
| Collections and request organizationCollections organize reusable requests and API workflows. | Supported |
| Environment variablesEnvironments support reusable request configuration across development contexts. | Supported |
| Team workspaces and collaborationWorkspace and collaboration features are available, with exact Community Edition limits documented upstream. | Supported |
| Admin dashboardCommunity Edition documentation describes an admin dashboard for workspaces and users. | Supported |
| Docker deploymentOfficial self-hosting documentation provides a Docker-based install and build path. | Supported |
| OAuth providers and SMTP workflowsThese require external provider and mail configuration during self-hosting. | Partial support |
Community signals
- Stars
- 80.6k
- Forks
- 6.1k
- Open issues
- 849
- Last commit
- 6d ago
- Latest release
- 2026.9.0
- Repo created
- Aug 2019
Includes open pull requests
2w ago
Refreshed nightly from the GitHub API.
Questions
What is Hoppscotch Community Edition used for?
It is used to build, send, organize, and test API requests through a self-hosted web, desktop, or CLI workflow, including REST, GraphQL, and WebSocket use cases.
Is Hoppscotch a self-hosted Postman alternative?
Yes. Hoppscotch is an open-source API development ecosystem commonly compared with Postman, and Community Edition can be deployed on infrastructure you manage.
Can Hoppscotch Community Edition run with Docker?
Yes. The official Community Edition documentation provides a Docker-based installation and build path.
Does Hoppscotch Community Edition need PostgreSQL?
The official self-hosting prerequisites include PostgreSQL for the Community Edition deployment, along with the other services and configuration described in the current guide.
Does self-hosted Hoppscotch need SMTP?
SMTP is part of the documented prerequisites for account and email workflows. Configure it if your deployment needs those flows.
Is Hoppscotch free and open source?
Community Edition is documented as open source and available without an additional license fee, but hosting, maintenance, and any external services remain your responsibility.
Who should use Hoppscotch instead of a local API client?
Use it when shared collections, workspaces, or browser access matter. A local client may be simpler when one developer only needs private request testing.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.