Skip to content
← Tools / Skills
ToolKubiya/10 trustMetrics-checked

Kubiya

AI agents for DevOps that run Terraform, restart pods, and triage incidents from Slack.

Visit official site →

About

Kubiya is an agentic platform for DevOps and platform teams: task-aware agents execute real operations like restarting Kubernetes pods, running Terraform plans, or provisioning staging environments, mostly through Slack or CLI. Every action is gated by role-based access control, logged for audit, and can require manager approval, with just-in-time access grants for production. Agents keep persistent memory of your infrastructure context, and the Agent Development Kit turns plain-English descriptions into deterministic, reviewable workflows. It is enterprise-focused and DevOps-scoped, so it is overkill outside infrastructure work.

What it can do

  • Slack-native DevOps agents
  • Kubernetes pod restarts and log triage
  • Terraform plan and apply execution
  • Incident escalation with Jira and PagerDuty
  • Interactive manager approval gates
  • Just-in-time temporary production access
  • RBAC with full audit logging
  • Custom agents via Python and Bash
  • Persistent memory across sessions

Setup

  1. Create an account at kubiya.ai.
  2. Connect Slack or Teams plus your cloud and Kubernetes accounts.
  3. Deploy a Kubiya Runner inside your cluster for in-VPC execution.
  4. Chat with agents to run operations; set approval gates for destructive actions.

Prerequisites

A Kubiya account; Slack or Teams; Kubernetes or cloud infrastructure access.

Use cases

automationagentscode

Works with

Any agent (.md)

Trust score — 6/10

/10 trustMetrics-checked

Scored 6/10 (metrics tier, metrics-v1). Evidence: Niche but real adoption among platform/DevOps teams; enterprise-focused positioning.; Actively developed: Agent Development Kit, deterministic workflows, OTLP/Prometheus observability.; Closed-source commercial platform; no public repository.; Honest caveat: DevOps-only scope and enterprise complexity make it overkill outside infrastructure teams.. License: Proprietary SaaS; no public source license..

How the trust score is built

Full methodology →
Adoption · stars/downloads, log-scaled vs peers
6.0/10
Maintenance · recency, releases, issue load
7.0/10
Openness · license + docs
2.0/10
Manual review · sanity read + red-flag check
6.0/10
  • · Niche but real adoption among platform/DevOps teams; enterprise-focused positioning.
  • · Actively developed: Agent Development Kit, deterministic workflows, OTLP/Prometheus observability.
  • · Closed-source commercial platform; no public repository.
  • · Honest caveat: DevOps-only scope and enterprise complexity make it overkill outside infrastructure teams.

Sources

Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.