Insomnia
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
A side-by-side editorial comparison of Casdoor and Kubeshark — release velocity, themes, recent moves, and the top alternatives to consider.
Casdoor is turning single-tenant SSO into per-organization governance, one small release at a time
Casdoor ships multiple tagged releases a week, each carrying one or two commits, with version-only titles that hide the work. The current cluster is governance plumbing: configurable record and token retention per organization, auto-revoking permissions after an expiry window, and a batch UpdatePermissions API that cuts how often the Casbin enforcer rebuilds. Alongside it runs steady OAuth/OIDC conformance work — RFC 8707 resource indicators preserved through fast auto-signin, a backchannel logout URL on the application edit page.
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
Casdoor ships multiple tagged releases a week, each carrying one or two commits, with version-only titles that hide the work. The current cluster is governance plumbing: configurable record and token retention per organization, auto-revoking permissions after an expiry window, and a batch UpdatePermissions API that cuts how often the Casbin enforcer rebuilds. Alongside it runs steady OAuth/OIDC conformance work — RFC 8707 resource indicators preserved through fast auto-signin, a backchannel logout URL on the application edit page.
The center of gravity has moved from 'can users sign in' to 'can an operator govern what happens after they do.' Retention windows, permission expiry, and rename-safe Casbin group rules are all multi-tenant administration concerns, and each is being made configurable per organization rather than per deployment. The Casbin enforcer rebuild cost surfacing as its own fix suggests these installs are getting large enough for permission-model performance to matter.
Expect more per-organization lifecycle policy knobs and continued work on Casbin enforcer performance, since both themes have produced several releases in the last week alone.
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
The product is moving down the stack. It started as an API-level traffic viewer and the recent work is all about L4 — connectivity maps, raw PCAP export, mapping L7 calls onto the connections beneath them — which puts it closer to a cluster-wide packet capture tool than a service-mesh observability dashboard. The licensing is moving in the opposite direction of the feature set: an almost-unlimited complimentary licence through the end of 2025 was replaced by one capped at 100 nodes, so the free tier is being defined rather than left open. Two releases also mention agentic infrastructure being staged but not yet usable.
Expect V2 to consolidate onto the new backend and the legacy V1 path to be dropped once the transition completes, since the release notes already describe V1 as being sunset. The staged agentic infrastructure is the most likely candidate for the next substantive feature, given it has been shipped inert twice.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Casdoor or Kubeshark.
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
See all Casdoor alternatives → · See all Kubeshark alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Casdoor is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Casdoor is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.
Top Kubeshark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kubeshark alternatives" section above for the current picks, or visit /alternatives/kubeshark for the full list with editorial commentary on each.