Frequently Asked Questions

Get answers to common questions about Cokpit, our AI-powered DevOps assistant

1. What is Cokpit and how does it help DevOps teams?

Cokpit is an AI-powered DevOps assistant designed to automate and simplify complex infrastructure and CI/CD workflows. It integrates with your cloud environments (AWS, GCP, Azure), Kubernetes clusters, CI/CD tools like Jenkins, and monitoring stacks to deliver natural language-based automation, RCA (Root Cause Analysis) and incident diagnosis, cost insights and billing breakdowns, knowledge base-driven compliance, and one-click actions via secure approval flows.

2. Is it multi-cloud compatible?

Yes. Cokpit supports AWS, GCP, and Azure out of the box. It can interact with services like EC2, IAM, S3, GKE, Compute Engine, AKS, etc., via both CLI and APIs.

3. How does it integrate with CI/CD tools like Jenkins, GitHub, or GitLab?

Cokpit integrates natively with Jenkins and supports generic pipelines from GitHub Actions, GitLab, Bitbucket, and more using its MCP (Model Context Protocol) interface. It can clone, edit, and run CI jobs via chat, fetch logs, diagnose failures across pipeline stages, and provide auto-remediation prompts.

4. Can it analyze logs and perform RCA?

Yes, especially for Kubernetes workloads using Grafana, Prometheus, and Kube-state metrics. Note: ELK (ElasticSearch, Logstash, Kibana) is currently not supported, but it's on the roadmap.

5. Is it self-hosted or SaaS?

Cokpit is a self-hosted product. It runs on customer infrastructure (VMs or Kubernetes), with no data leaving your environment.

6. Does Cokpit learn from previous failures?

Currently, Cokpit uses LLMs and knowledge base context to recommend solutions. A learning module for historical RCA is under development.

7. What security measures does it follow?

All actions are gated via human-in-the-loop approvals. Integrations use scoped IAM roles or temporary credentials. Secrets and credentials are managed via encrypted storage. No long-lived access keys are required if SSO is configured.

8. Can I integrate it with Jira or other ITSM tools?

Yes. Cokpit supports Jira and ServiceNow integration to trigger actions from tickets, automate resolution, and post updates.

9. How long does it take to deploy?

Deployment typically takes about 15–20 minutes and can run on a VM with 2 CPUs and 8 GB RAM. Helm charts and YAMLs are provided.

10. Does it support Docker image vulnerability scanning?

Partially: Can parse and analyze Dockerfiles for misconfigurations. Runtime image scanning is not yet available.

11. Can I define internal infra policies for Cokpit to follow?

Yes. You can use the Knowledge Base to define rules such as approved AWS regions, naming conventions, and Helm values. Cokpit follows these automatically when executing tasks.

12. Can we do a POC before buying?

Yes. A 15-day free guided POC is available with full infra setup support and help defining use cases.

13. What if I'm using a small DevOps team—will this still help?

Yes. Cokpit is ideal for lean DevOps teams (1–5 members), enabling automation, reducing MTTR, and improving safety for junior engineers.