4 messages
DevOpsNinja5 months ago
Kubernetes shouldn’t feel like juggling five tools just to ship one change.
Platform teams managing Kubernetes at scale are drowning in tool sprawl. Lens for visibility, k9s for speed, Flux CLI or ArgoCD for GitOps — but no single workflow that works for everyone. The result? Onboarding bottlenecks, visibility gaps, and constant context-switching.
The Solution
We are working on a new platform - called Kunobi - that unifies Kubernetes and GitOps management in one place. It keeps the speed and flexibility of the CLI, but adds just enough visualization so you don’t need to rebuild the entire mental model in your head every time.
Key Features
• GitOps-native control – FluxCD + ArgoCD with one-click sync, rollback, and drift detection.
• Unified topology view – Real-time map of deployments, pods, and secrets.
• Actionable resource management – Live statuses with quick actions (logs, shell).
• Collaborative, efficient UI – Keyboard speed plus GUI for teamwork.
If these pains resonate, we’d love your feedback—help us push Kunobi further before we launch more widely.
Join the Beta Program
We’re opening up early access to 100 platform teams. Beta testers receive:
• Full Professional access — free during beta
• Direct influence on roadmap & features
• Priority support via our Reddit community
• Early access to new GitOps & AI capabilities
Send a request here https://kunobi.ninja
Platform teams managing Kubernetes at scale are drowning in tool sprawl. Lens for visibility, k9s for speed, Flux CLI or ArgoCD for GitOps — but no single workflow that works for everyone. The result? Onboarding bottlenecks, visibility gaps, and constant context-switching.
The Solution
We are working on a new platform - called Kunobi - that unifies Kubernetes and GitOps management in one place. It keeps the speed and flexibility of the CLI, but adds just enough visualization so you don’t need to rebuild the entire mental model in your head every time.
Key Features
• GitOps-native control – FluxCD + ArgoCD with one-click sync, rollback, and drift detection.
• Unified topology view – Real-time map of deployments, pods, and secrets.
• Actionable resource management – Live statuses with quick actions (logs, shell).
• Collaborative, efficient UI – Keyboard speed plus GUI for teamwork.
If these pains resonate, we’d love your feedback—help us push Kunobi further before we launch more widely.
Join the Beta Program
We’re opening up early access to 100 platform teams. Beta testers receive:
• Full Professional access — free during beta
• Direct influence on roadmap & features
• Priority support via our Reddit community
• Early access to new GitOps & AI capabilities
Send a request here https://kunobi.ninja
Nat G.4 months ago
Hey folks 👋
The conversation around the impact of AI on developer velocity is shifting. Signadot’s CEO, Arjun Iyer, had a chat with David Cramer (Sentry) at Tech Week SF last week, and it sparked an idea: Is AI-generated code secretly creating a massive bottleneck for our validation infrastructure?
It feels like we're getting great at
Curious to hear how others are thinking about this challenge.
https://www.signadot.com/blog/what-sentrys-evolution-taught-me-about-the-future-of-development-velocity
The conversation around the impact of AI on developer velocity is shifting. Signadot’s CEO, Arjun Iyer, had a chat with David Cramer (Sentry) at Tech Week SF last week, and it sparked an idea: Is AI-generated code secretly creating a massive bottleneck for our validation infrastructure?
It feels like we're getting great at
code generation but the real tax on developer velocity is becoming code validation—long CI queues, flaky staging envs, etc. We put together some thoughts on how Sentry's evolution points to a future where pre-production testing platforms become critical.Curious to hear how others are thinking about this challenge.
https://www.signadot.com/blog/what-sentrys-evolution-taught-me-about-the-future-of-development-velocity
Nat G.4 months ago
Hi folks! I want to share one of our recent articles that tackles a problem many of us deal with every day: the shared staging environment.
If your team is constantly running into a "blame game" because someone's change broke the main test environment, you know how frustrating and slow that is. The old model of duplicating your stack is too expensive, but sharing it leads to painful bottlenecks. A better way to test is by using isolation to give every developer a personal, instant sandbox for their pull request. This eliminates the contention, speeds up testing dramatically, and removes a huge source of friction.
Check out the full analysis here: https://www.signadot.com/blog/the-staging-bottleneck-why-your-engineering-team-is-slow-and-how-to-fix-it
If your team is constantly running into a "blame game" because someone's change broke the main test environment, you know how frustrating and slow that is. The old model of duplicating your stack is too expensive, but sharing it leads to painful bottlenecks. A better way to test is by using isolation to give every developer a personal, instant sandbox for their pull request. This eliminates the contention, speeds up testing dramatically, and removes a huge source of friction.
Check out the full analysis here: https://www.signadot.com/blog/the-staging-bottleneck-why-your-engineering-team-is-slow-and-how-to-fix-it
DevOpsNinja4 months ago
Hey everyone, we just shipped something and would love honest feedback from the community.
What we built: Kunobi is a new platform that brings Kubernetes cluster management and GitOps workflows into a single, extensible system, so teams don’t have to juggle Lens, K9s, and GitOps CLIs to stay in control. We make it easier to use Flux and Argo by enabling seamless interaction with GitOps tools. We’ve focused on addressing pain points we’ve faced ourselves - tools that are slow, memory-heavy, or just not built for scale.
Key features include:
• Kubernetes resource discovery
• Full RBAC compliance
• Multi-cluster support
• Fast keyboard navigation
• Helm release history
• Helm values and manifest diffing
• Flux resource tree visualisation
Here’s a short demo video for clarity.
Current state: It’s rough and in beta, but fully functional. We’ve been using it internally for a few months.
What we’re looking for:
• Feedback on whether this actually solves a real problem for you
• What features/integrations matter most
• Any concerns or questions about the approach
Happy to answer questions about how it works, architecture decisions, or anything else. https://kunobi.ninja — download the beta here.
What we built: Kunobi is a new platform that brings Kubernetes cluster management and GitOps workflows into a single, extensible system, so teams don’t have to juggle Lens, K9s, and GitOps CLIs to stay in control. We make it easier to use Flux and Argo by enabling seamless interaction with GitOps tools. We’ve focused on addressing pain points we’ve faced ourselves - tools that are slow, memory-heavy, or just not built for scale.
Key features include:
• Kubernetes resource discovery
• Full RBAC compliance
• Multi-cluster support
• Fast keyboard navigation
• Helm release history
• Helm values and manifest diffing
• Flux resource tree visualisation
Here’s a short demo video for clarity.
Current state: It’s rough and in beta, but fully functional. We’ve been using it internally for a few months.
What we’re looking for:
• Feedback on whether this actually solves a real problem for you
• What features/integrations matter most
• Any concerns or questions about the approach
Happy to answer questions about how it works, architecture decisions, or anything else. https://kunobi.ninja — download the beta here.