Public Roadmap

You need to know what is shipping next before you standardize on an analytics stack. This page tracks public HitKeep roadmap items in one place.

Roadmap Notes

• Release numbers are target buckets, not a delivery contract.
• Scope can move if implementation details change or a feature adds too much operator complexity.
• The constraint does not change: HitKeep stays focused on a single-binary, privacy-first, auditable product without turning into a sprawling analytics platform.

2.2.0

HitKeep 2.2.0 is the current closeout release. It focuses on two things: better visibility into AI-driven traffic, and cleaner data by default.

AI Visibility

• Built-in AI visibility analytics for tracking AI crawler fetches and correlating them with later AI-referred visits
• Reporting dimensions around assistant family, operator family, and resource type
• A clearer way to answer which AI systems are discovering your content versus sending real follow-up traffic

AI Chatbots

• Built-in AI chatbot analytics for on-site assistants, support bots, shopping helpers, and docs bots
• Structured reporting for prompts, responses, citations, handoffs, and assisted conversions
• Native dashboard support instead of forcing teams to stitch this together from generic custom-event charts alone

Spam Filtering Pipeline

• A more sophisticated spam filtering pipeline with automated, sensitive defaults
• Spamhaus integration for blocking known bad networks before they pollute reports
• Referrer filtering to suppress classic analytics spam patterns
• Host name filtering to cut out junk host values and noisy traffic sources
• Cleaner reports without turning spam mitigation into a manual maintenance project

2.3.0

The 2.3.0 release is aimed at common tracking tasks teams should not have to instrument by hand.

Automatic Interaction Tracking

• Automatic outbound link tracking
• Automatic download tracking
• Built-in dashboards for outbound link and download activity
• Better reporting on what content actually drives exits, downloads, and deeper engagement

First-Party SDKs And Integrations

• First-party SDKs and integrations, starting with WordPress and similar platforms
• A smoother path for teams that want native integrations instead of wiring everything through the raw snippet or ingest API
• Continued focus on keeping those integrations simple and aligned with the core HitKeep data model

Further Horizon

These are active product directions, but they sit beyond the current release buckets above.

Enterprise Identity

• SSO for organizations that need centralized identity and user lifecycle management
• Likely focus areas: SAML and OIDC-based sign-in for procurement-heavy and enterprise environments

Custom Branding

• Custom branding for teams, agencies, and customer-facing dashboards
• Better fit for client portals, shared dashboards, and branded cloud workspaces

MCP Support

• MCP support so AI tools and internal assistants can query HitKeep in a structured, governed way
• Useful for internal analytics copilots, reporting automation, and support workflows that need direct access to analytics context

More First-Party Integrations

• Broader first-party platform support after the initial CMS and SDK wave
• Focus on integrations that remove repetitive setup work without bloating the core product

What Will Not Change

Even as the feature set grows, the product direction stays the same:

• single binary
• zero external database dependency
• privacy-first defaults
• open export formats
• self-hosted and managed cloud from the same product foundation

If you need something specific for a deployment, procurement review, or migration, open an issue on GitHub or see HitKeep Cloud if you want the same product without the operational overhead.