Kvendra Platform

Kvendra Platform: publication card

What it is and what problem it solves

What it is: the knowledge behind kvendra-platform (https://github.com/KvendraAI/kvendra-platform): the decisions that shaped it, its architecture and its manual, as the author recorded them while building it. The code lives in GitHub; the knowledge lives here.

This publication is a snapshot of the author's own project KB, so some entities are in Spanish. Your own KB is written in whichever language you work in.

PLATFORM — kvendra-platform (TypeScript). It is the KB engine that anyone can run on their own machine with docker-compose up: PostgreSQL with pgvector, an MCP server, and the model of entities, transactions and change history that the Kvendra skills use. One deployment holds one team's data. It solves the problem of owning a self-hosted KB that works with the same skills, without depending on a managed service. Use your own embedding model, for example a local one with Ollama; a mock provider is included for tests. It is for developers and teams who want their agents' project memory on infrastructure they control.
Sister project — kvendra-cli (Rust; not included in this publication). It is the MCP capability broker with a local credential vault: agents run git, GitHub, package and cloud operations through it, and the broker uses your tokens on the agent's behalf instead of handing them over. It has its own publication in the catalog.
Sister project — kvendra-skills (not included in this publication). The skills are a Claude Code plugin; they read and write the KB through the platform's MCP tools. It has its own publication in the catalog.

How to use it and fork it

Read it. Anyone can read this publication in the browser.

Fork it, to work on the code with the author's knowledge. You need a Kvendra account on Pro or higher.

Clone the repository: git clone https://github.com/KvendraAI/kvendra-platform.git.
Fork this publication into your Kvendra project with the publication_fork tool in Claude Code. It becomes a new project, or is added to one you already have.
Review and activate. Forked entities wait in quarantine, and your AI does not use them until you review and activate them in the dashboard. Standards and patterns are activated one by one.

What your AI gains. Once you activate them, it works on the code with the author's decisions, architecture and manual in your project's knowledge base, instead of reading the code cold.

Good to know. A fork is a snapshot of one version; a new version is a new fork, and nothing is merged automatically. Private values, files and history are not copied. Self-hosted engines cannot fork.

Navigating the publication. The publication has three parts, and each one is reachable from the top navigation:

The cover page — this card. Read it first: it tells you what is in the snapshot and how it is licensed.
Manuals — the English book of the platform, organised in chapters: overview, architecture, installation with Docker Compose, connecting clients, the entity model, transactions, relations, change history, embeddings providers, semantic search, the MCP tool reference, configuration and operations, troubleshooting, and releases and licensing. It is the guided path through the design, the installation and the day-to-day use.
The entity index — every published KB entity, grouped by type. Each entity page shows its content, its tags and its relations. Start with the component entity CMP-KVD-PLATFORM, which describes the scope, stack and status of the component, and follow the relations from there.

Relations to entities that are not part of this publication are shown as "[private entity]", without an id or a title. This is intentional.

Using the code. The repository is public on GitHub:

KvendraAI/kvendra-platform (https://github.com/KvendraAI/kvendra-platform) — run it locally with docker-compose up from a clone of the repository, or use the signed container image docker.io/kvendra/kvendra-platform (cosign keyless signature and an SPDX SBOM).

The sister projects are public too: KvendraAI/kvendra-cli (https://github.com/KvendraAI/kvendra-cli) and KvendraAI/kvendra-skills (https://github.com/KvendraAI/kvendra-skills).

KB structure

The KB is made of typed entities. Each entity has a stable identifier of the form TYPE-PROJECT-COMPONENT-SUFFIX, Markdown content, tags, and typed relations to other entities. The types in this publication are:

| Type | What it is |
|------|------------|
| CMP | component sheet: scope, stack, status and repository of the component |
| REQ | requirements: what was asked for, why, and the acceptance criteria |
| DOC | documentation entities attached to the component |

The manual is not an entity: the platform book is published as its own section, chapter by chapter.

The most common relations are part_of (an entity belongs to the project), affects (an entity concerns a component), fulfills (a component fulfils a requirement), depends_on and derives_from. A good reading order is: platform book → CMP → REQ → DOC.

Licenses

PLATFORM code (kvendra-platform): AGPL-3.0-only.
Content of this publication (the text of the KB entities, the manual and this card): AGPL-3.0-only, the same license as the code.

The sister projects are not part of this publication: kvendra-cli is licensed under Apache-2.0 and kvendra-skills under MIT, as stated in their repositories.

Maintainer

Kvendra team — hello@kvendra.ai

Version

Content as of 2026-10-17. Component version at that date:

PLATFORM: kvendra-platform 0.1.0-alpha.1, an alpha published as a signed container image. Status: alpha; one deployment holds one team's data.

The publication version number is assigned by the server when the snapshot is published.

What is included and what is not

Included component:

PLATFORM (CMP-KVD-PLATFORM) — kvendra-platform, the self-hosted KB engine, together with its English book in Manuals.

For this component the publication includes its component sheet and its active entities of type CMP, REQ and DOC.

Sister projects. kvendra-cli and kvendra-skills are mentioned on this card as context. Their component sheets, entities and books are not part of this publication.

Language of the entities. The card and the manual are in English. The entities are published in their original language, and part of this KB is written in Spanish.

Not included:

Issues, tests, releases, roadmap items and architecture decision records (ISSUE, TEST, REL, ROAD and ADR) are left out by default.
The sister projects kvendra-cli and kvendra-skills, the other components of the project, and its cross-cutting context.
Drafts, proposals and archived entities.
Restricted types (COST, CFG, ENV, RUN) and security or incident issues.
Internal metadata, change history and authorship of the entities.