Skip to content
Type
website
Verdict
Useful
Licence
Conditional licence, mixedmixedFree desktop app with per-seat team licences managed through an organisation, prices on a separate pricing page at review. The source is published as MIT-licensed; the hosted team features are proprietary, so licences differ by what you take
Agent channels
mcp, cli
Pricing
freemium
Reviewed

← Atlas · Topics: landing-pages, documentation

Yaak ​

Type
website
Verdict
Useful
Licence
Conditional licence, mixedmixedFree desktop app with per-seat team licences managed through an organisation, prices on a separate pricing page at review. The source is published as MIT-licensed; the hosted team features are proprietary, so licences differ by what you take
Agent channels
mcp, cli
Pricing
freemium
Reviewed

What it is ​

Yaak is a local-first API client, and its page is a study in restraint: a headline, a download, and a light/dark switch sitting in the preview itself rather than in a settings menu. The capability list is written as short claims with numbers attached ("Manage 3,286 requests with no lag"), each followed by a plain explanation, and the middle of the page is a Git section that explains one YAML file per request, folder and environment.

When to open it ​

Open it when you need a reference for showing an interface across two themes on a marketing page, or for using a changelog as evidence rather than as an archive: the versions are listed with dates and what changed, which reads as proof of maintenance.

Most useful ​

  • Theme toggle in the hero preview, so a reader judges both appearances before downloading.
  • Capability lines with a number in each, which make vague claims checkable.
  • A stated non-feature list: no cloud platform, no dashboard, no AI sidebar. Saying what it refuses to include is the positioning.
  • Git as the collaboration story, with one YAML file per request, folder and environment, and a built-in diff view.
  • Changelog as a design element: dated versions in a vertical list, each with a one-line summary.

Using it with agents ​

The site states an MCP plugin and a CLI, plus a one-line skill install for agents, and notes that changes made through the CLI appear in the app. That makes it one of the few pages here where the agent channel is part of the product rather than a documentation afterthought.

Watch out for ​

  • The page leans on developer trust signals (GitHub stars, changelog, quotes) rather than screenshots; the interface is barely shown.
  • Team features (SSO, SCIM, provisioning) are the paid part, so the free app's collaboration story is Git only.
  • The MIT claim covers the source, not the team product; the split is easy to miss.
  • Version numbers and request counts date quickly.
  • The design is quiet to the point of being sparse; there is little to borrow visually beyond the toggle.

Reusable ideas ​

  • Put a theme switch on the preview, not in a menu.
  • Attach a number to each capability claim.
  • Name what the product deliberately does not do.
  • Show the changelog as a dated list, because maintenance is the feature.

Warp, Spacedrive