Why another API tool?

As I built more complex applications, I noticed a pattern: every API has its own auth, rules, and formats. Setting up a full API Gateway like Kong felt like overkill for my needs.

I wanted a single tool to handle execution, authentication, and logging so my app only deals with business logic.

The Architecture (PoC Stage)

To validate the concept quickly, I built a synchronous MVP using: