When comparing Koa vs Strapi, the Slant community recommends Strapi for most people. In the question“What are the best backend web frameworks?” Strapi is ranked 32nd while Koa is ranked 33rd. The most important reason people chose Strapi is:
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Generator support from ground up
Using generators (a bleeding edge feature, even for Node.js) would clean up your code from the mess caused by all those callbacks; making your code more manageable.
Pro Extremely lightweight
Koa is very lightweight with just 550 lines of code.
Pro async/await keywords are supported and has transcended beyond generator functions
Generators functions are of course a huge plus, but at the time Koa team has transcended generations functions and shifted towards async/await style programming. It has made the Koa best framework available in the market.
Pro Development team has a proven track record
Koa is developed by the team behind a widely used node.js framework (express.js).

Pro Built for ES6
Pro Auto-generate REST APIs
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Pro Users, groups and permissions
Manage user settings, login, registration, groups and permissions on the fly. Strapi delivers all those essential features out-of-the-box.
Pro Out-of-the-box administration panel
Easy way to manage your application. This panel allows you to add/edit/delete entries for your APIs, manage your users, groups and permissions. In the future, it will be such as WordPress-like administration panel dedicated to your application.
Cons
Con Community is relatively small
Con Not compatible with express style middleware
Koa uses generators which are not compatible with any other type of Node.js framework middleware.
Con Has no routes separated by HTTP method or URL pattern
Con Wrong Middle ware, security issue
