Ir al contenido
Empezar gratis en Cloud

HitKeep Support Channels and Issue Reporting

Esta página aún no está disponible en tu idioma.

Choose the channel that fits the question. Live chat is available for private sales and support conversations; GitHub remains the public support channel for the open-source product.

Use Chat with us on this site, or Support in the HitKeep Cloud dashboard, to start a conversation with the HitKeep maintainer. The chat shows whether a person is currently available, without promising fixed hours or a response-time SLA.

  • Docs visitors start anonymously and can provide contact details after sending a message.
  • Signed-in HitKeep Cloud users are securely identified so support can distinguish the account and selected Cloud region. Analytics data, site or team identifiers, API tokens, and dashboard contents are never added to the chat automatically.
  • If nobody is available, provide your email address so the conversation can continue by email.
  • File uploads and AI support agents are disabled.

Chat is self-hosted by HitKeep at support.hitkeep.eu. It is not contacted and does not set its functional chat cookies until you explicitly open chat. See the Privacy Policy for the data and residency details.

If chat cannot load, you can stay on this page and use the contact details below.

GitHub Issues is the primary place for public bugs, feature requests, and self-hosted setup help. Do not include secrets, private analytics, or customer data in an issue.

  1. Search existing issues — someone may have already reported it.
  2. Open a new issue and include:
    • HitKeep version (from the startup log line)
    • Deployment method (binary, Docker Compose, Kubernetes)
    • Your configuration (flags or compose.yml, with secrets redacted)
    • Relevant log output and steps to reproduce

Before opening a request, check the Public Roadmap and the linked GitHub release buckets to see what is already planned.

  1. Check whether the feature is already tracked in open issues.
  2. Open an issue with a clear description of the problem you are trying to solve.
  3. The more specific the use case, the better — especially for enterprise or compliance requirements.

If the Installation Guides don’t cover your scenario, open an issue describing your environment. Answers become part of the public knowledge base.

Open GitHub Issues →

For private inquiries, partnerships, enterprise procurement discussions, privacy requests, or a chat fallback:

Official HitKeep profiles for public product updates:

For managed hosting, enterprise deployments, or direct support, see HitKeep Cloud. The pricing page compares plans; you choose EU or US hosting on the signup form.

Start with HitKeep Cloud →