ArkChat: ask Ark about your infrastructure, see how it answered
Questions answered from your live platform data, not from general knowledge, with the query path shown so the answer can be checked rather than trusted.
What is ArkChat?
ArkChat is the conversational interface to DevOpsArk that answers questions about your own infrastructure (clusters, services, deployments, incidents, cost and security posture) using live platform data, and shows the steps it took to produce each answer.
What ArkChat is for
The conditions this module removes. If none of these are familiar, you probably do not need it yet.
- Answering "which services are affected by this CVE" means opening four consoles and joining the results by hand.
- Only two people know the query language well enough to get answers quickly.
- General-purpose assistants know Kubernetes but know nothing about your clusters.
- During an incident, the person who can find the data is the bottleneck.
- An answer from a model that cannot show its working is not usable for an operational decision.
ArkChat resolves a question into queries against the DevOpsArk data model (the application catalogue, cluster inventory, metric and log stores, deployment history, cost allocation and security findings), and answers from the results. It does not answer infrastructure questions from general model knowledge, because general knowledge does not contain your cluster. Every answer is accompanied by the execution trace: which queries ran, against which sources, and what they returned, so the answer can be verified rather than trusted. Where an action is possible, ArkChat proposes it as a plan with an explicit scope and asks for approval; it does not execute a change because a sentence sounded like a request. Access follows the asking user own permissions, so ArkChat cannot reveal data the person could not otherwise see.
What ArkChat does
The 7 capabilities that make up ArkChat.
Answers from your data
Questions resolve to queries against your live inventory, metrics, logs, deployments, cost and findings, not to general knowledge.
Visible execution trace
Every answer shows the queries that produced it and what they returned, so it can be checked.
Proposed plans, not silent actions
Where an action is possible it is proposed with explicit scope and requires approval before anything runs.
Permission-scoped
ArkChat answers within the asking user own access. It cannot surface data the person is not entitled to see.
Incident companion
During an incident, ask for the recent deployments, the correlated alerts and the matching log patterns in one place.
Works where you work
Available in the DevOpsArk console and in the chat tools your team already uses.
Audited conversations
Questions, the queries they generated and any approved actions are recorded.
How ArkChat fits together
Outcomes
- Infrastructure questions are answerable by anyone on the team, not only the two people who know the query syntax.
- Answers can be verified, which is what makes them usable operationally.
- Incident data gathering stops being a bottleneck.
- Nothing changes without an explicit approval.
- Access control is preserved rather than bypassed by a convenience layer.
Using ArkChat, step by step
The path from connecting a source to getting value, in the order it happens.
- 1Ask
Put the question in plain language from the console or a chat tool.
- 2Plan the query
ArkChat resolves the question into queries against the platform data model.
- 3Filter by permission
Results are limited to what the asking user is entitled to see.
- 4Answer with a trace
The answer is returned alongside the queries and results that produced it.
- 5Propose an action
Where a change is possible, it is proposed with scope and requires approval.
Where teams apply ArkChat
Gather incident context fast
Ask what deployed in the last hour, which alerts correlate and what the logs show, in one exchange.
Scope an advisory
Ask which services ship an affected library and which of them are internet-reachable.
Get an answer without a ticket
Ask what a team spend was last month, or how many services are missing resource limits.
Learn the estate
Ask what a service depends on and where it runs, and get an answer drawn from the live system.
What ArkChat works with
Named integrations link to their own page. The rest are supported runtimes and formats.
ArkChat: frequently asked questions
The 8 questions teams ask most often before adopting ArkChat.
ArkChat is the conversational interface to DevOpsArk. It answers questions about your own infrastructure using live platform data, and shows the queries it ran to produce each answer so the result can be verified.
Not for questions about your environment. Those resolve to queries against your inventory, metrics, logs, deployments, cost and findings. General model knowledge is used to interpret the question, not to invent the answer.
Only through an explicit approval. Where an action is possible, ArkChat proposes it as a plan with its scope stated, and nothing executes until a person with the right permissions approves it.
No. It answers within the asking user own access. If you cannot see a namespace in the console, ArkChat will not report on it for you.
Because an operational decision needs a verifiable answer. The trace lists the queries that ran, the sources they hit and what they returned, so you can confirm the answer rather than trust it.
In the DevOpsArk console and in the chat tools your team already uses, so incident conversations can stay in one place.
Yes. Questions, the queries they generated and any approved actions are written to the audit trail, which matters for both incident review and compliance.
No. Your environment data is used to answer your questions. It is not used as training data.
See ArkChat against your own environment
A 30-minute walkthrough with a platform engineer, not a sales deck. Bring a cluster and a problem.