HitKeep Roadmap
HitKeep is built in the open, and most of what ships starts as a request from someone running it. This page shows where the product is heading. If something you need is missing, tell us: that is how it gets on the list.
Ask for a feature
Section titled “Ask for a feature”- Open a feature request on GitHub. Describe the problem you want solved, not only the solution you have in mind.
- Start a discussion if the idea is still rough or you want to compare notes with other users.
- Email hello@hitkeep.com if you prefer not to post publicly, for example for a procurement question or a deployment you cannot describe in an issue.
Upvote existing requests with a 👍. It is the clearest signal for what to build next. For help with an existing setup, email support@hitkeep.com.
Work in progress after 2.14.0:
- Ask AI and MCP quality. Better answers to “why did this change?” questions, tested against a fixed set of questions on several models before each release.
- Faster reports on large sites. Continued query work like the 2.14.0 overview speed-up, so dashboards stay quick as traffic grows.
- Smoother upgrades and releases. Fewer surprises for self-hosted operators across migrations, backups, and restarts.
Planned, roughly in this order. Follow the linked issues for details or to add your use case.
- Self-service account deletion (#316)
- A Search Console workspace with query, page, and trend views in one place (#261)
- Typed webhook payloads for every event (#260)
- OAuth 2.1 for the API and MCP, so assistants and integrations connect without long-lived tokens (#245)
- Team SSO enforcement for teams that want single sign-on to be the only way in (#226)
Directions we want to take, without dates yet:
- Automatic insights: spike and drop alerts, and period summaries that point at the biggest movers.
- Conversion attribution: which sources, campaigns, and pages lead to goals and revenue, without cookies or user-level tracking.
- Page reports: one view per page with traffic, sources, events, and conversions.
- Custom branding for agencies and client-facing dashboards.
- More SDKs and integrations beyond the npm tracker and WordPress plugin.
Recently shipped
Section titled “Recently shipped”- 2.14.0: chart annotations, a conversational Ask AI that explains what drove a change, exact report email previews, dashboard themes (contributed by @gnacho), shared table controls, bundled DuckDB extensions for offline startup, and explicit config files. Release post
- 2.13.0: scheduled reports with external recipients, Google, GitHub, and Microsoft sign-in, the typed
@hitkeep/trackerSDK, layered traffic exclusions, and isolated tenant storage. Release post - 2.12.0: team OIDC single sign-on and routed settings. Release post
- 2.11.0: signed outbound webhooks. Release post
The changelog has every release, and GitHub Releases is the source of truth for what shipped.
What will not change
Section titled “What will not change”- One binary, with no external database, cache, or queue to run.
- Privacy-first defaults: cookieless tracking that collects only what analytics needs.
- Open export formats, so your data is never locked in.
- Self-hosted and HitKeep Cloud run the same product.
Plans can shift when something turns out to add more complexity than it is worth. If an item matters to you, say so on its issue or at hello@hitkeep.com.