The problem we saw

There are 100 API gateways. They all route traffic. They all apply policies. They all log requests. None of them understand anything.

Ask any gateway: "Why is the payment API slow?" You get dashboards. Latency charts. Log entries. You, the human, correlate, diagnose, and fix. That takes hours. Sometimes days.

We asked: what if the platform itself could answer that question? What if it knew that the checkout service depends on the inventory service, which depends on a third-party AI API that just hit its token budget, causing cascading retries?

That question requires a knowledge graph, not a database with foreign keys. So we built one.

Our principles

What we believe

APIs deserve intelligence, not just routing

Every API request builds a picture. After a week, the platform knows more about your infrastructure than your team does. That compounding intelligence is the product.

Open source is trust, not a marketing trick

The gateway core is Apache 2.0. No bait and switch. No paywalled security. No surprise licensing. We earn revenue from intelligence, not from locking down basics.

One platform, not six tools duct-taped together

Platform engineers manage APIs across 6-7 disconnected tools. We replace the stack with one platform where everything shares the same data model.

By the numbers

Built for production from day one

738K+
Requests per second
Go
Single language stack
Apache 2.0
Open source license
CNCF
Sandbox submission planned

Want to work with us?

We are building a small, focused team. If you care about developer tools, API infrastructure, or knowledge graphs — we want to hear from you.