kagent Website & Docs
The official website and documentation source for kagent and kMCP, covering the Kubernetes-native agent framework and its adopters.
- Source repo
- kagent-dev/website
- Stars
- ★ 21
- Last updated
- 2d ago
- License
- Apache-2.0
- Primary language
- TypeScript
- FA score
- 30/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free, no paid service needed
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A developer who wants to understand what kagent is and how to build AI agents on Kubernetes reads the site and docs hosted here.
- Not a fit if
- Readers who want to deploy the kagent framework itself — this repo is only the site and docs
- Teams with no kagent or kmcp usage who just want a demo
- Source review
- 30/100 · Major gaps 3 safety controls not found
What does this agent do, and when should you use it?
This repository is the website project under the kagent-dev organization, positioned as the official site and documentation home for kagent and kMCP rather than the framework code itself. The README shows site-oriented assets, pulling logo images (icon-dark.svg and icon-light.svg) from the kagent main repository and embedding a Discord invite badge. Three collaboration paths are documented: local development lives in DEVELOPMENT.md, contribution instructions in CONTRIBUTION.md, and adopters join the public list by opening a PR against src/data/adopters.yaml. Because the README invites companies using kagent or kmcp in dev/test or production to add their name and logo, this repo also serves as the public record of ecosystem adoption. Content-wise it is a site and docs repository: pages plus data files, with documentation maintained here.
The repository hosts the kagent and kMCP website and documentation. It renders site content, maintains the adopter roster in src/data/adopters.yaml, and accepts community PRs that append a company name and logo to that file. The README pulls the kagent logo from the main repository (icon-dark.svg and icon-light.svg) for the site header and embeds a Discord invite badge pointing at bit.ly/kagentdiscord. Guidance is split across two files: DEVELOPMENT.md describes how to run everything locally, and CONTRIBUTION.md describes how to contribute; the README only links to them and contains no commands. The output is a browsable official site with documentation pages and a public list of kagent and kmcp adopters.
- A developer who wants to understand what kagent is and how to build AI agents on Kubernetes reads the site and docs hosted here.
- A company already running kagent or kmcp in dev/test or production wants to be listed publicly and opens a PR editing src/data/adopters.yaml.
- A community member who wants to fix or extend the kagent site and docs follows the workflow in CONTRIBUTION.md.
- A contributor who wants a local preview while editing follows the local development instructions in DEVELOPMENT.md.
- Someone looking for the community channel joins the Discord server through the badge linked in the README.
- Maintainers who need kmcp described alongside kagent keep both sets of docs in one site.
How do you install or deploy this agent?
The README does not provide copyable installation or build commands. It states only that instructions for running everything locally are in DEVELOPMENT.md and that contribution instructions are in CONTRIBUTION.md; neither file's contents are included in the source shown here. Concretely missing: the package manager, dependency install command, required runtime and version (for example Node.js), and the build or preview commands. The repository is published under Apache-2.0. For the actual setup steps, DEVELOPMENT.md is the required next reference, and CONTRIBUTION.md covers the contribution path.
How do you use this agent?
The adoption flow is the one fully documented procedure in the README: open a PR against the adopters data file with your company name and logo.
File: src/data/adopters.yaml
Action: submit a PR adding your company name and logoBeyond that, the README gives no commands for running, previewing or deploying the site — those steps live in DEVELOPMENT.md and CONTRIBUTION.md, whose contents are not included here. The README also exposes a community entry point: the Discord invite badge at https://bit.ly/kagentdiscord.
What are this agent's strengths and limitations?
- Clearly scoped: the repository is dedicated to the kagent and kMCP website and docs, keeping it separate from framework code.
- The adopter path is open and cheap to join — a PR adding a company name and logo to src/data/adopters.yaml.
- The community entry point is built in: a Discord invite badge linking to bit.ly/kagentdiscord.
- Apache-2.0 licensed, so site content and docs can be used and redistributed.
- It is not the kagent framework; there are no install or run commands for the agent framework here, so deployment questions must go elsewhere.
- The README delegates local setup and contribution entirely to DEVELOPMENT.md and CONTRIBUTION.md and states no stack, runtime version, or build command.
- Environment requirements are undocumented in the README — no Node.js or package manager version — so local startup success cannot be judged from it.
- The adopter list depends on manual PRs, and review criteria plus logo format or size requirements are not stated.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| kagent Website & Docs This agent | 30 · Major gaps | Web appFree | ★ 21 | 2d ago | TypeScript | — |
| Cordum Agent Control Plane | 64 · Some gaps | Self-hosted serviceFree | ★ 511 | 1d ago | Go | Claude Code |
| HolmesGPT SRE Agent | 57 · Major gaps | CLIFree + model costs | ★ 3.6k | 1d ago | Python | OpenAI API |
| SandBase Harness | 52 · Major gaps | CLIFree + model costs | ★ 639 | 7d ago | TypeScript | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence is limited to README, LICENSE, package.json, two CI workflows, and two Playwright specs. This is the kagent website/docs repository, not an installable Agent product, so runtime trust properties are largely unobservable in source: least_privilege scores 1 only because CI declares explicit permissions (contents: read, issues: write), with no Agent-side permission model shown; user_confirmation has no confirmation/approval mechanism, 0; data_flow_transparency is a single positioning sentence with no data-flow description, 1; sensitive_data_handling has no secrets/PII/redaction guidance, 0; external_effects scores 1 because CI creates issues, posts to Slack, and deploys a Cloudflare worker, but no impact scope or recovery is described; rollback has no rollback/recovery procedure, 0; dependency_security scores 1 for pinned postcss/sharp overrides and SHA-pinned actions, which is thin; source_attribution scores 1 for Apache-2.0 and upstream icon references but no NOTICE or provenance inventory.
self_consistency: README, package.json scripts, and CI comments broadly agree, but README never mentions the docs-site/ Hugo subsite or the dual Next.js/Hugo structure, so documentation and actual repository layout diverge — 1. dependency_availability: dependencies are public npm packages with pinned CI versions, but no lockfile evidence or offline/mirror guidance — 1. failure_messages: CI comments thoroughly document failure modes (job timeout, apt mirror stalls, pipefail masking test failures) and mitigations, which is good evidence, but only at the CI layer; no product-side error design — 1.
audience_and_scenarios: README addresses contributors and adopters only, with no distinction between Agent users, operators, and developers — 1. capability_boundaries: no statement of what the Agent can or cannot do beyond a one-line framework positioning — 1. trigger_precision: no trigger conditions, invocation contract, or input/output definition — 1. environment_fit: local dev, Cloudflare worker, and Hugo docs-site hints exist, but no environment requirements matrix — 1.
information_architecture: basic structure (README/LICENSE/package.json/CI/tests) exists but no directory guide or navigation — 1. install_notes: only pointers to DEVELOPMENT.md and CONTRIBUTION.md, which are not in evidence and cannot be verified — 1. naming_stability: package name kagent-website and script names are consistent, but no versioned naming policy — 1. examples_and_faq: no examples or FAQ; Playwright specs are the only test-like examples — 1. known_limitations: no known-limitations section; CI comments about temporary preview overlays and continue-on-error are internal notes, not user-facing limitations — 1. license: full Apache-2.0 text present — 2. versioning_changelog: no CHANGELOG or release notes — 0. maintenance_responsibility: Discord, contribution guide, and adopters process exist, but publisher identity is unverified and there is no maintainer or security contact — 1.
output_usability: the repository produces a website and docs, with no directly runnable artifact for Agent users — 1. marginal_value: as kagent's documentation site it has informational value, but it is ancillary to the main kagent repository, so marginal value is limited — 1. cost_benefit: maintaining a dual stack (Next.js + Hugo) and multiple CI pipelines is non-trivial cost for a documentation-presentation benefit — 1.
claim_traceability: README's framework positioning cannot be traced or verified within this repository's source — 1. cross_source_corroboration: README, package.json, and CI disagree about repository structure (README omits docs-site), so cross-source corroboration is weak — 1. fact_inference_separation: CI comments do distinguish observed symptoms from inferred causes (e.g., the apt mirror issue), which is a plus, but the overall material remains narrative — 1.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- This repository is kagent's website/docs site, not an installable Agent product; do not treat its documentation as evidence of Agent runtime safety or reliability.
- Publisher identity is unverified; the Discord link and adopters process in README do not establish maintenance responsibility or a security response channel.
- CI workflows create issues, post results to a Slack channel, and deploy a Cloudflare worker, producing external side effects with no stated impact scope or rollback path.
- The framework-tests workflow is marked continue-on-error, so test failures do not block merges; a green run should not be read as a quality guarantee.
- README never mentions the docs-site/ Hugo subsite, so documentation and actual repository structure diverge and following README alone may miss content.
- No CHANGELOG, no release notes, and no known-limitations section; version and compatibility information is absent.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
What's Changed * Update kagent 1.x reference docs at v1.0.0-alpha13 (version conrefs changed) by @github-actions[bot] in https://github.com/kagent-dev/website/pull/603 * Derive runtime metrics from invocation spans by @Rachael-Graham in https://github.com/kagent-dev/website/pull/602 * Clarify ModelConfig rejection behavior by @Rachael-Graham in https://github.com/kagent-dev/website/pull/604 * Revert npm-minor-patch group bump (#599) to restore kagent.dev by @Rachael-Graham in https://github.com/kagent-dev/website/pull/605 …View on GitHub ↗ -
v0.10.3 Docs for v0.10.3
Release notes excerpt
Point-in-time snapshot of the kagent documentation at the kagent v0.10.3 release. Publishing this release runs Update Reference Documentation against the kagent v0.10.3 tag and opens a pull request regenerating the 0.x API, Helm, and CLI references along with the 0.x version conrefs. See https://github.com/kagent-dev/website/pull/525 for the trigger. First docs release cut from this repository, so there is no earlier tag to generate a changelog from. Later releases carry the usual What's Changed list. Full Changelog: https://github.com/kagent-dev/website/compare/v0.10.2...v0.10.3View on GitHub ↗ -
v0.10.2 Docs for v0.10.2