Community

Kvendra's open-core pieces are developed in the open on GitHub. That is where you ask questions, report bugs and propose changes — each repository has its own Discussions and issue tracker.

Ask a question or report a bug

Questions, ideas and "how do I…?" go to Discussions. Bugs — something that is broken and reproducible — go to Issues. Use the repository closest to your problem. Not sure which one? If it happened while following the Quickstart, start with kvendra-reference-stack.

A good report says what you ran, what you expected and what happened:

• the exact command or prompt, and the full error text;
• versions — docker compose version, the plugin version from /kvendra-skills:version, and kvendra --version if you use the CLI;
• the output of curl http://localhost:7777/healthz for engine problems.

Never paste tokens, keys or the contents of your .env into an issue. Issues are public.

Contribute

Fixes and improvements are welcome. For anything bigger than a typo, open an issue first so the approach can be agreed before you write the code.

• Skills have a contribution guide covering conventions and templates: CONTRIBUTING.md.
• Platform, reference stack and CLI: open an issue describing the change, then a pull request against main.
• These docs: open an issue or a pull request on kvendra-dev.

Report a security issue

Do not open a public issue for a vulnerability. Follow the private reporting instructions in the repository's security policy: Platform, CLI, Skills.

Support

Help here comes from the maintainers and other users, on GitHub, as time allows. Most setup questions are already answered in the Quickstart and Advanced install.

Community support is free and best-effort. Email support comes with paid Kvendra Cloud plans — kvendra.com/support →