Yaak review

Yaak is a desktop API client for HTTP, GraphQL, gRPC, WebSocket, and SSE requests. It is built around local workspaces: your work stays on your machine, and an account or automatic cloud sync is not required. That makes it a different fit from tools whose workflows depend on a hosted workspace.

For sharing and version control, Yaak supports Git workflows to commit, diff, and share requests, with optional secrets encryption. Request chaining lets you reuse values between requests without writing scripts. Plugins can add authentication methods, importers, and template functions. Yaak also has a CLI and an MCP server plugin for giving AI agents access to existing requests. A Reddit post from Yaak’s creator says the project is now open source.

The main draw is range without forcing one request style. Yaak covers five API protocols—HTTP, GraphQL, gRPC, WebSocket, and SSE—in a desktop client, while keeping work local by default. If you want to avoid account-based storage or automatic cloud syncing, that setup is a clear distinction.

Git support gives teams a way to review and share request changes in a familiar version-control workflow. Optional secrets encryption is useful when requests include sensitive values, and chaining can pass values between requests without a custom script. Plugins add room to extend authentication, imports, and template functions; the CLI and MCP plugin also let agents work with existing requests rather than starting from a separate collection.

The listed paid entry point is $79 per year for Individual Annual, or $6.58 per month when expressed as an annual rate. There is also a $349 one-time Individual Lifetime license. The pricing page lists a 30-day free trial, so buyers can check fit before committing.

The free plan’s limits are not published on the vendor's site. It confirms a free plan and a 30-day trial, but does not say what the free tier includes or where its caps sit. That makes it hard to judge whether free use will cover a real team or professional workflow before signing up.

There is no monthly billing for paid licenses. Individual Annual costs $79 upfront each year; Business costs $149 per user annually, shown as $12.42 per user per month. Individual licenses are single and non-transferable, with a three-device cap. Business adds transferable licenses, SSO, and user provisioning, but still caps each license at three devices. The $349 lifetime option is also single-user and non-transferable, so it is not a team-wide buyout.

Local-first storage avoids automatic cloud sync, but teams should be comfortable with Git as their sharing workflow. Buyers looking for a ready-made hosted collaboration model should confirm that Yaak’s approach suits them before switching.

Yaak has a free plan, but its limits are not published. The pricing information lists a 30-day free trial; it does not specify which paid plan the trial applies to.

Individual Annual costs $79 per year, or $6.58 per month when averaged across the year. It covers one person, commercial use and up to three devices, with a lifetime fallback license if the subscription ends. Individual Lifetime is $349 once, including future updates, for one person on up to three devices.

Business is $149 per user per year, equivalent to $12.42 per month. That is $5.84 more per user per month than Individual Annual, with transferable licenses, SSO and user provisioning. Both subscriptions are billed annually; there is no monthly billing. The pricing details list no add-ons. Compare the annual bill—not just the monthly equivalent—and confirm the free-plan limits before moving a team over.

Yaak’s local workspaces mean work stays on your machine, with no account or automatic cloud sync required. The listed sharing route is Git: commit, diff and share requests, with optional secrets encryption. That may suit teams already using Git, but it is not the same as automatic cloud collaboration.

The product supports HTTP, GraphQL, gRPC, WebSocket and SSE, and plugins include importers. The published information does not name migration sources, explain a bulk import process, or document an export format. Before switching, check how your current collections, environment values, secrets and request chains can be brought across—and test that path with a small sample. Don’t assume the importer plugins cover your current client.

Local storage and Git offer ways to keep work outside a hosted account, but the available details do not establish how painless a move away would be. No Reddit posts or comments were included in the published material, so we can’t substantiate a Reddit-based pattern for why users leave.