🐙
Freemiumapi testingdeveloper toolsopen source

Hoppscotch is an open-source API testing and development platform covering REST, GraphQL, WebSocket, and more, available as a web app, desktop app, and CLI, with offline, on-prem, and cloud deployment options. It's positioned as a lighter, open-source alternative to Postman and Insomnia. MIT-licensed, 80,000+ GitHub stars.

What is Hoppscotch?

Hoppscotch is an open-source API development environment, the kind of tool you open to send a request, read the response and save it for next time. It covers REST and GraphQL along with real-time protocols such as WebSocket, and organizes work into collections and environments so the same request can run against local, staging and production without editing it by hand. It comes in three forms that share the same collections: a browser app, a desktop app, and a command line runner you can drop into CI to execute a collection as a test suite. Deployment is flexible in the same way, with a hosted version, a self-hosted option for teams that need requests and secrets to stay inside their own network, and offline use. The project is MIT licensed, and it positions itself directly as the lighter open alternative to Postman and Insomnia.

Who is Hoppscotch for?

This is the obvious pick when the API client you use has grown into something heavier than the job requires. The common trigger is an account wall or a sync feature you never asked for standing between you and a request you want to fire once. Hoppscotch opens fast and gets out of the way. It also fits teams with a hard requirement that API credentials and internal endpoints never touch a third-party cloud, since the whole stack can run on your own infrastructure. The CLI matters here too: if you want collection runs in a pipeline rather than a person clicking send, that path exists without a separate product.

How does Hoppscotch compare?

The other open-source projects it sits near in this category solve different problems. Pocketbase gives you a backend to build against, a database with auth and file storage in one binary, where Hoppscotch is the tool you use to exercise an API that already exists. n8n is a workflow automation platform that calls APIs as steps in an automation, which is production plumbing rather than an interactive client for development and debugging. Papercups is a self-hosted customer messaging tool, related only in that it belongs to the same family of open replacements for commercial SaaS. Hoppscotch is the one you reach for while building and testing the API itself.

Compare with: Pocketbase, n8n

Hoppscotch pricing

The catalog records this as freemium. In practice that means the code is open source and self-hosting is available, while the hosted service carries paid plans for the things teams need beyond individual use, typically collaboration, shared workspaces and administrative controls. Trying it costs nothing, and running it yourself replaces a subscription with your own hosting and maintenance. Check the project site for the current split between the free tier and paid plans before committing a team to it.

Notes

No notes have been added for this tool yet.

Hoppscotch FAQ

Is Hoppscotch a drop-in replacement for Postman?
It covers the same core job of composing requests, managing environments and organizing collections, and it is positioned as an open alternative. It is not feature-identical, so if your team leans on specific Postman capabilities, test those first. Migrating existing collections is the step most worth trying before you commit.
Can I self-host Hoppscotch?
Yes. Self-hosted and on-premise deployment is one of the documented options, which is a common reason teams choose it. Running your own instance keeps API keys, internal endpoints and request history inside your network rather than in a vendor account, at the cost of maintaining the deployment.
Does it work in CI?
There is a command line interface that runs collections, which is the piece you would wire into a pipeline to check that an API still behaves after a deploy. Consult the CLI documentation for how collections and environments are passed in, since that determines how cleanly it drops into your existing setup.
Browse all Open Source