Kreya 1.10 is out with some important changes, including a CLI and operation tabs. Many other features like a history of operations and path variables for REST operations were also implemented. And of course various bugs have been fixed in this version.
What a year! Almost two million operations were invoked with Kreya. To be exact, there were 1,992,648 tracked invoked operation events, of which 15,382 (0.77%) were REST operations. Many more numbers and insights can be found in this article.
The BloomRPC GitHub repo just got archived. BloomRPC was one of the earliest gRPC GUI clients, but has not received any updates in nearly two years.
Kreya 1.9 is here :partying_face:. This time with a small release. Just a few new features, but an important macOS bugfix.
It has been more than half a year since Kreya released a new version. Now Kreya 1.8 is here with many new features. Kreya now supports REST APIs, scripting and tests 🚀. We also introduced a Pro and Enterprise plan. Don't worry, almost all features are still available in the free version of Kreya.
One question we are often asked is why Kreya is not open source. We explain our thoughts and considerations in this blog post.
At the beginning of 2021, the first release of Kreya was published. Since then, many more releases have been added and more and more users are actively using Kreya. In this article, we give you an insight into our current telemetry data and briefly summarise the year 2021.
Creating and using gRPC services is pretty easy. However, there are a few gotchas and best practices that should be known to all. For example, do you know the default message size limit? Or do you know that protobuf supports optional fields since v3.15? Or that enum names should be unique inside a protobuf package?
If you don't know the answers to these questions, then this blog post is exactly for you.
Kreya 1.7 introduces generating fake data, referencing authentication configurations, adds a new light theme and other useful changes.
How many users use Kreya? How many requests are sent each day? Why do we collect this information? These and more questions we want to answer in the following blogpost and give you a detailed insight in our telemetry data.