Milkman – The Better Alternative to Postman

14 days ago (milkman.dev)

For a Postman-like experience, I prefer Bruno: https://github.com/usebruno/bruno (not affiliated)

The UI looks a bit outdated, it gives me vibes of some old software from 2000s somehow (probably because of the Java). And it would be really helpful to clearly state benefits of using Milkman instead of Postman right on the home page (e.g. performance benchmarks, UX, extendability, etc.). I see that it has some users and 1.3k stars so there're definitely some cool things in Milkman, probably you could just present them better

  • At this point, "outdated" is a compliment, it means that it has a menu with standard shortcuts, discoverability, accessibility. It means that it won't take 800MB of RAM to provide minimal functionality. It will stay the same across the years and not be subject of experimentation by UI designers thinking that they know better. Postman's UI started so-so and just went worse from there. SoapUI before it offered similar functionality using Swing. It's always the same app, you can rewrite it but there's no reinventing it.

What is better than the existing, established alternatives https://www.usebruno.com/ and https://insomnia.rest/ ?

Looking at such ugly UI breaks my heart :(

  • I always feel like some sort of crude brute when I read comments like this. I appreciate a good, modern UI/UX, but will always choose a tool that works well and is FOSS, despite any "last decade" look.

    Several years ago when I was developing HTTP/RPC apps, I found MilkMan and never used Postman again.

I don't understand why REST clients are so overcomplicated... We only need an interface for cURL, we don't need cloud synchronization, creating servers, grouping by namespace (or environment, or session, or call what you want), electron, JVM and so on. A simple native app would do the job.

These kinds of things are prime candidate for vibe coding; I don't understand why I would use someone else's. I have a native swift postman ripoff which hardcodes exactly the APIs I'm interested in, and is full of convenience features that make sense to nobody but me.

Sad for all the better postman alternatives, but very happy that postman is in trouble.

These days I mostly ask my coding agent to test the APIs. It can use curl create the request, attach all the cookies, whatever is necessary, and send the request, look at the response to all the testing I need. And if I need to manually test something, I ask it to give me a curl command that I can run.

How about writing it in C++ or Rust and doing away completely with huge memory footprint and long startup times. Java also needs a runtime, which is bothersome.

I suggest using wxWidgets or Qt so you get multi-platform support for free.

The author appears to be suggesting that a key difference between Bruno and Insomnia is that Milkman not written in JavaScript/Electron, but rather JavaFx (i.e., Java) and thus is faster.

> New features regularly. There are more and more plugins/features coming.

Why all software needs to constantly evolve and grow with features? This is how you end up with what Postman has become.

- I got sick of all those electron-based applications - I created a JavaFx-based workbench

Oh boi

We are in an age where it’s easier to vibe code your own alternative than to do a quick internet search to check if an alternative already exists.

  • Magnificent. One step closer to self sufficient community ships drifting through the system, meeting up with other ships once a month or less.

  • What a wonderful usage of resources.

    • Maybe this is what and how it always should have been. My life is better now that an LLM proxies my human sound waves and finger clacks to bits that do what I say - and precisely what I say nothing else

    • It's wild that building bespoke software that fits your needs instead of relying on a one-size-fits-all approach that you're constantly battling against is frowned upon.

      I have to ask myself what business you could possibly be in where you look at the software landscape and think "Yea, this aligns perfectly with my needs".

      2 replies →

Are API testing UIs really relevant anymore? I haven't manually tested an API for almost two years, and my APIs are SO much better. This kind of GUI is going to die over the next 5 years.

Postman should be seriously worried.

  • I'm thinking the same thing, I haven't have a need for a tool like Postman in a long time, prompting is enough at this point. I wonder what features others use from Postman that an agent can't do quickly.

    • Quickly eye-balling onprem responses, skipping over UIs and just eyeballing data in general is really useful. Curl can do it but with a couple headers it becomes messy, also RPCs, websockets, etc. It’s just convenient to have a single place where you can eyeball all comms.

      1 reply →

  • You're not wrong - I bought a Bruno "Golden Edition" for $9 two years ago pre-release... and... I just don't use it. I'm not even sure why I keep it around, at 524.5 MB

    ...and... it's gone

    • That's an interesting point. I wonder if over the next X years consumers will free up ALOT of disk space by just using agents and not needing to download and install desktop software.

      Full disclosure, I'm building a desktop app called DB Pro [1] which is a modern desktop database client.

      We're still doing well, and selling a lot, but we're having to think about what the next 2/3/4/5 years look like...

      [1] https://dbpro.app

      3 replies →

By the time I decided I should maybe try postman, I was absolutely turned off that it wants you to setup an account (for what?).

Went with Insomnia instead (which IIRC also wants an account now?) and now just some text-mode VSCode http client.

When I saw the UI, my first thought was "is that written in Java"? And indeed, it is. Kinda funny that it's so easy to spot that language based on its horrible default UI skins alone.

Isn’t testing an API just more test cases that Claude toils through? Why do I care about milkman Bruno or postman.

Oof, outdated UI (website and platform).

No excuse for this in 2026 tbh - get Claude to implement a dark and light mode in tailwind and pick a colour theme. It doesn't mean the product is trash but it's a poor first impression.

  • In 2026, a website that hasn't been designed to match every other AI slopped up UI is a poor first impression?

    • Using tailwind != looking like an AI slopped UI. Did you know tailwind existed before ChatGPT?

      You can actually be involved in the design direction rather than just accept the first iteration and get rid of all that italic text.