varunjsr7

Ah! I see your point, Thanks for sharing your perspective. [I'm not 100% sure if you saw my response, apologies if this is repetitive] Below are a few differentiators than existing solutions

1. Less expensive, 2. Encourages collaboration between internal dev teams by connecting to active directory (or source of authentication & authorization), 3. Curation i.e. takes care of the lifecycle management i.e. design, arch. approval, development, test, release, production, versioning, monitoring, deprecation. 4. Compliance - PCI compliance and app management (generating clientIDs and secrets, rotation included) 5. Multi cloud-native 6. Simpler UI/UX experience 7. API based role access.

Fully understand that these feature sets may overlap with existing players.

Looks like we are saying the same thing :)

I 100% agree with your opinion and it makes total sense to go with minimal intermediaries! I'm trying to decipher your comment around "bypass APIs" - the webhook and event streaming arch. makes sense for any net new applications being built from now (or for the past few years).

A typical small to medium enterprise would still have hundreds of APIs (internal and external) that still need a platforms to take care of API lifecycle events. My follow-up question is as follows - Is there a market for another API management tool that is

1. Less expensive, 2. Encourages collaboration between internal dev teams, 3. Curation i.e. takes care of the lifecycle management i.e. design, arch. approval, development, test, release, production, versioning, monitoring, deprecation. 4. Compliance - PCI compliant and manage clientIDs and secrets (rotation included) 5. Be multi cloud-native