Issue tracker and support for KeyKosh (K2) — the self-hosted, permanently-licensed configuration and secrets platform.
0
stars
0
commits
Jul 29, 2026
updated
README
KeyKosh Support
This is the public issue tracker for KeyKosh (K2) — a self-hosted, permanently-licensed configuration and secrets platform that runs entirely inside your own infrastructure.
There is no source code here. KeyKosh's server is a commercial product; this repository exists so customers and evaluators have one public place to report bugs, request features, and ask questions.
- Product & pricing: https://keykosh.com
- Documentation: https://keykosh.com/docs/
- Client SDKs (MIT, open source): Java · Node · Python
Where to file what
| What | Where |
|---|---|
| Bug in the platform, admin UI, CLI, installer, or an SDK | Open an issue |
| Feature request or roadmap input | Open an issue |
| Documentation error or gap | Open an issue |
| Question / "how do I…" | Discussions |
| Security vulnerability | Never a public issue — see SECURITY.md |
| License keys, activation, billing, renewals | support@keykosh.com |
| Anything containing your hostnames, credentials, or config | support@keykosh.com |
Before you open an issue
This tracker is public. Do not paste license keys, SDK tokens, passwords, database endpoints, internal hostnames, or real configuration values. Redact them, or email support@keykosh.com instead — a private channel exists precisely so you don't have to sanitise anything.
The details worth including up front (the issue forms will prompt you for them):
- The
k2-appimage tag you're running — visible in yourdocker-compose.yml, or viadocker inspecton the running container. - How you installed — Docker Compose, AWS/Terraform, CLI, or the desktop installer.
- Your tier — Free, Pro, Pro+, or trial.
- For licensing or entitlement problems, the output of
GET /api/licensewith thekeyfield removed — thetier,bindingStatus,degraded, andusagefields are what diagnose almost every activation issue.
Support scope
Bug reports, feature requests, and questions are welcome from everyone, including people evaluating KeyKosh on the Free tier or a trial key.
A paid maintenance plan adds a response-time commitment and covers version upgrades and security patches. See https://keykosh.com/pricing for what's included. Issues here are triaged on a best-effort basis regardless of tier — a maintenance plan changes how fast you get a response, not whether your report is read.
Your data stays yours
KeyKosh makes no outbound calls to vendor infrastructure. License validation is offline,
and images are pulled directly from ghcr.io. Nothing about your install reaches us
unless you put it in an issue or an email — which is why the guidance above is to send
sensitive details privately, or not at all.
See what people are saying
Similar repos
Issue tracker and support for KeyKosh (K2) — the self-hosted, permanently-licensed configuration and secrets platform.
0
stars
0
commits
Jul 29, 2026
updated
README
KeyKosh Support
This is the public issue tracker for KeyKosh (K2) — a self-hosted, permanently-licensed configuration and secrets platform that runs entirely inside your own infrastructure.
There is no source code here. KeyKosh's server is a commercial product; this repository exists so customers and evaluators have one public place to report bugs, request features, and ask questions.
- Product & pricing: https://keykosh.com
- Documentation: https://keykosh.com/docs/
- Client SDKs (MIT, open source): Java · Node · Python
Where to file what
| What | Where |
|---|---|
| Bug in the platform, admin UI, CLI, installer, or an SDK | Open an issue |
| Feature request or roadmap input | Open an issue |
| Documentation error or gap | Open an issue |
| Question / "how do I…" | Discussions |
| Security vulnerability | Never a public issue — see SECURITY.md |
| License keys, activation, billing, renewals | support@keykosh.com |
| Anything containing your hostnames, credentials, or config | support@keykosh.com |
Before you open an issue
This tracker is public. Do not paste license keys, SDK tokens, passwords, database endpoints, internal hostnames, or real configuration values. Redact them, or email support@keykosh.com instead — a private channel exists precisely so you don't have to sanitise anything.
The details worth including up front (the issue forms will prompt you for them):
- The
k2-appimage tag you're running — visible in yourdocker-compose.yml, or viadocker inspecton the running container. - How you installed — Docker Compose, AWS/Terraform, CLI, or the desktop installer.
- Your tier — Free, Pro, Pro+, or trial.
- For licensing or entitlement problems, the output of
GET /api/licensewith thekeyfield removed — thetier,bindingStatus,degraded, andusagefields are what diagnose almost every activation issue.
Support scope
Bug reports, feature requests, and questions are welcome from everyone, including people evaluating KeyKosh on the Free tier or a trial key.
A paid maintenance plan adds a response-time commitment and covers version upgrades and security patches. See https://keykosh.com/pricing for what's included. Issues here are triaged on a best-effort basis regardless of tier — a maintenance plan changes how fast you get a response, not whether your report is read.
Your data stays yours
KeyKosh makes no outbound calls to vendor infrastructure. License validation is offline,
and images are pulled directly from ghcr.io. Nothing about your install reaches us
unless you put it in an issue or an email — which is why the guidance above is to send
sensitive details privately, or not at all.