I was confused by the first chart where they cropped off the Y-Axis label.

I thought the X-Axis was "# of people at the company" and the Y-Axis was "# of developers". That wouldn't make sense because the "less than 10" person company would have "16.40" developers!

I found the survey they mentioned. The Y-Axis is "Number of Internal APIs" which makes much more sense. https://rapidapi.com/blog/rapidapi-developer-survey-insights...

Ah good catch! I have updated the graphic to not cut off the left axis label. Thanks.

How does this compare to Cilium's Hubble?

Can you host the dashboard and data storage yourself or is it only accessible as a hosted SaaS product (free or otherwise)?

Hello, Jean here from Akita.

Akita is lighter weight in terms of install and setup than Cilium's Hubble and will get you to insights more quickly. With Akita, it's easier to have a single dev use Akita and get visibility across many services. Cilium's Hubble is more of a power tool: it will give you more different kinds of data, which can be quite useful for people who are looking for that.

Akita is currently only accessible as a hosted SaaS product (with a free tier).

You don’t need SYS_PTRACE to really do this? Or is it only observability for the network alone?

Right now it's only based on network packet capture, not tracing the application itself. For packet capture we need CAP_NET_RAW, not SYS_PTRACE.