# Pororoca: an HTTP/2 and HTTP/3 API client that keeps your collections on disk > Pororoca is a cross-platform API testing tool for Windows, macOS and Linux that imports and exports Postman collections, speaks HTTP/2 and HTTP/3, and stores everything locally instead of syncing it to a server. **alexandrehtrb/Pororoca** — An API testing tool with support for HTTP/2 and HTTP/3. Alternative to Postman. - Repository: https://github.com/alexandrehtrb/Pororoca - Website: https://pororoca.io - Stars: 668 · Forks: 56 - Language: C# - License: NOASSERTION - Published: 2026-09-10 · Updated: 2026-09-10 · Language: en - Canonical page: https://hysenlabs.com/projects/alexandrehtrb-pororoca ## What Pororoca is for, and who ends up using it Pororoca is an HTTP testing tool, described in its README as inspired by Postman but with many improvements. The problem it targets is narrow and practical: sending HTTP requests by hand, keeping them organised in collections, and reusing them across environments without a desktop client that phones home. The README states that Pororoca does not sync user data such as preferences, collections, environments, machine info or telemetry to any remote server, and that preferences and collections are saved as files on the user machine. That single design decision is what separates it from most hosted API clients, and it is the reason the project claims HIPAA compliance. The audience follows from that. Teams handling health data, internal APIs, or anything under a policy that forbids third-party storage of request definitions will care more about where collections live than about collaboration features. Individual developers who want a fast desktop client that can still exchange files with Postman users are the other obvious fit. The README lists multilanguage support and a fast startup time among the features, which points at day-to-day interactive use rather than CI-only execution. ## The request model: collections, environments and variables The unit of work is a collection, and collections are scoped to environments. The README lists collection-scoped environments, easy variable management and secret variables as separate features, which tells you variables are a first-class part of the model rather than a string substitution bolted on later. Secret variables matter for the same reason the local-storage policy does: credentials referenced by a request should not be written into the exported file in plain form. Collections and environments can be exported together in a single file, and the README states full export and import compatibility with Postman. That compatibility is the migration path. It also sets a boundary: because the format is Postman-compatible, anything Postman cannot express is unlikely to survive a round trip through Pororoca either. On the protocol side, the README lists support for HTTP/2 and HTTP/3, WebSockets over HTTP/1.1 and HTTP/2, automated testing, and load testing appears in the repository topics. HTTP/2 and HTTP/3 support is the feature the project leads with, and it is also where the platform constraints bite, which the next section covers. ## Installing Pororoca and sending a first HTTP/3 request There is no package manager command in the README. Installation is a download: the README points to the installation instructions at pororoca.io/docs/installation and to the GitHub releases page for the program itself. So the first step is to fetch the build for your platform from the releases page, where the most recent listed release is 3.10.2 from 2026-08-28. Once the client is open, the workflow is the same shape as any collection-based client. Create a collection, add an environment, then add a request. The README does not print a request definition or an exported file, so there is no configuration snippet to copy; the structure is created through the application's interface rather than by pasting a file. The concrete thing to check on your first run is protocol selection. The README notes that on Windows, HTTP/2 requires Windows 10 or later, while HTTP/3 requires Linux or Windows 11 and later. If you are on Windows 10, an HTTP/3 request is not something you can validate locally, regardless of how the request is configured. Test the same request over HTTP/2 first, confirm the response, then switch the protocol version and see whether the client negotiates HTTP/3 on a supported platform. ## HTTP/3 support depends on the operating system you run The most concrete limitation is stated plainly in the README and is easy to skip past. HTTP/2 on Windows needs Windows 10 or later. HTTP/3 needs Linux or Windows 11 and later. That means a Windows 10 workstation cannot exercise the headline feature at all, and a team with a mixed fleet will get different results from the same collection depending on who runs it. This is a platform constraint rather than a bug, and it is worth being direct about the consequence: if HTTP/3 testing is the reason you are evaluating Pororoca, the operating system is part of the adoption decision, not an afterthought. A CI runner also needs to be on a supported platform for HTTP/3 checks to mean anything. The second limitation is structural. The README describes full export and import compatibility with Postman. That is a strength for migration, but it also means the collection format is anchored to another tool's model. Features that a Postman-compatible file cannot represent have nowhere obvious to go, and the README does not document how Pororoca-specific settings survive a round trip through Postman. A third gap is documentation depth in the README itself. Installation, licence details and the exact shape of exported files are all pushed to pororoca.io or to files in the repository rather than spelled out inline. ## Pororoca compared with Postman and with command-line clients The README names Postman directly as the inspiration and claims much lower memory usage, two to three times less than Postman. That is the project's own claim, not a number reproduced here, and the method behind it is not described. The real difference in approach is where state lives. Postman's model centres on a synced workspace: collections and environments are shared through a hosted service, which is what makes team collaboration convenient and what makes the data-protection question complicated. Pororoca inverts that. Collections and environments are files on your machine, exported together in a single file when you want to move them. You get a smaller attack surface and a simpler compliance story; you give up the hosted sharing model, and the README does not describe a replacement for it. The second comparison is against command-line tools such as curl or an HTTP client in a scripting language. Those are better when the request is generated by code or must run in a pipeline with no GUI. Pororoca is a desktop application with collections, environments and a variable system, and its automated testing feature is described in the README but not detailed. If your test suite is already code, a GUI client adds a layer you do not need. ## Maintenance, releases and the licence question The repository is not archived, and the last push was on 2026-09-09. Release cadence over the visible window is modest and steady: 3.10.0 on 2026-05-27, 3.10.1 on 2026-06-03, and 3.10.2 on 2026-08-28. That pattern suggests a maintainer who ships fixes as they come rather than on a fixed schedule, and it means you should not expect a release every month. The upgrade cost looks low for a desktop client. The README does not document a migration step between minor versions, and it does not document rollback either, so the practical assumption is that upgrading replaces the application and your collections remain as files. That is an assumption, not a documented guarantee. Back up the exported collection file before a major version jump if the collection is the only copy. On licensing, the repository contains a LICENCE.md file, but the licence is reported as NOASSERTION rather than a recognised SPDX identifier. That is a flag, not a verdict. Read LICENCE.md before you ship anything that depends on Pororoca, and if the terms are ambiguous for your use case, ask the maintainer through the contact address in the README rather than assuming. Nothing here is legal advice. ## Conclusion Adopt Pororoca if you need HTTP/2 or HTTP/3 requests, WebSockets, or a client that never syncs collections to a remote server, and if your team is comfortable with a Postman-compatible file format. Do not adopt it if you depend on a hosted collaboration workspace or on HTTP/3 from a Windows 10 machine, since the README ties HTTP/3 to Linux or Windows 11 and later. Verify first that the release build for your platform exists on the releases page, and check the LICENCE.md file in the repository, since the licence is not declared as a standard SPDX identifier. ## FAQ ### What is Pororoca? Pororoca is an HTTP testing tool for Windows, macOS and Linux, described in its README as inspired by Postman but with many improvements. It supports HTTP/2 and HTTP/3, WebSockets, collection-scoped environments and automated testing. ### How do I install Pororoca? The README points to the installation instructions at pororoca.io/docs/installation and to the GitHub releases page, where you download the program for your platform. There is no package manager command documented in the README. ### Does Pororoca sync my collections to a server? No. The README states that Pororoca does not sync user data such as preferences, collections, environments, machine info or telemetry to any remote server, and that preferences and collections are saved as files on the user machine. ### Can I import my Postman collections into Pororoca? Yes. The README lists full export and import compatibility with Postman, and notes that collections and environments can be exported together in a single file. ### Does Pororoca support HTTP/3 on Windows? The README states that on Windows, HTTP/3 support requires Windows 11 and later, while HTTP/2 requires Windows 10 or later. On Linux, HTTP/3 is supported according to the same note. ## Sources - [alexandrehtrb/Pororoca on GitHub](https://github.com/alexandrehtrb/Pororoca) - [Issues](https://github.com/alexandrehtrb/Pororoca/issues) - [Project website](https://pororoca.io) - [README](https://github.com/alexandrehtrb/Pororoca/blob/develop/README.md) - [Releases](https://github.com/alexandrehtrb/Pororoca/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/alexandrehtrb-pororoca