A year ago I had just launched Yaak’s commercial-use license and was sitting at $160 MRR. It was a gamble to choose a business model that offered no actual incentive to upgrade other than good-faith compliance, but it’s been paying off. My bet was that larger organizations would purchase for legal compliance (and support) and it’s proving to be true. Multiple teams of 30+ seats have signed on!
Today, MRR sits at $1900—over 10x growth in one year—and total revenue has crossed $25,000!
While the numbers are moving in the right direction, 2025 was a struggle. As always, marketing and user acquisition was the main challenge.
Around mid-year, active users plateaued for ~6 months. Revenue continued to climb, but nothing meaningfully accelerated growth. In hindsight, this seems to be due to two factors: API clients aren’t especially exciting right now, and teams already have deeply ingrained workflows with other tools.
Individuals clearly enjoy using Yaak, but turning that enthusiasm into team-wide adoption has proven difficult.
Here’s a quote from the survey I sent out at the beginning of the year:
The thing preventing most people from using Yaak more is the inability to convince their coworkers and friends to switch.
It seems that the only path forward is hoping early adopters become advocates and push Yaak within their companies… or by waiting for the competition to screw up.
On October 20, AWS experienced a major regional outage. Postman was unusable as a result—even for local APIs—so there were suddenly a lot of angry users looking for alternatives. Since Yaak works fully offline and can never have downtime, it was an easy sell.
I was able to capitalize on X and Hacker News with some good posts, which led to ~20k new downloads and a 6x increase in daily active users!
This was a huge win. Growth has settled down again but it seems like this was the spike that’s been driving larger companies to sign on.
Of course, marketing wins are nothing without a good product. I’m extremely proud of how far Yaak has come in just a couple of short years, and this pace of improvement is only going to increase.
Git and Team Workflows → Directory sync, Git compatibility, 1Password integration, encryption
Customization → Environment colors, custom fonts, colored HTTP methods, layout toggle
Plugin Ecosystem → Plugin directory, GraphQL doc explorer, Run-in-Yaak button
Core Improvements → Folder inheritance, folder variables, sidebar filtering, improved Postman imports, more template functions
See the full changelog for more details.
My goal for 2026 is to bring Yaak to the sustainable revenue number of $10k/mo. By MRR alone that means a 10x increase. However, because subscriptions are annual, revenue is actually 3x MRR and so only a 3x increase is needed if this ratio holds true.
I still have close to 2 years of runway to do this so I’m not overly worried, but reaching this milestone would take that looming doubt off my shoulders and start thinking further into the future.
To get there, I’ll be focusing on a few core things:
Migration & onboarding → Keep reducing friction for teams switching from other tools.
Team workflows → Git integration, sharing, and more import/export control.
Plugin ecosystem → Expand APIs and community contributions to support more use cases.
Product onboarding → Improve the first-user experience, and feature discovery.
I’m super excited for 2026. This year proved to me that Yaak can work as a product in the long term. As long as growth keeps going at the same rate, 2026 is going to be the year Yaak proves itself.
Happy New Year!
~ Greg
