Hoppscotch is fast.
Scrapeman is on your disk.
Hoppscotch lives in a browser tab. Collections sit in IndexedDB, requests go through the browser stack, and CORS gets a vote on every call. Scrapeman is a native desktop app. Your collections are YAML files in a folder you pick, your requests leave from a real HTTP client, and nothing about your workflow depends on staying signed in.
At a glance
Web app, or app on your machine
| Scrapeman | Hoppscotch | |
|---|---|---|
| Runtime | Native desktop (Electron) | Browser PWA (IndexedDB) |
| Collections storage | .sman YAML files in a folder you pick | Browser storage, wiped on clear site data |
| Team sync / SSO / audit log | Use git, no plan needed | Hoppscotch Cloud paid plans |
| Account required | No | Yes for sync across devices |
| License | Apache 2.0 (open source) | MIT (open source) |
Key differences
Different place, different powers
Browser sandbox vs native process
Hoppscotch runs inside a browser tab. Requests go through the browser fetch stack, CORS rules apply on many endpoints, and auth tokens sit in page memory next to every other tab you have open.
How Scrapeman handles it
Scrapeman is an Electron desktop app. Requests leave from a native process with no CORS. Secrets stay in the app, not in a browser origin you also use for email and social media.
Local files vs IndexedDB
Free collections live in the browser IndexedDB for that profile. Clearing site data, switching browsers, or using a second machine loses them unless you sign in to Hoppscotch Cloud.
How Scrapeman handles it
Every request is one .sman YAML file in a workspace folder you choose. Folder, collection, and global variables get their own YAML files. Commit them to git, share them on a drive, diff them in review. The files are the source of truth.
Native proxy and Scrape.do mode
No built-in HTTP proxy support. If your target needs residential IPs, geo routing, or a corporate proxy, you are on your own.
How Scrapeman handles it
HTTP and HTTPS proxy with basic auth ship in the box. Native Scrape.do integration rewrites the URL and injects the token with one toggle. Per-request settings, not global hacks.
Load runner and full auth menu
No built-in single-request load runner. AWS SigV4 and advanced OAuth2 flows are not part of the free web client.
How Scrapeman handles it
Bounded-concurrency load runner with p50, p95, p99 latency, a response validator, watched response headers, CSV-driven iterations, and a save-failed-bodies ring buffer. Basic, Bearer, API Key, OAuth 2.0 (client credentials, authorization code, and code + PKCE), and AWS Signature v4 are all free.
Where Hoppscotch wins
We are not better at everything
- Open it in any browser, no install, no download. Scrapeman needs a desktop binary.
- Postman-compatible script API (pm.* namespace) for teams migrating from Postman test scripts. Scrapeman runs scripts in a Node vm sandbox with a bru API instead.
- GraphQL, MQTT, and Socket.IO out of the box. Scrapeman ships HTTP, HTTPS, and a WebSocket client today. SSE responses get a dedicated Events mode in the response viewer.
- SSO and team workspaces on the Hoppscotch Cloud enterprise tier. Scrapeman is local-first and routes collaboration through git.
- Five million monthly users and a wider plugin ecosystem. Scrapeman is younger and smaller.
If GraphQL, MQTT, or Socket.IO is a hard requirement, try Hoppscotch. If native proxy plus Scrape.do mode, a load runner with watched headers, OAuth 2.0 PKCE, and git-friendly .sman files matter more, stick with Scrapeman.
Try it free. Keep it free.
Scrapeman is free forever. No account. No trial. No browser tab required.
Download Scrapeman