GITNUXSOFTWARE ADVICE
Cybersecurity Information SecurityTop 10 Best Keystroke Logger Software of 2026
Top 10 Keystroke Logger Software ranking with technical criteria for IT admins and security teams, including Teramind, Veriato, and ActivTrak.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Teramind
Keystroke capture mapped into a session and application activity model for forensic pivots.
Built for fits when mid-size enterprises need keystroke-grade monitoring with RBAC, audit logs, and automation hooks..
Veriato
Editor pickAudit-log and RBAC governance that tracks who configured monitoring and what changed.
Built for fits when regulated teams need keystroke capture with RBAC governance and auditable configuration..
ActivTrak
Editor pickPolicy-driven keystroke capture tied to session and application metadata in the event schema
Built for fits when security and operations teams need governed interaction telemetry with automation and reporting control..
Related reading
Comparison Table
This comparison table maps keystroke logger software across integration depth, data model, and extensibility. It also evaluates automation and the available API surface, plus admin and governance controls such as RBAC, provisioning, and audit log coverage. The goal is to surface practical tradeoffs around configuration, schema design, and how each tool moves high-volume telemetry into governed workflows.
Teramind
enterprise monitoringProvides user and endpoint behavior monitoring that includes keystroke logging for insider-risk and compliance use cases.
Keystroke capture mapped into a session and application activity model for forensic pivots.
Teramind captures keystrokes at the workstation level and correlates them with activity context such as windows, apps, and user identity for forensic review. The data model is built around event and session records so investigations can pivot from what a user typed to where it happened. Admin controls include RBAC to separate oversight duties and audit logs that record administrative and configuration changes.
A concrete tradeoff is that keystroke capture can increase event throughput and storage demands, especially in high-concurrency environments. In practice, Teramind fits teams that need consistent capture rules across departments and require automation hooks for ticketing, SIEM ingestion, or policy workflows.
- +Keystroke events are correlated with app and session context for faster investigations
- +RBAC separates monitor, admin, and investigator permissions with auditable configuration changes
- +API and automation surface supports data export and integration into existing workflows
- +Configurable capture rules support targeted monitoring instead of blanket logging
- –High monitoring volume can raise storage and ingest load during peak usage
- –Keystroke retention and scope tuning require careful configuration to avoid data overshare
Best for: Fits when mid-size enterprises need keystroke-grade monitoring with RBAC, audit logs, and automation hooks.
Veriato
workforce monitoringDelivers employee monitoring with keystroke logging and application activity capture for compliance and security investigations.
Audit-log and RBAC governance that tracks who configured monitoring and what changed.
Veriato is a keystroke logger intended for controlled rollouts where administrators need repeatable configuration and predictable data schema. The collection side supports user and endpoint attribution so logs can be correlated with identity and workstation context. The admin side emphasizes governance with RBAC-style access control and an audit log to track configuration and operational changes.
Automation and API surface are the main decision factor for teams that need to wire monitoring into existing workflows. Veriato fits environments where compliance teams require exportable evidence, consistent schemas, and traceable changes across groups. A tradeoff is operational overhead, since governance controls and data handling rules require careful planning before broad endpoint rollout.
- +Governance-focused data model that ties keystrokes to identity and endpoint context
- +Audit log supports traceability for configuration and monitoring operations
- +RBAC-style admin permissions limit access to captured activity
- +Extensibility through automation and API-driven integration patterns
- –Provisioning and configuration complexity slows initial deployment
- –High control granularity increases the need for change management discipline
Best for: Fits when regulated teams need keystroke capture with RBAC governance and auditable configuration.
ActivTrak
workplace analyticsTracks endpoint and application activity and can capture keystroke-level data for security and productivity governance workflows.
Policy-driven keystroke capture tied to session and application metadata in the event schema
ActivTrak’s differentiation comes from combining interaction events with a documented data model that connects keystrokes to session, user identity, and application metadata. Configuration supports structured monitoring scopes so administrators can define what data is collected per group and environment. RBAC controls restrict who can view reports, manage configurations, and administer integrations. Audit logging supports change tracking for configuration and administrative actions.
The main tradeoff is that keystroke-grade visibility depends on explicit collection policies and accurate identity mapping. If identity sources are inconsistent, event streams can fragment by user or device, which lowers the usefulness of analytics and investigations. A practical usage situation is monitoring regulated workflows where administrators need both granular interaction evidence and application context for incident triage.
- +Keystroke events tied to user, device, and application session context
- +RBAC gates configuration, reporting, and integration management
- +Audit log records admin changes across monitoring and governance controls
- +Integration and schema mapping support consistent downstream analytics
- –Keystroke fidelity depends on correctly configured collection policies
- –Identity mapping issues can split event streams across users or devices
Best for: Fits when security and operations teams need governed interaction telemetry with automation and reporting control.
GoGuardian
education monitoringMonitors managed student devices and can support keystroke-level visibility to mitigate risk in education environments.
Class- and user-scoped monitoring policies enforced across managed Chromebooks.
GoGuardian applies browser and Chromebook monitoring patterns through a centrally managed deployment for school-managed endpoints. The data model centers on device and student identity, then ties captured activity to classes, users, and applied policies.
Integration depth is driven by school domain provisioning and district administration workflows rather than direct keystroke API export. Automation and governance are expressed through policy configuration, role-based admin permissions, and audit trails for administrative actions.
- +Policy-based monitoring aligned to school identity and managed device enrollment
- +Central admin workflows for class and user grouping without custom scripting
- +Audit visibility for admin changes and monitoring configuration edits
- +High deployment throughput for district-scale endpoint fleets
- –Limited evidence of keystroke event export via third-party API
- –Extensibility depends on platform features rather than external processing hooks
- –Automation coverage focuses on policy management, not external data pipelines
- –Granular RBAC boundaries are not described as schema-level controls
Best for: Fits when districts need governed monitoring across managed student devices with policy-driven configuration.
Spyrix
monitoring suiteOffers computer monitoring with keystroke logging, application tracking, and activity reporting for parental and enterprise oversight.
Endpoint-level keystroke event capture with timestamped, user-context log records.
Spyrix captures keystroke input and organizes events by endpoint and session to support incident review. The product exposes configuration and reporting workflows that can be driven by automation, with an admin console focused on controlled deployment.
Its integration depth depends on how endpoints are provisioned and how exported logs can be routed into existing investigations workflows. The data model centers on typed keystroke events, timestamps, and user or device context for audit-style traceability.
- +Keystroke events tied to user and endpoint context
- +Central admin console for consistent endpoint configuration
- +Exportable logs support downstream investigation workflows
- +Provisioning workflow supports controlled rollout across endpoints
- –Automation surface details and API options are limited in documentation
- –Schema flexibility for custom event fields is not clearly defined
- –RBAC granularity and admin role controls are hard to validate externally
- –Throughput tuning for high-volume logging depends on deployment design
Best for: Fits when controlled endpoint keystroke capture and audit-style review must integrate with internal workflows.
Teramind by Insight
managed enterpriseDelivers managed monitoring capabilities that include keystroke-level capture through the vendor’s enterprise offering.
Audit log plus RBAC-enforced administration for monitored sessions and investigator actions.
Teramind by Insight fits organizations that need keystroke-level monitoring tied to a governance and automation workflow, not just endpoint capture. Its integration depth centers on configurable data collection, centralized case and session review, and policy-based monitoring that maps to a controllable data model.
Automation and extensibility rely on an admin surface plus API-driven administration, with audit log visibility for investigation and compliance workflows. RBAC, configuration controls, and auditability shape how monitoring throughput and retention policies can be governed across teams.
- +RBAC controls limit access to session content and investigative workflows
- +Keystroke capture links to session context for targeted review
- +API and automation surface supports provisioning and operational integration
- +Audit log coverage supports governance and evidence trails
- –High capture volume can stress storage and investigation throughput
- –Configuration complexity increases when aligning policies to roles
- –Automation depends on admin API capabilities for full workflow coverage
- –Data model tuning is required to keep analytics and exports usable
Best for: Fits when mid-size to enterprise teams need keystroke monitoring governed by RBAC, audit logs, and API automation.
iMonitor
endpoint monitoringProvides keystroke logging and activity monitoring for device oversight with audit trails for later review.
RBAC-governed capture configuration with auditable changes tied to endpoint scope
iMonitor positions itself around administrator control and device-level keystroke capture configuration rather than end-user reporting screens. The product’s value is driven by how its data model supports session context, event schemas, and retention workflows.
Integration depth depends on whether iMonitor exposes an API or scripted configuration hooks for provisioning, automation, and export. Governance centers on role-based access controls and auditable administrative actions tied to capture scope changes.
- +Configurable keystroke capture scopes per endpoint and application context
- +Event-oriented data model that separates sessions from captured keystroke streams
- +Administrative controls for managing capture behavior across managed endpoints
- +Audit-ready administrative workflows for configuration and access changes
- –Integration depth hinges on the availability of documented API endpoints
- –Automation coverage can lag if provisioning requires manual UI steps
- –Search and export throughput may be constrained by stored event volume
- –RBAC granularity may be limited if roles cannot target fine-grained permissions
Best for: Fits when admin teams need controlled capture scope plus automation and governance hooks.
Snagit
supplementary captureCaptures screen activity and can be used alongside monitoring deployments to support incident review workflows involving typed input.
Video capture with annotation for producing documented workflow evidence.
Snagit is a screen capture tool that can record on-screen activity and help produce evidence-based documentation, but it is not designed as a keystroke logging product. Its core capabilities center on capture workflows, annotation, and image or video output, which limits suitability for credential monitoring and input auditing.
Integration depth relies on common desktop capture workflows rather than a documented telemetry data model for keystroke events. Automation and API surface are therefore constrained for teams that need RBAC, audit log retention, and high-throughput event ingestion.
- +Capture images and videos with consistent annotations for recorded workflows
- +Export outputs for review and documentation workflows
- +Supports repeatable capture steps for training and process evidence
- –No documented keystroke event schema or keystroke capture mode
- –Limited admin governance features for monitoring and retention
- –No clear automation or API surface for event ingestion workflows
- –Not built for RBAC, audit log, or access-controlled telemetry
Best for: Fits when teams need visual workflow evidence, not keystroke-level monitoring or governance.
Netwrix Auditor
audit and integrationsAudits identity and access events and integrates with endpoint monitoring workflows that may include keystroke capture via connected tooling.
Role-based access to audit reports paired with event-to-entity correlation across directory, endpoints, and Microsoft 365.
Netwrix Auditor records and correlates user and system activity across Windows, Active Directory, and Microsoft 365 to produce an audit log. Its data model maps events to entities such as users, computers, domains, and objects, and then enriches those events with RBAC-scoped context.
Integration depth is driven by connector-based collection plus an API surface for automation and configuration workflows. Admin and governance controls center on role-based access to reports and audit data, retention policy configuration, and granular alerting rules.
- +Cross-system audit log correlation for AD, endpoints, and Microsoft 365 activities
- +Entity-based data model ties events to users, devices, and directory objects
- +API and automation support for provisioning workflows and configuration changes
- +RBAC controls limit who can view reports and audit data
- –Keystroke logging is not a primary audited-data focus for this product
- –Automation needs careful schema mapping to keep event correlations consistent
- –Throughput depends on connector coverage and event volume tuning
- –Admin configuration requires strong governance around roles and retention
Best for: Fits when audit governance needs API-driven configuration and cross-system audit log correlation.
ManageEngine Endpoint DLP
DLP telemetryProvides data loss prevention controls and can integrate with endpoint telemetry workflows to detect typing events that indicate exfiltration.
Endpoint DLP keystroke and content event policies with correlated enforcement and governance audit logs.
ManageEngine Endpoint DLP fits organizations that need endpoint keystroke capture rules tied to a structured DLP data model, then enforced through repeatable endpoint configuration. The solution focuses on content and event policies that depend on endpoint telemetry, including keystroke and activity correlation, rather than reporting-only logging.
Governance depends on admin roles, policy scoping, and audit trails that track changes to data handling rules. Automation and extensibility are handled through ManageEngine integrations and administrative configuration workflows, with an emphasis on consistent deployment across endpoints.
- +Policy-driven keystroke and content controls tied to DLP event correlation
- +Centralized admin roles with RBAC scoping for policy management
- +Audit log coverage for configuration changes and enforcement actions
- +ManageEngine integration patterns support endpoint provisioning and rule distribution
- –Rule tuning for keystroke capture can increase operational configuration overhead
- –High-volume keystroke telemetry can strain log pipeline throughput
- –Automation depth depends on ManageEngine integration points rather than a generic API-first model
- –Schema flexibility for custom event fields is limited by the DLP data model
Best for: Fits when security teams need keystroke-based DLP enforcement with governed policy rollout.
How to Choose the Right Keystroke Logger Software
This buyer's guide covers keystroke logger software selection across Teramind, Veriato, ActivTrak, GoGuardian, Spyrix, Teramind by Insight, iMonitor, Snagit, Netwrix Auditor, and ManageEngine Endpoint DLP.
It focuses on integration depth, data model design, automation and API surface, and admin and governance controls that affect capture scope, downstream usability, and auditability.
Keystroke-grade monitoring platforms that model typed input as auditable telemetry
Keystroke logger software captures typed input events and links them to identity, endpoint context, and application or session activity so investigations can pivot across related actions. Teramind maps keystrokes into a session and application activity model for faster forensic pivots, while Veriato ties keystrokes to identity and endpoint context using a governance-heavy data model.
Teams use these tools to support compliance investigations, insider-risk review, and security workflows where typed input must be correlated with sessions, devices, and policy configuration changes. ActivTrak supports this with policy-driven keystroke capture tied to session and application metadata in its event schema.
Evaluation criteria for integration, schema control, automation, and governance
Evaluation should start with how typed-input events are represented in the data model and how consistently those events are correlated to sessions, devices, and applications. Teramind and ActivTrak stand out for mapping keystrokes into session and application-aware models that preserve context for investigation and analytics.
Governance and automation matter next because keystroke telemetry volume, retention, and access controls require operational controls rather than ad hoc viewing. Veriato and Teramind by Insight emphasize audit logs and RBAC-style permissions for traceability of who configured monitoring and what changed, while Netwrix Auditor focuses on entity-based audit-log correlation with RBAC-scoped reporting access.
Session and application context mapping in the keystroke event model
Teramind correlates keystroke events with sessions and applications so investigation teams can pivot from typed input to the related activity. ActivTrak similarly ties keystrokes to session and application metadata in its event schema to keep downstream analytics coherent.
RBAC-style access gates for monitoring and investigative workflows
Veriato uses RBAC-style admin permissions that limit access to captured activity and keeps configuration actions traceable through audit logs. Teramind by Insight adds RBAC controls that limit access to session content and investigative workflows.
Audit logs for administrative changes and evidence-grade traceability
Veriato’s audit-log and RBAC governance tracks who configured monitoring and what changed, which supports governance and evidence trails. ActivTrak and iMonitor also include audit trails that record admin changes across monitoring and governance controls and capture scope updates.
Automation and API surface for provisioning, exports, and workflow integration
Teramind explicitly supports an API and automation hooks for data export and integration into existing workflows, which reduces manual extraction steps. ActivTrak also provides export, API access, and workflow hooks, while Veriato supports API-driven integration patterns built around auditable activity capture.
Configurable capture policies and schema-driven control of what gets logged
Teramind supports configurable capture rules so monitoring can be targeted instead of blanket logging, which directly affects throughput and storage load. ActivTrak depends on correctly configured collection policies and maps those policies into an event schema, and GoGuardian enforces class- and user-scoped monitoring policies across managed Chromebooks.
Throughput-aware design for high keystroke volume telemetry
Teramind and Teramind by Insight both call out that high monitoring volume can stress storage and investigation throughput, which makes tuning and policy scope a first-order requirement. Spyrix highlights that throughput tuning depends on deployment design because event volume can constrain search and export workflows.
Decision flow for selecting keystroke logger software with enforceable control
Start by deciding what integration depth is required for typed-input investigations and where the governance records must land. Teramind and Veriato provide an API and automation surface built for operational integration and auditability, while GoGuardian centers on managed endpoint workflows and policy configuration for education fleets.
Then confirm that the data model and admin controls match the required control plane for capture scope, access boundaries, and audit logs. ActivTrak, iMonitor, and Spyrix each depend on correct capture policy configuration, while Netwrix Auditor prioritizes identity and access audit correlation through connectors and RBAC-scoped access to audit data.
Define the required data correlation target
If investigations must pivot from typed input to the exact session and application activity, choose Teramind or ActivTrak for their session and application-aware keystroke models. If investigations must align typed input to broader identity and endpoint entities across systems, include Veriato or Netwrix Auditor for identity and endpoint context with audit-log correlation.
Require schema-level control through policy and capture scope configuration
Select tools that support configurable capture rules rather than only broad monitoring modes, because Teramind targets capture with configurable capture rules and ActivTrak uses policy-driven keystroke capture tied to an event schema. For education environments, GoGuardian enforces class- and user-scoped monitoring policies across managed Chromebooks without custom schema integration.
Validate governance controls with RBAC and auditable admin changes
For regulated teams, prioritize Veriato or Teramind by Insight since both emphasize audit logs that track who configured monitoring and what changed and both apply RBAC-style access boundaries. For teams focused on endpoint scope governance, iMonitor provides RBAC-governed capture configuration with auditable changes tied to endpoint scope.
Map automation and API expectations to each tool’s integration surface
If automation must provision monitoring and push data into existing investigation workflows, confirm Teramind’s API and automation hooks for integration and export. If downstream automation must rely on governed activity telemetry exports and workflow hooks, ActivTrak and Veriato provide API-driven integration patterns aimed at extensibility.
Estimate telemetry throughput risk and plan capture scope tuning
When monitoring volume is high, choose tools that explicitly support targeted capture tuning, since Teramind and Teramind by Insight both note storage and ingest pressure from peak monitoring volume. Spyrix emphasizes that throughput tuning depends on deployment design, so capture scope should be treated as a performance control.
Which teams should buy keystroke logger software for control and traceability
Keystroke logger software fits organizations that need typed-input telemetry correlated with identity and sessions and backed by audit records for governance. Teramind and Veriato target compliance and security investigations that require RBAC, audit logs, and automation hooks.
Some tools fit narrower fleet models where policy scoping is the primary control plane, such as GoGuardian for managed education endpoints, while others fit DLP enforcement patterns where typing signals drive policy actions, such as ManageEngine Endpoint DLP.
Mid-size to enterprise compliance and insider-risk teams that need RBAC, audit logs, and automation hooks
Teramind and Teramind by Insight align keystroke telemetry with sessions and applications and include RBAC and audit logging for evidence trails and investigator access control. Veriato also targets regulated needs with audit-log and RBAC governance that tracks who configured monitoring and what changed.
Security and operations teams that require governed interaction telemetry with event-schema consistency
ActivTrak ties keystrokes to user, device, and application session context using a policy-driven keystroke capture pipeline and includes audit trails for admin changes. This pairing supports consistent downstream analytics via schema mapping and export or API access.
Education districts that must enforce monitoring policies across managed student Chromebooks
GoGuardian provides centralized admin workflows for class and user grouping and enforces class- and user-scoped monitoring policies across managed Chromebooks. The integration model is policy and managed-device driven rather than a documented keystroke API export focus.
Identity, access, and cross-system audit teams that want RBAC-scoped audit correlation
Netwrix Auditor correlates entity activity across directory, endpoints, and Microsoft 365 and offers RBAC-scoped access to audit reports. It can integrate with endpoint monitoring workflows that may include keystroke capture from connected tooling, which suits organizations already centered on audit-log correlation.
Security teams using endpoint DLP policies that must tie typing behavior to data exfiltration controls
ManageEngine Endpoint DLP uses a structured DLP data model with endpoint keystroke and content event policies tied to correlated enforcement and governance audit logs. This fits when typed input signals are needed to trigger or support DLP outcomes rather than when keystrokes are only for investigation.
Common buying pitfalls that break integration, governance, or performance
A frequent failure mode is choosing a tool without verifying that keystroke events are mapped to the session and application context required for investigations. Teramind and ActivTrak explicitly map keystrokes into session and application activity models, while Snagit is not designed around a keystroke event schema and lacks documented keystroke capture mode.
Another failure mode is ignoring operational impact from high monitoring volume and poorly scoped capture policies. Teramind and Teramind by Insight both highlight storage and ingest pressure at peak volume, and Spyrix notes throughput tuning depends heavily on deployment design.
Choosing a non-keystroke telemetry tool for keystroke governance
Snagit captures screen activity with video and annotation, but it lacks a documented keystroke event schema and does not provide RBAC, audit log retention, or access-controlled telemetry for typed input. For keystroke-grade monitoring and governance, use Teramind, Veriato, or ActivTrak instead.
Assuming keystroke data is exportable and automatable without checking the integration surface
GoGuardian centers on policy configuration and managed endpoint workflows for Chromebooks and provides limited evidence of keystroke event export via third-party API. If automation and integration into existing workflows are required, Teramind and ActivTrak provide an API and workflow hooks oriented around export and downstream processing.
Skipping governance validation for RBAC boundaries and audit logs
Tools like Spyrix have limited external validation of RBAC granularity and admin role controls, which increases the risk of unclear access boundaries. Veriato and Teramind by Insight emphasize audit log coverage tied to configuration changes and RBAC-style permissions.
Under-scoping capture policies and then discovering throughput and retention issues late
Teramind and Teramind by Insight warn that capture volume can stress storage and investigation throughput, and retention and scope tuning require careful configuration to avoid data overshare. ActivTrak also depends on correctly configured collection policies, and iMonitor relies on capture scope configuration that is auditable for governance.
How We Selected and Ranked These Tools
We evaluated Teramind, Veriato, ActivTrak, GoGuardian, Spyrix, Teramind by Insight, iMonitor, Snagit, Netwrix Auditor, and ManageEngine Endpoint DLP on the strength of their keystroke event features, ease of use, and value signals. Each tool received an overall score as a weighted average where features carried the most weight, while ease of use and value each contributed a meaningful share. This criteria-based scoring used the same categories across all ten products and produced the ordering without relying on hands-on lab testing or private benchmarks.
Teramind separated itself by mapping keystroke capture into a session and application activity model for forensic pivots, which lifted it strongly through the features factor and also aligned with higher ease-of-use and value signals for governance and investigation workflows.
Frequently Asked Questions About Keystroke Logger Software
How do Teramind and Veriato differ in their data model for keystroke evidence?
Which tools provide automation hooks and an API surface for administering monitoring policies?
What integration paths exist for sending keystroke or activity logs into downstream workflows?
How do RBAC and audit logs differ between ActivTrak and iMonitor?
Which products work best for governed monitoring across managed endpoints with policy scoping?
Can keystroke logging be configured to correlate events by user, device, and application context?
What security controls matter most when setting up keystroke capture scope?
How do teams handle data migration when moving between keystroke logging platforms?
What are common operational failures when deploying keystroke loggers, and how do the tools mitigate them?
Why is Snagit usually a poor substitute for keystroke logging in evidence and governance workflows?
Conclusion
After evaluating 10 cybersecurity information security, Teramind stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Cybersecurity Information Security alternatives
See side-by-side comparisons of cybersecurity information security tools and pick the right one for your stack.
Compare cybersecurity information security tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.