head to head · open source
gofr vs kubeshark
gofr has 20,820 GitHub stars, 1,789 forks, 132 open issues and last shipped yesterday. kubeshark has 12,126 stars, 558 forks, 149 open issues and last shipped 2 days ago. gofr leads on adoption by 72% (20,820 vs 12,126 stars). gofr is written in Go under Apache-2.0; kubeshark is written in Go under Apache-2.0. gofr has attracted 9% as many forks as stars, kubeshark 5%. gofr was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (golang, grpc), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| gofr | kubeshark | |
|---|---|---|
| GitHub stars | ★ 21K | ★ 12K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Go | Go |
| Last push | 2026-11-02 | 2026-11-01 |
| Forks | ⑂ 1.8K | ⑂ 558 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick gofr if
- You weight community size — 21K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick kubeshark if
- You want the kubeshark feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and kubeshark fits your workflow better
About gofr
Go Fr GoFr: An Opinionated Microservice Development Framework Listed in the CNCF Landscape 🎯 Goal GoFr is designed to simplify microservice development , with a key focus on Kubernetes deployment and out of the box observability . While capable of building generic applications, microservices remain at its core. 💡 Key Features 1. Simple API Syntax 2. REST Standards by Default 3. Configuration Management 4. Observability (Logs, Traces, Metrics) 5. Inbuilt Auth Middleware & Custom Middleware Support 6. gRPC Support 7. HTTP Service with Circuit Breaker Support 8. Pub/Sub 9. Health Check for All Datasources 10…
About kubeshark
Network Observability for SREs & AI Agents Live Demo · Docs Kubeshark indexes cluster wide network traffic at the kernel level using eBPF — delivering instant answers to any query using network, API, and Kubernetes semantics. What you can do: Download Retrospective PCAPs — cluster wide packet captures filtered by nodes, time, workloads, and IPs. Store PCAPs for long term retention and later investigation. Visualize Network Data — explore traffic matching queries with API, Kubernetes, or network semantics through a real time dashboard. See Encrypted Traffic in Plain Text — automatically decrypt TLS/mTLS traffic…
read the full kubeshark overview →
More in Infrastructure & Operations
Related comparisons
More Monitoring & Observability projects
Compare either of these against the rest of the Monitoring & Observability field.
Frequently asked questions
Is gofr or kubeshark more popular?
gofr has 20,820 GitHub stars and kubeshark has 12,126. gofr has the larger community by that measure.
Are gofr and kubeshark free?
Both are open source. gofr is licensed under Apache-2.0 and kubeshark under Apache-2.0. Neither carries a licence fee.
What is the difference between gofr and kubeshark?
gofr is written in Go and kubeshark in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, gofr or kubeshark?
Choose gofr if you want the larger community (20,820 stars) or its Apache-2.0 licence terms. Choose kubeshark if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.