Wait, so that list is things you WANT? To be honest it sounds like you've read what's on the back of the box of some proprietary integration platform sold by IB

Wait, so that list is things you WANT? To be honest it sounds like you've read what's on the back of the box of some proprietary integration platform sold by IBM in the 90s. It's a bit like when a vendor writes an RFP. You're not telling me anything about the problem you're trying to solve, you're giving me a list of solutions. Based on your list of features - let's think about what would be a good option.. 1. Less expensive Than what, a private jet? 2. Encourages collaboration between internal dev teams by connecting to active directory (or source of authentication & authorization) Authentication, pretty much every paid platform has this. Some take more setup. Where does your AD sit, if you're a Microsoft shop, Azure might serve the best products. Having said that, there's out-of-the-box integrations with AD with many major platform providers. Secondly, is this for internal access only - or is this AD environment also serving external users and partners? Maybe you're looking for AD integration because that's all you know to support RBAC. 3. Curation i.e. takes care of the lifecycle management i.e. design, arch. approval, development, test, release, production, versioning, monitoring, deprecation So you want an API platform product that supports the end-to-end SDLC in a single product? Why? What is the the "solution" to? Also you're asking for "approval", so you're expecting an API Manager Platform to also have a baked in release process.. But based on requirement 5 - you can't go with a single cloud vendor. 4. Compliance - PCI compliance and app management (generating clientIDs and secrets, rotation included) Any commercial or Enterprise provider will provide this, however if you're building a solution which touches card data - you're going to need to re-certify the end-to-end solution. Expect to pay an auditor for this. 5. Multi cloud-native OK, this is the first thing on the list that would actually be useful in driving you towards a decision. You want something you can download and host on a server. This takes away all SaaS options and really only leave self-hosted options. You've removed all cloud providers and all proprietary providers with this decision. There is only open-source (and NOT that bullshit "open-source heritage"). 6. Simpler UI/UX experience Than what, a TI-84 graphing calculator? 7. API based role access. All major cloud providers will have this well supported. However I'd likely set up SAML integration with an IdP, and outsource the authorization and administration of users and roles to a purpose-built stack or SaaS - and not some crappy afterthought implementation that'd been strapped on top of an API Manager product. Think Okta.