Which API Gateway to use?

I'm currently working on the design of a solution which requires an API gateway architecture. I'm confused whether to develop an API gateway from scratch or to use existing solutions(tyk,kong or wso2). Here are the requirements:

• API gateway can be called by different companies so tables within a database should be split by company
• Each company contains users so we need Authentication (username+password) and access control/roles : some users cannot access to certain routes
• Some backend services communicate with different protocols. For instance kong supports only REST therefore I think of discarding it
• API gateway will be deployed on premises. Therefore all cloud based solutions are discarded

Which solution can cover those requirements?

• OptionA: existing API gateway? ( If so then which one)
• Option B: develop our own API gateway from scratch

via Hopkins