11–20 of 51 posts
Earlier quoted context omitted.
That relation is not on purpose, we found that after we decided on a name. We went through the list of islands on Wikipedia and changed some letters (and even forgot on which island the name Kreya is based on).
I think you are based in Germany. Was it https://de.wikipedia.org/wiki/Kreta ?
We are based in Switzerland
The app consists of a closed-source binary, so not different from Postman in this regard. Telemetry is opt-out and the gathered data points don't seem problematic to me: https://kreya.app/docs/telemetry/
Regarding telemetry, we are very open about what we collect and only use anonymized data.
This looks very similar to Insomnia[0]. How does Kreya compare with it? It also supports generated data, environments, references, and expiring references which might trigger a different http call to get a new value for them. [0]: https://insomnia.rest/
Some of the differences are the more complete gRPC support, how API authentication is handled and how the project data is stored.
I like that the product page has comparisons to Postman, Insomnia etc on the bottom, but it could be more on point (e.g. a table). Overall it looks quite well done, although personally I don't have a real reason to use it over Insomnia.
We can't deny that Insomnia is a pretty good product :) It has its pros and cons compared to Kreya.
The app consists of a closed-source binary, so not different from Postman in this regard. Telemetry is opt-out and the gathered data points don't seem problematic to me: https://kreya.app/docs/telemetry/
Yes, Kreya is closed source. We explain our reasons in https://kreya.app/blog/why-kreya-isnt-open-source (which got us mixed responses). Regarding telemetry, we are very open about what we collect and only use anonymized data.
1. Variables / Dynamic Variables
2. GraphQL introspection
3. Pre/Post request scripts
4. Collection Runner
Postman is pretty expensive for larger teams.
That makes it horrible to collaborate because then you’d just be sharing giant JSON files which can easily go out of sync between multiple people.
I have no idea what postman (or gRPC) is. Could you add a short explanation in your post?
> Postman is a scalable API testing tool that quickly integrates into CI/CD pipeline. It started in 2012 as a side project by Abhinav Asthana to simplify API workflow in testing and development.
I have a love - hate relationship with Postman. Mostly because it’s super slow to use. I’ve been trying to find an alternative for long. But Postman has some nice things which it does really well. 1. Variables / Dynamic Variables 2. GraphQL introspection 3. Pre/Post request scripts 4. Collection Runner Postman is pretty expensive for larger teams. That makes it horrible to collaborate because then you’d just be shari…
GraphQL may be supported in the future, but we currently plan to expand the core features of Kreya first.
Regarding collaboration, we explicitely designed the Kreya storage model to be easily syncable via git (or your favorite VCS).
https://docs.servicestack.net/api-explorer
I'd still use Postman for testing 3rd Party APIs, but it provides a subpar UX for calling our own APIs which we can provide a better optimized UX around our USP features, e.g. the "Code" tab walks end user API consumers through how they can easily call each typed API in 9 different supported languages:
I have no idea what postman (or gRPC) is. Could you add a short explanation in your post?
gRPC is a Remote Procedure Call framework