> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis/verification-and-next-steps.md).

# Verification & Next Steps

## **Confirm Everything Works**

Run these commands to verify your complete setup:

```bash
# Check all infrastructure components
kubectl get nodes -o wide
kubectl get pods -A
helm list -A

# If you used Terraform/OpenTofu (Path 2), verify outputs
terraform output
```

## **Start Using Konvu**

Your on-premise deployment is now operational. Here's what each component does:

**Broker**:

1. **Discovers repositories** from your GitHub organization
2. **Syncs vulnerability data** from GitHub Dependabot
3. **Generates secure tokens** when needed for repository access
4. **Tracks commit activity** for risk assessment

**Controller**:

1. **Polls for analysis jobs** from your Konvu organization
2. **Executes security scans** on your code repositories
3. **Generates AI-powered triage** and remediation guidance
4. **Reports results** back to the Konvu platform

## **Configure Your Scanner Integration**

Connect your existing security tools to Konvu. See [Import Your Findings](/konvu/get-started/bring-in-findings.md).

## **Monitor Your Deployment**

Keep an eye on both components:

```bash
# Stream controller logs
kubectl logs -n konvu-controller -l app.kubernetes.io/name=konvu-controller -f

# Stream broker logs
kubectl logs -n konvu-broker -l app.kubernetes.io/name=konvu-broker -f

# Check resource usage
kubectl top pods -n konvu-controller
kubectl top pods -n konvu-broker

# View recent events
kubectl get events -n konvu-controller --sort-by='.lastTimestamp'
kubectl get events -n konvu-broker --sort-by='.lastTimestamp'

# Check analysis job pods
kubectl get pods -n konvu-controller -l konvu.com/job-type

# Check health endpoints
kubectl exec -n konvu-controller deployment/konvu-controller -- curl -s http://localhost:8081/healthz
kubectl exec -n konvu-broker deployment/konvu-broker -- curl -s http://localhost:8081/healthz
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis/verification-and-next-steps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.