Apigee and Mulesoft went "enterprise." AWS API Gateway and GCP Endpoints kind of stagnated. Seems like the only option for small and medium-sized SaaS businesses that want to sell access to APIs is to roll their own or fully commit to RapidAPI. (Please let me know other options I am forgetting or not aware of!)
We currently "roll our own" using Kong, Auth0, and a Rails app. Not sure if we'd want to outsource all of those components. But will keep an eye on this option for the future, particularly for doing metered billing.
This comment encapsulates the inspiration behind Kable beautifully.
Developers I've spoken with have struggled to get up and running with AWS API Gateway or GCP Endpoints. They each had plans to evolve their pricing model based on business-specific metrics (like monthly active users, transactions processed, or requests to specific APIs), and they weren't able to get the per-contract or per-endpoint pricing flexibility out of these offerings that they wanted.
Kable's greatest strength is its usage metering and billing. Not every developer is going to need to outsource their entire API gateway, and that's alright. In the early days, this does help get to market faster. At scale, though, when billing becomes more and more complex, is where Kable's greatest strengths in billing shine.
Apigee and Mulesoft went "enterprise." AWS API Gateway and GCP Endpoints kind of stagnated. Seems like the only option for small and medium-sized SaaS businesses that want to sell access to APIs is to roll their own or fully commit to RapidAPI. (Please let me know other options I am forgetting or not aware of!)
We currently "roll our own" using Kong, Auth0, and a Rails app. Not sure if we'd want to outsource all of those components. But will keep an eye on this option for the future, particularly for doing metered billing.