One developer portal for multiple API gateways
We are researching what would be the best solution for the community. If you are interested in an open source gateway connector project, as a user or collaborator, you can help us organize a better project by filling out our questionnaire.

Sign in to Google to save your progress. Learn more
Email *
Who will see the information you submit?
Raw data, resulting from this questionnaire, will be used by Pronovix for researching the needs of API program teams looking to use one developer portal for multiple API gateways. The research contributes to our research and publication of reports and articles to inspire the community as a whole on how to improve their developer portals. With your permission, we may reach out to you for a deeper dialogue on the topic being researched.
Help us understand your situation and needs
We would like to understand which gateways and API management systems you use and how they are used internally versus externally via your developer portal.
What API gateway(s) or API management system(s) do you use?
In Use
Live connected to devportal
In house built
Apigee
AWS
Axway Amplify
CA Broadcom
Dell Boomi
Gloo
Goku
Google Cloud Endpoints
IBM API Connect
Kong
KrakenD
Microsoft Azure
MuleSoft
Ocelot
Oracle Cloud Infrastructure
Perforce Akana
RedHat
SAP
Senisedia
Tyk
WS02
Other
Please provide us with details if you chose 'Other'.
How many gateways do you have in your IT infrastructure? (For example, 3 instances of Apigee gateways) *
Do you use a different gateway for your internal and external APIs? If so, can you explain which ones and why? *
What kind of key provisioning or access control do you need in your portal? *
Required
Please provide details. *
How do you see a benefit to separating a gateway connector from the developer portal? *
Assuming that there is a community maintained protocol definition (like in an OpenAPI spec), would you prefer to use an open-source gateway middleware implementation or build and maintain your own in your developer team’s preferred language? If so, can you explain why?
What API gateway features are a must have, and can’t be sacrificed for the sake of interoperability? *
Required
Keep in touch
Please provide us with your contact information.
Name *
Organization *
Do you want to stay informed about this initiative? *
How do you want to contribute to this project? *
Required
A copy of your responses will be emailed to the address you provided.
Submit
Clear form
Never submit passwords through Google Forms.
GoogleForms
reCAPTCHA
PrivacyTerms
This form was created inside of Pronovix.