How Is Yaak Licensed and Managed for Teams?

Yaak uses per-seat licenses for teams, managed from a central dashboard. If your team already runs an identity provider, you can connect it through OpenID Connect for sign-in and SCIM for member provisioning, then buy and reassign seats online as headcount changes. This model fits teams that want shared tooling without adopting a proprietary cloud platform — but it assumes you have (or are willing to set up) an identity provider and a Git workflow for the actual request files.

The licensing model

Yaak's team offering is seat-based rather than usage- or request-based:

• Per-seat licenses for teams of any size, managed in one place.
• Online purchase and reassignment — buy seats online and reassign them as your team changes.
• Central dashboard — assign and manage licenses from a single place.

The practical implication is that cost scales with the number of people who need access, not with how many requests they store or how much traffic they generate. Because seats can be reassigned, you don't have to over-provision for turnover; you can move a seat from a departing member to a new one.

Pricing figures are not included in the source material. The site links to a pricing page, so check there for current per-seat rates before committing to a headcount.

Identity and provisioning

Two standards handle team access:

Both connect to the identity provider you already use, which means onboarding and offboarding can follow your existing directory rather than a separate Yaak-specific account system. If your team has no IdP, this is the main prerequisite to resolve before adopting the team tier — the individual desktop app doesn't require an account, but organization sign-in is built around OIDC.

What stays outside the license

The team license covers access and administration. It does not change where your data lives:

• The desktop app stores work locally and sends API requests directly to your servers.
• No account is required for the desktop app, and there is no automatic cloud sync.
• Collaboration happens through your existing Git workflows — one YAML file per request, folder, and environment — with branch, commit, and diff available from a built-in Git UI.
• Access control for shared requests comes from your Git provider's existing permissions, not a Yaak-hosted permission system.
• Secrets can optionally be encrypted, with keys held in the OS keychain.

So the licensing layer governs who can use the app as part of your organization, while who can see which requests is still decided by your Git provider. Plan for both.

Choosing between individual and team use

Stay on the individual desktop app if you're a solo developer or a small group comfortable sharing requests purely through Git, you don't need centralized seat management, and you don't need SSO or automated provisioning.

Move to the team tier if you need to manage licenses in one place, want sign-in through your existing identity provider, need SCIM-based member provisioning, or expect headcount to change often enough that reassigning seats matters.

A reasonable evaluation sequence: confirm your IdP supports OIDC and SCIM, check current per-seat pricing on the pricing page, and run a small pilot where one person buys and assigns a seat before rolling out to the whole team.