/
HQ 2.0 and Voyager Server 3.0 Release Notes

HQ 2.0 and Voyager Server 3.0 Release Notes

Dec 8, 2025

About This Release

We’re excited to introduce HQ 2.0 and Voyager Server 3.0. This update delivers performance improvements, enhanced security and new productivity features that make it easier than ever for your team to search, protect and manage data at scale.

What’s New

HQ 2.0 and Voyager Server 3.0 represent a step forward in platform modernization, delivering improvements in speed, security and overall stability. With these upgrades, the foundation supporting your searches, indexing workloads and integrations becomes faster, more secure and more scalable.

Modernized Search Engine Core
This release includes a modernized search engine foundation designed for smoother performance at every scale. Both search queries and indexing pipelines have been optimized to keep systems responsive, even as data and user demand grow. The result is a faster, more stable experience across the platform.

Library and Framework Upgrades

This release includes a comprehensive refresh of Voyager’s underlying libraries and frameworks to boost performance, strengthen security and ensure long-term compatibility.

We’ve modernized Voyager’s foundation across the stack—updating core search/data libraries, the web and networking layer, distributed services, security/auth and encryption, data connectivity, geospatial and text content parsing, plus updated components that handle Microsoft Office files and the native system libraries Voyager relies on. For you, this means faster indexing, more reliable integrations with enterprise and cloud systems, cleaner Office/PDF parsing and previews, and stronger protection against known vulnerabilities—all on a more resilient, future-ready platform that’s easier to operate and scale.

Enhancements

  • Secure licensing and protected configuration secrets

    • Voyager’s security model has been strengthened with modern AES-based encryption that meets FIPS-validated standards. In addition to securing license files, Voyager now encrypts all passwords and sensitive secrets stored in configuration files, providing stronger protection across distributed and cloud environments. All new licenses now use this enhanced V3 encryption format, offering improved safeguards against tampering or misuse. To ensure a smooth transition, Voyager continues to support existing license formats and includes an interoperability mode so customers can migrate at their own pace.

  • Expanded data & file handling

    • Voyager can now gracefully index geodatabases (GDB) even when the “name” field is missing.

    • Improved handling of large archive files (.tgz) and Word documents regardless of uppercase extension (e.g., .DOCX), ensuring consistency across formats.

    • KML and KMZ files are now handled consistently under a single file filter, ensuring both formats are indexed and managed in the same way.

    • Improved support for ArcGIS Pro projects, including accurate thumbnails and geometries, as well as proper handling of nested group layer hierarchies.

    • ArcGIS layer files (.lyrx) now indexed more accurately — capturing complete metadata and applying the correct file-based names, so your map layers are easier to find and manage.

    • Feature class names from file geodatabases are now indexed correctly for more accurate search results.

  • Smarter filtering & configuration

    • Advanced filtering is now easier to manage with clearer UI feedback, descriptive labels, and automatic updates, reducing errors and giving administrators greater clarity and control.

    • The built-in JavaScript editor used for pipeline step configuration has been refreshed for better usability when creating or maintaining custom scripts.

    • Troubleshooting worker failures used to be difficult because job status updates lacked unique identifiers. PullJobs messages now include a VPID ‘tracking number’ for each job, giving administrators clearer visibility into processing activity and making it faster to pinpoint and resolve issues.

    • Administrators can now remove agents directly from the HQ interface, simplifying agent lifecycle management and making it easier to clean up inactive or redundant agents without backend work.

  • User experience improvements

    • Updated UI layout in the pipeline step configuration pages, ensuring options and parameters display correctly for a clearer and more reliable setup experience.

    • The ‘Show Home Page’ option has been updated to redirect to the Navigo landing page, making navigation smoother and more intuitive.

    • We have updated Navigo documentation links. Users can now reliably access help and support materials directly from the user interface.

    • Map visualizations in Navigo have been improved. Heat maps have been updated, enabling users to analyze data density and patterns, while Mapbox basemaps render properly on the home page and item detail views, ensuring maps are clear and informative across the platform.

    • Email (SMTP) settings have been improved. Previously, changes such as disabling authentication could appear incorrectly after a refresh. The UI now reliably reflects the true configuration, giving administrators confidence that their email settings are applied as intended.

  • Containerization

    • We recognize that containerized deployments—particularly through Kubernetes—are a priority for many of our enterprise customers. This remains a key focus area for Voyager, and we are actively investing in this capability through more robust Kubernetes-based deployment support this release .

Bug Fixes

  • Indexing & agents

    • Agents no longer go idle during distributed indexing, ensuring large jobs complete without interruption.

    • Indexing from AWS S3 is now more reliable and easier to manage. Connections to S3 buckets work without failures, and administrators can confidently assign agent groups to handle workloads, ensuring cloud-hosted data is ingested smoothly and without errors

    • The Spatial Classification pipeline step now executes correctly, accurately tagging documents with geographic context.

    • Under certain conditions, indexing large S3 collections with record limits caused both HQ’s built-in agent and Linux remote agents to hang indefinitely. Indexing jobs on Linux agents now complete as expected. This fix ensures indexing tasks finish properly, improving reliability and preventing stalled jobs during large-scale or cloud-hosted data ingestion.

    • Cloud Optimized GeoTIFF (COG) extraction now works correctly in HQ 2.0. With this fix, COG files index and extract as expected, ensuring smoother workflows for teams working with cloud-optimized raster data.

    • The Spatially Classify Documents pipeline step now works correctly across secured and Flex Index environments. Authentication issues previously prevented the step from accessing the internal gazetteer when anonymous access was disabled, and RHEL deployments connected to Flex Index were unable to complete spatial classification. These issues have been resolved, allowing documents to be accurately classified by location in all supported deployment configurations.

    • The Preview tool now works correctly across all repositories. It previously failed to open file previews for common document and text formats, making it difficult for users to quickly inspect content before indexing. With this fix, users can reliably preview files, streamlining review and validation workflows.

    • Lidar files now index successfully in RHEL environments.

  • System stability

    • HQ now launches reliably in environments where the Python module is installed. Customers can run HQ smoothly with python environments without configuration errors.

    • HQ and Agent now start correctly on fresh installations in FIPS-enabled RHEL environments. A setup issue prevented the system from generating the required security token, which caused the HQ and Agent interfaces to be inaccessible after installation. This fix ensures the security token is created properly, allowing customers to complete installation and access HQ/Agent without interruption.

    • Python RPM packages are now built and available for Red Hat environments. This update enables teams to install and test Python-based plugins and custom connectors on RHEL systems, ensuring full compatibility and supporting advanced Python-driven workflows.

  • Saved Searches & notifications

    • Date ranges now apply correctly to saved search notification triggers, and notifications consistently reflect new indexed content.

    • Saved Searches can now be shared seamlessly with user groups. Previously, users could create searches but not share them, limiting collaboration. With this fix, teams can easily distribute and access Saved Searches, making it simpler to share insights across the organization.

    • Default saved searches such as ‘Most Commonly Used Data’ or ‘Duplicate Files’, now work as expected, helping users quickly surface important datasets without extra effort.

    • Saved Searches now initialize automatically after a fresh install of Server 3.0. Administrators no longer need to manually restore them, saving time and ensuring a smoother setup experience.

  • Navigo fixes

    • ESRI Geocoder configurations no longer break click-to-select suggestions.

    • For map services, metadata “Used By” relationships now display properly for better dependency tracking.

    • Search suggesters now build reliably in Server 3. Previously, errors prevented them from working, breaking autocomplete functionality. With this fix, users benefit from fast, accurate type-ahead suggestions that make finding content quicker and easier.

    • Autocomplete search suggestions in Navigo now work correctly in Server 3.0 standalone deployments.

    • Names for indexed feature and map services now display correctly. Previously, the ‘name’ field was mistakenly set to the same value as the ‘namespaces’ field, causing confusing and inaccurate item names. With this fix, Voyager assigns the proper name, making indexed services easier to identify and work with.

    • Relationship views now show complete information — including thumbnails, names, and titles — so users can easily understand how items are connected.

    • Expanded Search in Navigo now behaves correctly. Certain queries returned invalid or empty results when Enhanced Search was enabled — especially after clearing filters — which made search results unpredictable. These issues have been resolved, ensuring that Expanded Search returns accurate results and filters reset cleanly so users can confidently explore and refine their searches.

    • The ‘Remove Items from Index’ task now works correctly for bulk removals. Users previously encountered errors when trying to delete items returned from a search query. This fix ensures that administrators can reliably remove multiple items from the index in a single action, making index maintenance faster and easier.

    • Shapefiles inside ArcGIS Pro projects now index correctly, allowing users to view and work with these layers without errors.

    • Thumbnails for ArcGIS Online basemap layers now display correctly. An issue in the thumbnail URL caused images to appear blank and, in some cases, triggered indexing warnings. With this fix, these layers index cleanly and show accurate previews, making it easier for users to recognize and work with ArcGIS Online basemap content.

    • Access controls now function correctly in RHEL environments. This fix ensures that security filters from VGP tokens are enforced as intended, so organizations can confidently restrict access to sensitive data.

 

Why Upgrade?

Upgrading to HQ 2.0 and Voyager Server 3.0 gives your organization a faster, more secure, and more reliable platform for search and data management. Modernized libraries and frameworks bring improved security, speed, and seamless integration with enterprise and cloud environments. Combined with numerous feature enhancements and usability improvements, this release strengthens day-to-day workflows for both end users and system administrators.

To make things simple, we’ve provided a set of step-by-step upgrade guides to walk you through the available options for migrating your previous version to this new release. For detailed guidance, please refer to the HQ 2.0 / Server 3.0 Migration Guide.