Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free
Promoted
Reqly
rest-client privacy-first postman-alternative
13 followers
rest-client privacy-first postman-alternative
13 followers
A lightning-fast, privacy-first desktop REST API client. Built with Wails, Go, and React.
✨ Core Principles
1. 🔒 Data Safe & Private — Your API keys, tokens, and data stay strictly on your local machine. Nothing is ever sent to 3rd party cloud servers.
2. ⚡ Just Call HTTP — A minimal, clean, and intuitive interface designed to execute requests without getting in your way.
3. 📜 History & Re-run — Automatically save your request history and click to re-run past requests instantly.
4. 🏷️ Tags for Filtering — Organize your workflows with custom tags and filter your history blazingly fast.
5. 📥 Parse Import — Paste pure `cURL` commands or `.http` entries, and Reqly will parse them right into the builder.
Native support for WebSocket and gRPC testing would round this out perfectly, since most REST clients end up needing those eventually. Also curious if you're planning team sync or shared collections, since that tends to be the next thing people ask for once they get hooked on a new client.
@remziye6uti You’re speaking our language! WebSockets and gRPC are definitely on our radar as we expand beyond pure REST.
The team sync question is a fascinating challenge for us. Because Reqly is strictly privacy-first and local-only (using a local SQLite DB), we want to avoid building a mandatory, bloated cloud backend. We’ve been brainstorming git-friendly collection exports or local folder syncing so teams can share workflows via their own repositories.
How does your team currently share API collections? Do you prefer a centralized cloud, or would a Git-based file approach fit your workflow?
Love the speed and the privacy focus, this is basically what I've been wanting from a desktop client. One thing that would make it way more useful for me though is built-in environment variables and the ability to share request collections between teammates, like through a simple json export or import. That would honestly put it ahead of the alternatives for me.
@huriyeyr8y Thank you so much! That is incredibly validating to read. You’ll be happy to know that environment variables are already high up on our immediate roadmap—we completely agree that they're essential for handling different stages and tokens without losing your mind.
Your suggestion for a simple JSON export/import for collections is spot-on, too. It fits perfectly with our local-first philosophy because it means teams can easily share files via Git or Slack without us forcing you to create a cloud account. We're definitely prioritizing this!
The choice to go native with Wails and Go instead of another Electron app is refreshing, especially for something that handles sensitive API tokens. The speed difference is immediately noticeable compared to the bloated clients I'm used to.
@farukalayemdm Thank you! Honestly, moving away from the standard Electron playbook was a deliberate choice. We wanted something that respects both your RAM and your privacy. Wails + Go allowed us to build a truly native experience where your sensitive data never leaves your machine.
Out of curiosity, what’s the biggest 'bloat' feature in your current client that you’re happiest to leave behind?
Snappy launch and the Go backend really shows in how quickly requests fire off. Wish the response viewer had better diffing between requests, but overall feels like Postman without the bloat.
@tturan98497 Wow, 'Postman without the bloat' is exactly what we pinned on our virtual mood board when starting Reqly! The Go net/http engine really gives it that raw speed.
Also, you hit the nail on the head with the response diffing feature. That is a fantastic idea and makes total sense for debugging rapid API changes. How would you ideally like to see it visualised? Side-by-side text diffing, or just highlighting changed values/headers? Would love to get your thoughts so we can sketch it into the roadmap!
Runs way snappier than Postman on my M1, and I genuinely appreciate that nothing leaves my machine. The Wails setup shows.
@avlarsezer81295 Great to hear it’s playing nice with your M1! One of the biggest wins for us with Wails was getting that tight, native performance without the overhead of heavy frameworks. Keeping your tokens and requests strictly local was our #1 rule from day one, so I'm really glad that resonates with you.
Anything in particular you’ve found that makes the workflow feel different compared to what you were using before?
finally a desktop rest client that doesn't feel like it was held together with electron, the startup is genuinely instant and my collections actually load fast
@seluk741047 thank you for your comment, 'held together with Electron' hits close to home—that’s exactly the feeling I wanted to escape! Using Wails and Go for the backend has been a game-changer for collection load times, so it’s awesome to hear you’re seeing that speed in your own workflow. Since you've got collections loaded up, is there a specific feature you find yourself reaching for most often in Reqly?