Deploy Voyager where your information lives

Voyager can be deployed in multiple patterns, from a single-computer environment to a distributed architecture with dedicated platform services, index nodes, coordination services, and remote Indexing Agents.

The appropriate topology depends on data scale, update rates, query workload, availability needs, network boundaries, source locality, security requirements, and operations.

Distributed processing

Indexing Agents can be positioned closer to source information.

This allows source discovery, extraction, and processing to be distributed across computing environments instead of requiring all work to happen at a single central node.

Scale the index separately

Voyager uses Apache Solr as its indexing and query foundation.

Distributed deployments can use Solr collections, shards, and replicas to support scalability and availability. ZooKeeper provides coordination for distributed index environments.

Operating environments

Current Voyager documentation describes Windows, Linux, hybrid, and containerized deployment patterns, including Kubernetes-based approaches.

Exact operating-system support, installation requirements, and component compatibility are release-specific and should be confirmed against the relevant current product documentation.

Design around the workload

A Voyager deployment is sized and configured around the actual information environment.

Important design factors include source location, source type, amount of information, rate of change, extraction and enrichment workload, query volume, availability objectives, security domains, network topology, recovery requirements, and operational ownership.