HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
getezy
ezy
TypeScript2022–2023
getezy / ezy

ezy

🔥 GUI client for gRPC/gRPC-Web

Developer ToolsWeb DevelopmentMobile & DesktopTesting & QualityNetworking
Explore on GitHubRead Hacker News discussions
3Distinct people
11Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🔥 GUI client for gRPC/gRPC-Web

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month11 dated mentions

Observed mentions: 2022-08-16 10:41:55 UTC to 2023-11-09 13:35:36 UTC.

012342022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsAug 20222022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 20232023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC220
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC211
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC413
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC110
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC000
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC101
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC101

What Hacker News says

11 sources
typosaur·Sep 29, 2023
Do you have a plan to maintain it long-term or is it just a fork in sake of a fork? Other than that, for UI/manual testing I'd recommend Restfox or Bruno and ezy for gRPC. Hurl and Step CI for automated testing Restfox: https://github.com/flawiddsouza/Restfox Bruno: https://github.com/usebruno/bruno ezy: https://github.com/getezy/ezy Step CI: https://github.com/stepci/stepci Hurl: https://github.com/Orange-OpenSource/hurl Upd: added links
In Insomnium – Local, privacy-focused fork of Insomnia API client
notmedia·Feb 7, 2023Submission

Show HN: Ezy’s universal, extendable, typesafe gRPC/gRPC-Web client library

While working on ezy (https://github.com/getezy/ezy) - open-source alternative to Postman and Insomnia, I had requests to move the gRPC client into independent library which users can use in their projects and get the same behavior like in ezy. The idea was to create extendable client as much as possible. You just need to pass strategies of protobuf definition loader and gRPC protocol implementation to the client factory and then make your requests! Out of the box it supports gRPC and gRPC-Web protocols, loader by protobuf file. Also loader by server reflection is coming soon. Typesafe and well-tested - 99% coverage. Give it a try!
3 points · Open discussion
notmedia·Dec 8, 2022
> No, I had a proto file which imported another proto file, which could not be found, because I had not added its path to the import path list. Seems like it would be a common enough issue. Ah, this make sense. I agree that this could be a common issue while importing a protobuf. I will fix this in next release :) > Something like Grip, maybe: https://gripgrpc.dev/. Got it, we have a related discussion here -https://github.com/getezy/ezy/discussions/29 I will think how to show it, thank you! > Appears to be related to the number of tabs. If I have only one tab open, it's not particularly laggy. The main problem here is persistance (saving all data on the disk), and this make performance problems. I have plans to rewrite this section to improve it. > Click on an endpoint. It always opens a new tab. I think I need to create a poll :) Some u
Read the rest
sers saying that they want to open new tab by one click, others wants double click. And here I really don't know whats the better way of UX should be.
In Show HN: Ezy – open-source gRPC client, alternative to Postman and Insomnia
notmedia·Dec 8, 2022
Hi! Thank you for testing! > It doesn't remember your "environment". So if I call endpoint A and then click on endpoint B to try that, it forgets which environment is being targeted. Similarly, metadata is also specific to the request. If you use metadata for providing authorization headers, that means you have to enter the metadata separately every time you make a different request; there's no way to share metadata as an "environment". Yeah, I have this in plans for taking environment and Metadata from previous tab - https://github.com/getezy/ezy/issues/30 > If you create a collection and click "Create", and it errors saying an imported proto resource wasn't found, the entire collection disappears. Ha, interesting case, you selected the file and then just delete it before clicking create :) I will think how to handle this. > The app uses
Read the rest
the proto schema to show a list of endpoints, but it doesn't know anything about the message and response schemas, and you can't browse the types? It seems tedious to have to manually enter the request as a JSON payload. This is the great point, was already mentioned earlier, I have plans to add auto-mocking feature for request payloads and autocompletion in code editor this will fix this issue. Also I will think for option to show raw Protobuf definitions > Similarly, response is shown in JSON, rather than Proto data. So I can't see what the returned types actually are. Maybe you have an idea on how we can represent decoded message (which an object) and map it to Protobuf Message definition? > The "Request" and "Metadata" editors are super laggy to the point of being unusable. It takes several seconds for what I type to appear in the editor, and my computer's CPU usage goes to 150% while it's sitting there doing nothing. Is there some kind of autocompletion that's supposed to kick in that's going into overdrive? Interesting, this is the first feedback about app performance. Can you open an issue and put more details there? I need to know app version, your OS, how much tabs opened and how much are you typing. Will be helpfull, but I try to reproduce it anyway. > Clicking on an endpoint adds another tab. Click around and you end up with dozens of tabs. Seems a bit pointless. Sorry, I can't reproduce this bug. You said clicking around, where exactly I need to click? > No support for setting HTTP headers or seeing the returned headers. You can set it in your Metadata and this should work as expected.
In Show HN: Ezy – open-source gRPC client, alternative to Postman and Insomnia
notmedia·Dec 8, 2022Submission

Show HN: Ezy – open-source gRPC client, alternative to Postman and Insomnia

In this release I have concentrated on user experience: - Full support of shortcuts - Reworked collections management - Notifications - Improved UX gRPC clients I’ve worked with had drawbacks and didn’t fit my use-case in a way I was expecting, since I’ve started working with gRPC 3+ years ago. Since then, I wanted a tool that fits any need in gRPC world. This is why I created ezy. Compared to Insomnia and Postman, ezy offers better streams support, allows you to use Server-Side and Mutual TLS with custom TLS certificates, works with gRPC-Web and has a more slick UI/UX. If you are looking for a gRPC/gRPC-Web client which fits your needs, give ezy a chance! I’d love to hear your feedback and answer any questions regarding ezy.
155 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.