Congrats on your launch. Your site was a little light on details. Could you say how your product compares to Pixie which is also Kubernetes-native and uses eBPF?
The initial version of ContainIQ is in a similar space to what pixie has built, but our eventual vision has a few differentiators. I believe Pixie was built using BCC (an assumption based on the 2GB requirement and their BPF trace tooling) which requires llvm and the kernel headers to be installed on every node. This ends up requiring a lot of ephemeral storage. Since Kubernetes is most commonly used for stateless applications this ends up being a problem, because the default node storage allocatable is relatively low. We’re in the process of migrating out from BCC to libbpf which should alleviate a lot of the issues associated with the larger storage/memory footprint of BCC. We also have a few unique features in the pipeline that I believe are unique to our product (EX: P95, P99 http latency by microservice endpoint).
https://pixielabs.ai/