·SECTION 08 — SUPPORT

Support.

Two tiers. Community (free) for self-hosters who run on GitHub Issues, and Business (bespoke, negotiated case by case) for teams that need a private channel, an SLA, and a real human on the other end.

§ 01 — PLANS ·COMMUNITY · BUSINESS

·COMMUNITY
·FREE · LIVE

GitHub Issues · Docs

The default. Public bug reports, RFC discussions, community-driven answers from maintainers and other users. Best-effort, no SLA — but it's where most questions get solved fastest because everyone benefits from the answer.

github.com/KvendraAI → · x.com/kvendraai →

·BUSINESS
·CONTACT US

Bespoke support, negotiated case by case

For teams shipping serious workloads on Kvendra. Every Business plan is shaped to your stack, your SLA, your compliance profile. Includes a private Slack channel, scheduled video calls, and engineering on call for the issues that matter to you.

Typical scope: custom SLA (4 hr P1 down to 24/7 on-call), architecture reviews, migration planning, on-prem deployment support, custom skill development guidance.

or email sales@kvendra.ai

§ 02 — WHAT'S COVERED ·BUSINESS PLAN

Every Business plan covers the basics, plus whatever else you negotiate. The defaults below are the floor — most engagements add to them.

Install, configure, run. Docker, compose, Kubernetes, on-prem networking, embedding providers, vault initialisation, MCP wiring to your IDE of choice.
Integrations. Hooking Kvendra into your existing CI/CD, observability, secrets management, and IAM. Glue code reviews included.
Custom skills. Scoping, authoring, and reviewing private skill packs for your team's pipelines.
Architecture reviews. Quarterly sessions covering KB modelling, contract design, and how to surface domain entities in a way Claude can reason about.
Migration & rollout. Planning a phased move from harness-only / chat-only setups to the typed KB. Coexistence patterns while teams ramp up.
Incident response. P1 paths into engineering, postmortem support, and follow-up reviews of the typed audit log.

·NOT IN SCOPE

We don't write your code. Support is about getting Kvendra out of the way so your team ships — not replacing the team. If you need a build partner, ask and we'll route you to a vetted services partner.

§ 03 — CHANNELS & SLA ·HOW WE ANSWER

·CHANNEL
·COMMUNITY

Public · async · community-driven

GitHub Issues + Docs. No SLA. Maintainers triage and pick up what's prioritisable; community often answers faster than we do.

·CHANNEL
·BUSINESS

Private Slack · video calls · email backup

A dedicated Slack channel with a named contact on our side. Weekly or biweekly video sync for active engagements. Email fallback for anything that needs to live outside Slack history.

·SLA
·BUSINESS

Custom — typically 4 hr P1 / 1 business day P2

Every engagement defines its own severity matrix. Floor is 4 hr response on P1 critical and 1 business day on P2. Optional 24/7 on-call rotation as an add-on.

§ 04 — GET IN TOUCH ·START A CONVERSATION

Business support is negotiated case by case — a 30-min intro call is the fastest way to scope a plan. We'll ask about your stack, your team size, the workloads you want Kvendra to carry, and any compliance constraints. Drop us a message below and we'll send a calendar link within one business day.

or email sales@kvendra.ai

·NOTE

Support is independent from Cloud hosting — you can run self-hosted with a Business support plan, or use Cloud Pro with only Community support. Two separate axes, mix to taste.