In-somnia is in-credible... And allowing import from postman collections means I've never once looked back.
Postman is quickly trending towards bloatware, where _most_ people just want it for is for a GUI for curl and to share APIs across teams, but Postman becomes more and more bloated with "enterprise" features to justify valuations, while losing focus on the core demo that first adopted it!
The space is already crowded, though (many of them being open source), for example Insomnia, Paw, Fiddler, Hoppscotch, and even Thunder Client (a VS Code extension). I suspect that the Postman investors are privy to information that warrant the investment (plus the economic climate being what it is).
It's a GUI around curl commands. Any enterprise company could trivially spin up a team to build an open source tool that does 80 percent of its use cases.
Company i used to work for just hired a few part-time interns to build and maintain a custom version of Postman. Auto-generated web-forms based on the underlying service code. Then would offer those interns full time jobs on graduation and hire new interns to continue maintaining the project (with any ex-intern full-timers able to jump in and/or advice as needed).
Is there not already a 100% open source solution? This is one of those cases where a good dev could likely build a clone in a month. And it hardly needs constant updates.
Your posts are incredibly condescending. If you could at least make some effort to explain your thoughts, at least you'd be adding something to the conversation.
Maybe I'm using postman wrong? Besides saving data, what is there to scale? And even saving data is likely a minor point for many who use this, they could export their routes in some way.
Obviously dropbox has a sharing problem to solve, but I honestly don't see what your post adds to the discussion. Perhaps you could enlighten me to the problem that Postman is solving?
I mean, I have no idea how you use it, but I doubt you're "using it wrong". You're just not everyone or every use case.
Expanding on that, just because you don't understand what problem it solves, why people would want to pay for it, or why VC's believe they can profitably invest at a given valuation, doesn't meant that any of them are wrong.
It just means you don't understand from someone else's perspective. So when you say "This is one of those cases where a good dev could likely build a clone in a month. And it hardly needs constant updates." - it's coming from a place of ignorance to the other people's problems and their scope.
> Perhaps you could enlighten me to the problem that Postman is solving?
A quick glance at their homepage helps with this. "Build APIs together" and then the value props go on with "Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster."
So Postman is about the collaboration and process of building APIs. Not about a curl gui. That's an expensive, big, valuable problem space.
It's a socially-networked gui around curl commands! I need to dig up the quotes, but in Bruce Sterling's sci fi book Heavy Weather, he says that no one pays for sotware, except groupwere, which everyone begrudgingly pays out for.
I gotta say though I am super unimpressed by the Postman team's ability to prioritize / do the right things. Basic capabilities likes SOCKS proxies or proxies DNS are just totally awol, making this tool practically useless in a wide variety of everyday development circumstances. Ticket's been open 6 years now[1]. Really not that hard to add, would make such a powerful difference.
I have to second this comment... I really like the Postman software (I don't use it with an account). I really want to understand how this kind of valuation can be justified.
Postman is a nice free tool, but nothing more. I would never pay any money for it. I don't think they can monetize more than 1% of their user base. I am absolutely stunned by this valuation.
The only justifications I can see for this valuation:
1. 17 million developers using Postman. This is impressive for any developer tool.
2. Public API network. This is something that could easily turn into an API marketplace, which sounds like it could excite investors.
I am curious how they calculate #(developers using Postman). I have had Postman accounts associated with my emails at a few different companies. In every case, we moved away from Postman. I probably account for 5 different Postman accounts, all inactive.
Figma is a lot harder to replace than postman and it's primary users are not developers (although they often consume the result of the primary users). I think developers are more fickle than designers as a customer, especially for tools that are not central to the end result.
If I deploy my app and it works it does not really matter if I tested/documented it with postman, it's not central to the app at runtime.
I also think that postman's core product is a lot easier to replicate (they were not even the first to do it) than figma and there are a number of open source projects that do.
When it comes to their API gallery I would expect that any serious API would come with a non-proprietary definition or documentation (in something like OpenAPI or at least just good docs) too.
I don't know, I just have a hard time to see why this product (and by extension the company) is worth 5.6B.
Developers don't make the call. Companies would ask people to create and share a postman collection with API tests instead of checking it into git.
Valuations are crazy these days. But I don't see how this is crazier than other SaaS valuations. Why github when you can run your own server? Why use confluence when you can check in your docs into git?
lol, revenue not even mentioned on the page. Seems like an absurd valuation but times are crazy and VCs are throwing money anywhere they can
my only guess is that they raised based on their user count and have pitched some sort of strategy to monetize based on that. I'm guessing it is B2B focus, maybe some platform to make it easier for SaaS API companies to get to users. Or just pure enterprise sales and try to get big companies to pay for it. Maybe even try to monetize the data about what APIs free tier developers are using, although that type of telemetry would probably piss off most their users
I just don't see developers paying for Postman directly, there are decent open source alternatives.
I’ve totally had the why not just use curl moment a la the famous Dropbox quote. But man developer tool saas in general are on fire with growth and outright command these type of valuations. Congratulations to the postman team!
If you look at their feature
matrix they seem to plan to expand from a deveolpment tool to a general purpose API tooling/monitoring platform: https://www.postman.com/pricing/
If you find Postman too bloated, a great alternative is Insomnia (https://insomnia.rest/) which is very similar when Postman just started; a simple, very useful tool without all the corporate bullshit and lots of unnecessary paid features packed in Electron.
I don't know anyone personally that pays for Postman...anyone here pays for it?
I've used many times Postman, in the past, but never paid.
In comparison I pay and have paid for Github for a long time though, and know plenty of people who also do either through personal/work
I used to love Postman, but with their recent updates, it has become nearly useless for work.
They've clearly made it cumbersome to collaborate with collections via git so that you have to pay for their service, and the cost of the service is too high to justify what it does.
I don't think the cloud service route was the correct one for monetizing Postman. I think they should have left basic HTTP support at the free tier and then offered feature parity w/ curl and testing at paid tiers.
It always amuses me that Postman's branding is all space themed.
I realise the "post" in Postman is likely a reference to the HTTP POST verb, but wouldn't it have made more sense to go postal (ha) for their branding instead of space? Feels like such a missed opportunity.
My jaw hit the floor when I saw $5.6B. Valuations have been crazy for a while, but that kind of money for an OK-ish developer tool is bonkers in any world.
Weber Grills just went public at a similar valuation. It's truly amazing that a global household name would go for the same price as a niche tool that is optional to pay for.
I would pay a small one time fee for a good collection that would save me the time having to read the documentation. The API collection store could allow developers to create and sell their collection. They could also have sponsored links, you could target people with specific needs.
69 comments
[ 1.9 ms ] story [ 117 ms ] threadPostman is quickly trending towards bloatware, where _most_ people just want it for is for a GUI for curl and to share APIs across teams, but Postman becomes more and more bloated with "enterprise" features to justify valuations, while losing focus on the core demo that first adopted it!
[1]: https://insomnia.rest/ (hattip for the domain name as well ;) )
For the rest of us there is curl and Powershell Web-Request.
And yet...don't?
> could trivially spin up a team
Or they could trivially pay for a 100% solution w/o having to lose focus on what they actually do.
I wish I had $5 / user / yr for every person who says this about products!
Kidding aside, I think this dramatically underestimates what it takes to build a product that solves the problems that Postman solves.
"Curl has no gui" isn't the problem they're solving.
Yeah I'm getting Show HN: Dropbox thread vibes from this thread lol.
Obviously dropbox has a sharing problem to solve, but I honestly don't see what your post adds to the discussion. Perhaps you could enlighten me to the problem that Postman is solving?
Expanding on that, just because you don't understand what problem it solves, why people would want to pay for it, or why VC's believe they can profitably invest at a given valuation, doesn't meant that any of them are wrong.
It just means you don't understand from someone else's perspective. So when you say "This is one of those cases where a good dev could likely build a clone in a month. And it hardly needs constant updates." - it's coming from a place of ignorance to the other people's problems and their scope.
> Perhaps you could enlighten me to the problem that Postman is solving?
A quick glance at their homepage helps with this. "Build APIs together" and then the value props go on with "Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster."
So Postman is about the collaboration and process of building APIs. Not about a curl gui. That's an expensive, big, valuable problem space.
https://news.ycombinator.com/item?id=9224
I gotta say though I am super unimpressed by the Postman team's ability to prioritize / do the right things. Basic capabilities likes SOCKS proxies or proxies DNS are just totally awol, making this tool practically useless in a wide variety of everyday development circumstances. Ticket's been open 6 years now[1]. Really not that hard to add, would make such a powerful difference.
[1] https://github.com/postmanlabs/postman-app-support/issues/13...
I'm not a full time frontend dev though so perhaps they would be more willing to pay.
Money have never been cheaper, ever
What does that mean? Is there a top down SAAS?
Top down = decision makers force individual users to use
> There are now 17 million developers on the Postman API Platform, and the Postman app has been downloaded more than 60 million times so far.
That's a significant user base for a b2b oriented app in a very monetize-able space.
Throwing out some numbers to try and math it out:
- At $5 / yr / user, that's 85mm revenue. 5.4B = 64x rev
- At $10 / yr / user, that's 170mm revenue. 5.4B = 32x rev
- At $20 / yr / user, that's 340mm revenue. 5.4B = 16x rev
All depends on how effectively they monetize.
There's definitely a credible-to-vc's story that this is a large company in the making.
I think they can make significantly more per year for enterprise users, in the $100+ per user range.
1. 17 million developers using Postman. This is impressive for any developer tool.
2. Public API network. This is something that could easily turn into an API marketplace, which sounds like it could excite investors.
I am curious how they calculate #(developers using Postman). I have had Postman accounts associated with my emails at a few different companies. In every case, we moved away from Postman. I probably account for 5 different Postman accounts, all inactive.
In this case it should be compared to valuation of tools like figma
If I deploy my app and it works it does not really matter if I tested/documented it with postman, it's not central to the app at runtime.
I also think that postman's core product is a lot easier to replicate (they were not even the first to do it) than figma and there are a number of open source projects that do.
When it comes to their API gallery I would expect that any serious API would come with a non-proprietary definition or documentation (in something like OpenAPI or at least just good docs) too.
I don't know, I just have a hard time to see why this product (and by extension the company) is worth 5.6B.
Valuations are crazy these days. But I don't see how this is crazier than other SaaS valuations. Why github when you can run your own server? Why use confluence when you can check in your docs into git?
my only guess is that they raised based on their user count and have pitched some sort of strategy to monetize based on that. I'm guessing it is B2B focus, maybe some platform to make it easier for SaaS API companies to get to users. Or just pure enterprise sales and try to get big companies to pay for it. Maybe even try to monetize the data about what APIs free tier developers are using, although that type of telemetry would probably piss off most their users
I just don't see developers paying for Postman directly, there are decent open source alternatives.
How do you meet VCs or find good ones? Do you hunt them down? Do you suggest a valuation for investment?
0. https://www.postman.com/pricing/
They've clearly made it cumbersome to collaborate with collections via git so that you have to pay for their service, and the cost of the service is too high to justify what it does.
I don't think the cloud service route was the correct one for monetizing Postman. I think they should have left basic HTTP support at the free tier and then offered feature parity w/ curl and testing at paid tiers.
I realise the "post" in Postman is likely a reference to the HTTP POST verb, but wouldn't it have made more sense to go postal (ha) for their branding instead of space? Feels like such a missed opportunity.
Weber Grills just went public at a similar valuation. It's truly amazing that a global household name would go for the same price as a niche tool that is optional to pay for.