Kong vs. Paw vs. Apigility

We're a small startup in San Francisco (team of 18 people). After spending lots of time building our core technology, it was time to bring it to life and deploy with several very large customers (500+ API requests/customer/minute).

We looked for a solid API management solution that would allow for easy authentication, quick installation and great logging features (requests and responses). After looking at various (very) expensive solutions out there, we ran into Kong.

After testing it for a few days, we deployed quickly to production to serve the needs of our customers. 3 weeks in, our experience has been great. Highly recommended to anyone who's looking for API management solutions.

P.s. Scored "Reliability" as "OK" for now with lack of data. Will definitely update once we've had Kong in production for a longer period of time.

Apigility is loyal to the standards; we do not need a framework to write custom REST APIs, anyone can do that; we need a framework that makes sticking with the standards easy.

Every PHP framework should be designed in such a way, that it forces you to think about what you are doing, the current PHP mind-set is too much crowded with lazy documentation of custom-solutions that do not work as expected (because the language gives you too much freedom).

With Apigility it is easy to build RESTful APIs in a declarative way, so that you do not need to write tests for every API Service you create, because the underlying code doesn't change or break, all functionality comes within the framework, that has already been tested.

You do not need to write any boiler plate code, which is huge plus compared to Symfony 2 and the likes.

Apigility has had some reliability problems with newest releases and as far as I know, they do not report which release is the latest stable. But of course, they reached the 1.0 in 2015.