HitKeep Support Channels and Issue Reporting

There are two ways to get help: email for anything private, and GitHub for everything that can be public.

Email support

Email support@hitkeep.com for help with HitKeep Cloud or a self-hosted instance, especially when the question involves your account, billing, or details you cannot share in public. Include your HitKeep version, how you deploy it, and for HitKeep Cloud the region you signed up in (EU or US).

Do not send passwords, API tokens, or other secrets. Support never needs them.

For partnerships, enterprise procurement, privacy requests, and anything else, email hello@hitkeep.com.

GitHub

GitHub Issues is the place for bugs, feature requests, and self-hosted setup questions. Answers there help the next person with the same problem. Do not include secrets, private analytics, or customer data in an issue.

Reporting bugs

Search existing issues. Someone may have already reported it.
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

Feature requests

Check the roadmap first to see what is already planned, then open a feature request. Describe the problem you want solved; a specific use case helps most, especially for enterprise or compliance requirements.

Setup questions

If the installation guides do not cover your scenario, open an issue describing your environment, or start a discussion if you are not sure it is a bug.

Open GitHub Issues →

Product updates

HitKeep is maintained by Pascale Beier. Follow HitKeep for release news:

Cloud and enterprise

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

Start with HitKeep Cloud →