I trusted “the most popular API tool for developers.” I kept it updated, cleared cache when asked, stayed logged in — played by the rules. And what did I get? After some silent update (or maybe their backend just got bored), Postman cheerfully greeted me with:
“This wasn’t supposed to happen. How about a fresh start?”
Wow. Thanks. Especially for not mentioning that my data isn’t really mine. That “sync” isn’t a backup—it’s a gamble: win and see your collections, lose and start from scratch.
I didn’t ask for a social network for APIs. I asked for a tool. Instead, I got a SaaS slot machine that wipes weeks of work with a single server hiccup.
If you’re building your workflow around Postman—know this: you’re not a user. You’re a temporary custodian of data that can vanish at any moment “by accident.”
P.S. No, I didn’t export. Because I trusted you. Stupid? Maybe. But not as stupid as building a stateful developer tool with no reliable local persistence and calling it a “developer experience.”
UPD: Got the official response. This is due to an AWS outage affecting Postman’s internal services.
Totally get it. Cloud happens.
But here’s the thing: I trusted Postman as a local API client. Turns out, it’s a SaaS that just looks local. When your “tool” can vanish because of someone else’s infrastructure failure — it’s not a tool, it’s a dependency.
So I’ve migrated to Bruno - local-first, file-based, Git-friendly, zero cloud surprises.
To Postman team: your UX is great, but please bring back a real offline mode. Until then, my collections stay on my disk, not in AWS limbo.
P.S. Still salty about the “fresh start” message. That’s not an error, that’s a design choice.
