GITNUXSOFTWARE ADVICE
Aerospace DefenseTop 10 Best Space Situational Awareness Services of 2026
Ranked comparison of Space Situational Awareness Services for technical buyers, covering GMV, Leonardo, Serco, and other providers.
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.
GMV
RBAC plus audit log coverage for SSA pipeline changes and access boundaries.
Built for fits when operations teams need governed integrations and repeatable SSA automation across partners..
Leonardo
Editor pickRBAC plus audit log coverage aligned to API-driven data pipeline operations.
Built for fits when governed SSA pipelines need API automation and shared data schema..
Serco
Editor pickOperational SSA workflow integration with schema-driven ingestion and governed audit traceability.
Built for fits when operations teams need governed SSA integration and repeatable automation workflows..
Related reading
Comparison Table
This comparison table maps Space Situational Awareness Services providers by integration depth, data model, automation and API surface, and admin and governance controls. It highlights how each vendor structures schemas, supports provisioning, and exposes extensibility for tasks like ingesting observations, correlating tracks, and managing RBAC. Readers can use the dimensions to assess configuration options, audit log coverage, and the expected throughput characteristics of each platform.
GMV
enterprise_vendorGMV delivers space surveillance, SSA data exploitation, and mission support services that integrate sensor data into operational decision workflows for defense customers.
RBAC plus audit log coverage for SSA pipeline changes and access boundaries.
GMV’s SI services fit teams that need end-to-end ingestion to product generation, then to distribution via automation and API surface. The data model approach emphasizes schema definitions for entities like tracks, objects, events, and derived products, which reduces drift across pipelines. API and automation are built to support high-throughput processing and repeatable job runs, rather than manual export and upload cycles.
A concrete tradeoff is that deeper governance and schema rigor adds setup time for organizations that only need one-off outputs. GMV fits best when production operations require consistent provenance, RBAC, and audit logs across multiple stakeholders and mission partners. A common usage situation is integrating catalog and tracking outputs into an operator workflow that triggers downstream alerts and reporting based on events.
- +Integration depth across sensors, catalogs, and downstream automation
- +Data model with explicit schemas for consistent object and event handling
- +API and automation surface supports repeatable high-throughput workflows
- +Governance controls include RBAC and audit logging for traceability
- –Schema and governance setup adds initial integration overhead
- –Customization for niche workflows may require more engineering effort
Space operations integration teams
Provision API-driven SSA product pipelines
Fewer manual handoffs
Mission partner data teams
Standardize objects and event schemas
Reduced data inconsistencies
Show 2 more scenarios
Security and compliance owners
Enforce RBAC and auditability
Stronger traceability
Controls user permissions and captures change history for governed SSA operations.
Automation engineers
Run scheduled processing and distribution
Higher operational throughput
Uses API automation to trigger processing jobs and downstream dissemination reliably.
Best for: Fits when operations teams need governed integrations and repeatable SSA automation across partners.
More related reading
Leonardo
enterprise_vendorLeonardo offers SSA systems engineering and operational support services that combine surveillance, data processing, and integration into defense programs.
RBAC plus audit log coverage aligned to API-driven data pipeline operations.
Leonardo fits organizations that run end-to-end SSA services where observation ingest, catalog enrichment, and downstream tasking must share one schema and one configuration path. Its integration depth is strongest when multiple producers and consumers connect through APIs with automation hooks for ingestion, validation, and job orchestration.
A practical tradeoff is higher engineering effort for schema governance and API orchestration compared with less structured toolchains. A common usage situation is deploying a governed data model for conjunction analysis inputs across teams, then automating nightly pipeline runs with RBAC and audit log trails to support reviews and incident investigation.
- +Strong API automation surface for ingest, validation, and orchestration
- +Consistent schema approach improves integration across SSA pipelines
- +RBAC and audit log support governance for operational workflows
- +Extensibility supports custom transforms and pipeline stages
- –Schema governance work increases setup effort for small teams
- –Deeper API orchestration requires disciplined configuration management
Flight dynamics and SSA engineering
Automate ingestion to conjunction inputs
Faster, consistent pipeline runs
Program and mission data managers
Enforce schema and access controls
Governed data access and auditing
Show 2 more scenarios
Integration teams and platform ops
Connect multiple SSA systems via API
Lower integration friction
APIs and extensibility allow connecting catalogs, processing steps, and consumers with shared model.
Data science operations teams
Schedule enrichment and quality checks
More reliable data quality gates
Automation surface supports repeatable ETL stages and throughput-aware job orchestration patterns.
Best for: Fits when governed SSA pipelines need API automation and shared data schema.
Serco
enterprise_vendorSerco delivers defense space services and operations support that include SSA-related monitoring, analytics integration, and program execution under government contracting.
Operational SSA workflow integration with schema-driven ingestion and governed audit traceability.
Serco fits teams that need SSA services connected to existing mission and ground-system workflows rather than isolated analytics. The data model focus supports schema-driven ingestion and transformation across tasking, catalogs, and event reporting. Admin and governance controls are oriented around controlled access, change management, and traceability via audit logs. Extensibility tends to be realized through integration points that support provisioning and workflow configuration.
A tradeoff appears when organizations expect a developer-first, self-serve sandbox for rapid schema experimentation. Serco fits best when throughput requirements are steady and integrations must be managed with stable configuration and change control. A common usage situation is adding or updating ingestion sources and mapping them into the governed SSA data model for downstream automation.
- +Integration-centric delivery for mission and ground workflows
- +Schema-driven SSA data model supports controlled transformations
- +Governed automation with audit log and RBAC style controls
- +Extensibility through integration points and provisioning
- –Developer-first sandboxing for rapid experimentation is limited
- –Schema changes require managed governance and coordinated updates
Mission operations teams
Automate SSA tasking-to-reporting
Faster operational decisions
Space domain integration teams
Unify multi-source SSA ingestion
Lower integration rework
Show 2 more scenarios
Program governance leads
Control access and change management
Stronger compliance posture
Apply RBAC-style permissions and capture audit logs for configuration and data pipeline changes.
Ground system engineering
Integrate SSA into existing pipelines
Reduced manual handoffs
Use API and automation surfaces to route SSA outputs into downstream systems at required throughput.
Best for: Fits when operations teams need governed SSA integration and repeatable automation workflows.
Kongsberg Defence & Aerospace
enterprise_vendorKongsberg supports SSA and defense space surveillance services that connect sensor inputs to operational command-and-control information flows.
Role-based access control with audit logging for governed SSA provisioning and operations
Space Situational Awareness service comparisons often hinge on integration depth and control depth, and Kongsberg Defence & Aerospace differentiates through its defence-grade engineering focus and systems integration heritage. Core value centers on SSA data processing, sensor and tasking integration, and operational support for tracking and characterization workflows across organizational boundaries.
The service emphasis aligns with configuration-driven provisioning of feeds and interfaces, plus governance mechanisms like role-based access control and audit logging for traceability. Automation and API surface are key evaluation points, especially for turning SSA tasks into repeatable, monitored data flows.
- +Defence integration heritage supports complex SSA interfaces and operational workflows
- +Configuration-driven provisioning fits feed onboarding and schema alignment across partners
- +Governance controls include RBAC and audit logging for traceable operations
- +Extensibility supports integrating additional sensors and downstream consumers
- –API and automation surface details require direct technical engagement for verification
- –Deep integration can add delivery overhead for teams needing rapid standalone use
- –Data model specifics for schema mapping and normalization are not fully transparent publicly
- –Throughput and latency characteristics depend on system architecture and deployment scope
Best for: Fits when defence-adjacent programs need controlled SSA integrations and governed automation interfaces.
Thales
enterprise_vendorThales provides SSA-related engineering and integration services that support space surveillance architectures, data handling, and system-level integration for defense use cases.
Governed, schema-driven SSA data processing with RBAC-style administrative controls and auditability.
Thales delivers Space Situational Awareness Services that emphasize integration into existing operational environments and data handling pipelines. The offering centers on SSA data ingestion, event processing, and space object characterization workflows that can be governed across multiple user roles.
Integration depth is supported through documented interfaces and schema-driven data modeling patterns that fit downstream analytics, alerting, and tasking systems. Automation and API surface are designed for repeatable processing runs with traceable administrative controls, including access boundaries and auditability.
- +Integration patterns map SSA products into controlled operational data workflows
- +API-first automation supports repeatable ingestion to processing pipelines
- +Schema-driven data modeling improves consistency across feeds and services
- +Governance controls align with role-based access and restricted administration
- +Audit-oriented operation supports traceability of changes and access
- –Deep integration requires clear upstream data contract alignment
- –Automation coverage depends on the specific SSA service scope selected
- –Multi-tenant governance setup can add admin overhead for small teams
- –Throughput tuning needs careful configuration of ingest and processing steps
Best for: Fits when agencies require controlled SSA integrations with automation, schema discipline, and governance.
Lockheed Martin
enterprise_vendorLockheed Martin delivers defense SSA engineering and integration services that support space tracking, data exploitation, and operational deployment in major programs.
Operational governance with audit-oriented access controls across SSA data ingestion and tasking workflows.
Lockheed Martin fits organizations that need tight integration with defense-grade data handling for Space Situational Awareness Services. Its delivery model emphasizes government-aligned engineering processes, structured data workflows, and controlled operational access for space monitoring use cases.
Integration depth tends to center on mission data ingest, correlation workflows, and service-to-service provisioning with traceable governance. Automation and API surface are typically oriented around operational tasking, data exchange contracts, and managed interfaces rather than broad consumer-style tooling.
- +Governance-aligned engineering practices for controlled space monitoring operations
- +Integration focus on mission data ingest and correlation workflows
- +Role-based access support with auditability for operational changes
- +Data contracts that support extensibility across sensing and analytics feeds
- –API surface is oriented to operational interfaces rather than broad developer self-service
- –Schema and data model alignment may require partner work for complex deployments
- –Automation depth depends on integration scope and required operational control
- –Throughput tuning requires engineering involvement for high-volume ingest
Best for: Fits when government or defense contractors need controlled integration for SSA operations.
Raytheon Intelligence & Space
enterprise_vendorRaytheon Intelligence & Space provides SSA-adjacent defense services that include sensor data processing and integration for operational space situational awareness.
Governance-first operational audit logging tied to RBAC-style access controls.
Raytheon Intelligence & Space delivers space situational awareness services with a focus on integration depth across defense-grade data feeds and operational workflows. The provider supports orchestration of SDA inputs through defined data pipelines, with attention to schema consistency across ingestion, tasking, and derived products.
Automation and API surface align to governance needs such as RBAC-style access partitioning and auditable operational activity for multi-stakeholder environments. Configuration controls emphasize repeatable provisioning for new missions, sensors, and downstream consumers.
- +Integration depth across SDA inputs and downstream operational workflows
- +Defined data pipelines that preserve schema consistency from ingestion to products
- +Automation-oriented interfaces for repeatable provisioning across missions
- +Governance controls for RBAC-style access partitioning and auditability
- –Extensibility depends on approved integration paths and partner onboarding
- –Higher integration lift for teams needing custom data model extensions
- –API surface documentation may require program-level alignment for coverage
- –Throughput tuning is most straightforward inside supported deployment patterns
Best for: Fits when defense and government teams need tightly governed SDA integration and automation.
KBR
enterprise_vendorKBR delivers defense program engineering and data integration services that can support SSA system integration, operational workflows, and governance controls in delivery programs.
Systems-engineered SSA integration that supports repeatable provisioning of analysis workflows and governed access.
KBR delivers Space Situational Awareness Services with an engineering focus on integrating SSA data sources into operations-ready workflows. Core capabilities center on ingestion, custody, and analysis of space object data to support tracking, characterization, and conjunction risk use cases.
Integration depth is shaped by KBR's systems engineering approach, which typically spans ground segment data handling and downstream decision workflows. Automation and API surface are present through integration points that enable data model mapping, repeatable processing, and governed access for multiple users and systems.
- +Integration-focused SSA workflows that connect tracking data to downstream operations
- +Engineering delivery approach supports complex data model mapping across sources
- +Governed access patterns align with RBAC and audit log needs in missions
- +Extensibility for adding analysis steps within existing processing chains
- –API surface details for third-party automation are not consistently documented publicly
- –Data model schema availability and customization paths can require deeper engagement
- –Throughput tuning for high-frequency ingestion workloads may depend on integration scope
Best for: Fits when mission teams need systems-engineered SSA integration with strong governance controls.
How to Choose the Right Space Situational Awareness Services
This buyer's guide covers Space Situational Awareness services delivered by GMV, Leonardo, Serco, Kongsberg Defence & Aerospace, Thales, Lockheed Martin, Raytheon Intelligence & Space, and KBR. It focuses on integration depth, the underlying data model and schema approach, automation and API surface, and admin and governance controls.
The guide maps these providers to concrete evaluation criteria like RBAC and audit log coverage, repeatable provisioning workflows, and schema-driven ingestion and transformation. It also calls out common failure modes seen in integration-heavy delivery programs, including governance setup overhead and limited sandboxing for rapid experimentation.
Space surveillance ingestion, correlation, and tasking services built around a governed data model
Space Situational Awareness services take multi-source space observations and sensor-derived data, then normalize them into consistent schemas for ingestion, storage, transformation, and operational exploitation. These services connect SSA pipelines to mission execution workflows like tracking, characterization, tasking, and downstream consumer exchange.
Providers like GMV deliver sensor-to-workflow integration with explicit schemas and a documented API surface for repeatable automation. Leonardo pairs the same schema discipline with API-driven provisioning and orchestration for ingest, validation, and pipeline stages used in defense programs.
Evaluation criteria for governed SSA integration: schema, API automation, throughput, and control depth
Integration depth matters because SSA pipelines span sensors, catalogs, ingestion services, transformations, and downstream decision workflows. GMV stands out for integration across sensors, catalogs, and operational products while keeping access boundaries and change traceability governed.
Admin and governance controls matter because SSA operations involve multi-team handoffs and cross-system exchanges. Leonardo, Thales, and Raytheon Intelligence & Space each emphasize RBAC-style controls and audit-oriented traceability tied to pipeline operations.
Governed data model with explicit schemas
GMV delivers a data model with explicit schemas for consistent object and event handling across SSA pipeline steps. Leonardo and Thales use schema-driven modeling patterns to keep ingest and transformation outputs consistent for downstream analytics, alerting, and tasking systems.
Integration depth across sensors, catalogs, and downstream workflows
GMV integrates sensor data into operational decision workflows and covers sensor, catalog, and downstream automation paths. Serco emphasizes operational integration between SSA data collection, processing workflows, and mission tasking support tied to ground and mission operations.
API and automation surface for repeatable provisioning
GMV supports automation and extensibility through configurable schemas and repeatable provisioning for tasking, processing, and dissemination. Leonardo and Serco focus automation-oriented interfaces that support repeatable ingestion and orchestration across missions and cross-system exchange.
RBAC-style access controls and audit log coverage
GMV provides governance controls that include RBAC and audit logging for traceability of SSA pipeline changes and access boundaries. Kongsberg Defence & Aerospace, Thales, and Raytheon Intelligence & Space pair role-based access control with audit logging for governed SSA provisioning and operations.
Schema change governance and configuration discipline
Leonardo and Serco both tie schema work to governance effort because schema changes require controlled updates across pipeline stages. Kongsberg Defence & Aerospace emphasizes configuration-driven provisioning for feed onboarding and schema alignment across partners, which helps manage change impact during integration.
Extensibility paths that preserve governance
GMV and Leonardo support extensibility through configurable schemas and custom transforms aligned to controlled configuration management. Raytheon Intelligence & Space and KBR emphasize repeatable provisioning of new missions, sensors, and downstream consumers while limiting extensibility to approved integration paths.
A decision framework for selecting a SSA provider with the right integration and governance controls
Selection should start with the integration endpoints and the governance requirements of the SSA workflow, not with the sensor count. GMV is a strong fit when integrations must span sensors, catalogs, and downstream operational automation with governed change control.
Next, validate the automation and admin surface that will run the pipeline in production. Leonardo, Thales, and Raytheon Intelligence & Space emphasize RBAC and audit log coverage aligned to API-driven pipeline operations, which reduces control gaps during multi-stakeholder execution.
Map integration breadth to the provider's end-to-end workflow coverage
If the target workflow spans sensor inputs, catalog normalization, and operational products, GMV and Serco match that integration breadth because they connect SSA data collection to mission execution and downstream exchange. If the workflow is centered on defense-grade sensor processing stages that feed operational command-and-control information flows, Kongsberg Defence & Aerospace aligns through its configuration-driven provisioning of feeds and interfaces.
Confirm the data model and schema contract for objects and events
GMV and Leonardo provide explicit schema approaches for consistent object and event handling so ingestion outputs remain stable across pipeline steps. Thales also uses schema-driven data modeling patterns to keep SSA products aligned to downstream analytics, alerting, and tasking systems.
Evaluate the automation surface that provisions and runs pipelines
For teams that require repeatable tasking, processing, and dissemination, GMV supports automation and extensibility through configurable schemas and repeatable provisioning. Leonardo and Serco focus automation-oriented orchestration through API-driven provisioning for ingest validation and pipeline stages.
Stress-test governance controls for multi-team execution and change traceability
If RBAC and audit log coverage for pipeline changes is a hard requirement, GMV, Kongsberg Defence & Aerospace, Thales, and Raytheon Intelligence & Space provide explicit emphasis on role-based access and audit logging for traceability. Lockheed Martin also emphasizes operational governance with audit-oriented access controls across SSA ingestion and tasking workflows.
Plan for schema change overhead and configuration discipline
If internal teams cannot sustain schema governance work, Leonardo and Serco can add integration overhead because schema changes require managed governance and coordinated updates. Kongsberg Defence & Aerospace and Thales reduce integration churn by using configuration-driven feed provisioning and schema-driven processing patterns that align onboarding with normalization.
Which organizations should match which SSA provider based on operational goals
SSA service selection differs by how tightly the workflow is coupled to mission operations and how much automation must run under governance controls. GMV, Leonardo, and Serco target teams that need repeatable automation across partners or missions with explicit schema discipline.
Defense-adjacent programs and government-aligned contractors often prioritize controlled integration into existing operational environments with traceable access boundaries. Kongsberg Defence & Aerospace, Thales, Lockheed Martin, Raytheon Intelligence & Space, and KBR align to those operational and governance-centric deployment patterns.
Operations teams needing governed SSA automation across partners and downstream workflows
GMV fits this segment because it integrates sensors, catalogs, and downstream operational decision workflows with RBAC plus audit log coverage for SSA pipeline changes. Serco also fits because it emphasizes operational SSA workflow integration with schema-driven ingestion and governed audit traceability.
Programs that require API-driven provisioning with shared schema discipline
Leonardo fits teams that need API automation for ingest validation and orchestration while keeping ingest and transformation outputs consistent via structured schemas. Thales fits when governance and schema discipline must align to multiple roles and traceable processing of SSA events.
Defense and government teams executing tightly governed SDA integration and automation
Raytheon Intelligence & Space fits multi-stakeholder environments because it ties governance-first operational audit logging to RBAC-style access partitioning. Lockheed Martin fits when operational tasking and data exchange contracts require audit-oriented access controls across ingestion and tasking workflows.
Defense-adjacent programs that need controlled sensor and tasking integration across organizational boundaries
Kongsberg Defence & Aerospace fits programs that require role-based access control and audit logging for governed SSA provisioning plus configuration-driven feed onboarding. KBR fits mission teams that need systems-engineered SSA integration with repeatable provisioning of analysis workflows and governed access for multiple users and systems.
Common integration and governance mistakes in SSA provider selection
SSA integrations fail most often when governance and schema contracts are treated as implementation details instead of product-level requirements. Schema setup and configuration discipline create real overhead for teams that underestimate the change governance work.
Automation surface clarity also affects outcomes because some providers emphasize operational interfaces rather than broad developer self-service. Limited sandboxing or constrained extensibility can slow early experimentation and increase rework when integration assumptions change.
Choosing a provider without a clear RBAC and audit log plan for pipeline changes
A missing audit trail becomes a process risk during multi-team handoffs because SSA pipeline changes and access boundaries must remain traceable. GMV, Leonardo, Kongsberg Defence & Aerospace, Thales, and Raytheon Intelligence & Space explicitly emphasize RBAC and audit log coverage aligned to pipeline operations.
Underestimating schema governance setup overhead for multi-stage SSA pipelines
Schema governance adds initial setup overhead in providers like GMV and Leonardo because explicit schemas and governed setup require coordinated configuration. Serco and Thales also tie controlled schema processing to role-based governance, so schema change coordination should be planned as part of the integration plan.
Assuming extensibility is open-ended without approved integration paths
Raytheon Intelligence & Space and KBR indicate extensibility depends on approved integration paths and partner onboarding, which can slow custom data model extensions. GMV and Leonardo provide more extensibility through configurable schemas and custom transforms, but they still require disciplined configuration management.
Expecting rapid developer experimentation when sandboxing is limited
Serco shows that developer-first sandboxing for rapid experimentation can be limited, which increases the need for controlled test environments in the integration plan. GMV and Leonardo emphasize repeatable provisioning workflows, which can support repeatable testing if the pipeline provisioning is part of the delivery scope.
Selecting based on operational integration depth while neglecting automation and API surface verification
Kongsberg Defence & Aerospace notes that API and automation surface details require direct technical engagement for verification, which can hide integration gaps until late. GMV and Leonardo put more weight on a documented API and automation surface for repeatable high-throughput workflows.
How We Selected and Ranked These Providers
We evaluated GMV, Leonardo, Serco, Kongsberg Defence & Aerospace, Thales, Lockheed Martin, Raytheon Intelligence & Space, and KBR on capabilities, ease of use, and value, then produced an overall score as a weighted average in which capabilities carried the most weight while ease of use and value each accounted for a smaller share. Editorial research and criteria-based scoring used only the provided provider descriptions, named strengths like RBAC plus audit log coverage and schema-driven ingestion, and named constraints like governance setup overhead and limited sandboxing.
GMV separated from lower-ranked providers because it combines explicit schemas with a documented API and governed automation for repeatable tasking, processing, and dissemination. That specific combination lifted capabilities through integration depth across sensors, catalogs, and downstream workflows while governance controls like RBAC plus audit logging supported controlled handoffs.
Frequently Asked Questions About Space Situational Awareness Services
Which providers offer the deepest API coverage for integrating SSA data pipelines and downstream workflows?
How do the leading SSA platforms handle governed data models and schema consistency across ingestion and characterization?
What SSA vendors provide RBAC, audit logs, and administrative controls for change governance in automated pipelines?
Which providers are better suited for repeatable provisioning when onboarding new missions, sensors, or downstream consumers?
How do SSA services typically migrate existing data models or operational workflows into a new platform?
Which providers support extensibility via configuration rather than manual rework of ingestion or processing components?
What tradeoffs appear when choosing between defense-focused SSA integration and broader operational integration?
Which vendors best support end-to-end operational tasking workflows tied to SSA mission operations?
What are common integration failure modes when connecting SSA pipelines to other systems, and who mitigates them most directly?
Conclusion
After evaluating 8 aerospace defense, GMV 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
Aerospace Defense alternatives
See side-by-side comparisons of aerospace defense tools and pick the right one for your stack.
Compare aerospace defense 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.