GITNUXSOFTWARE ADVICE
Technology Digital MediaTop 10 Best Cable Tv Automation Playout Software of 2026
Ranked roundup of top cable tv automation playout software for broadcast teams, with tools like EVS IPDirector, Imagine MCR, and Grass Valley.
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
Imagine Communications Versio is the best fit if your cable TV operation needs governed, multi-channel playout automation tied into existing media workflows, whereas Amagi Cloudport suits teams that want repeatable cloud playout control across many channels with controlled operational changes.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Imagine Communications Versio
Versio’s automation orchestration links scheduled rundown intent to device execution with continuity-aware transitions.
Built for fits when cable TV groups need governed, multi-channel playout automation coordinated with existing media workflows..
Amagi Cloudport
Editor pickCloudport’s automation control for run execution keeps channel schedules and operational changes synchronized during playout.
Built for fits when broadcasters need repeatable cloud playout automation across many channels with controlled operational changes..
Grass Valley Karrera
Editor pickAutomated continuity control that coordinates scheduled events, switch points, and channel state transitions for playout continuity.
Built for fits when cable operators need scheduled continuity with strict switching and redundancy across many channels..
Related reading
Comparison Table
Cable TV playout automation software runs channel playout schedules, ingest-to-automation workflows, and channel-level control through configuration and APIs that match broadcast operational constraints. This ranked list targets operators, analysts, and technical evaluators who need verifiable comparisons across automation control depth, extensibility, and integration patterns without a custom dev stack, using a consistent scorecard across deployments.
Imagine Communications Versio
enterpriseSoftware-based playout and channel origination platform for linear television.
Versio’s automation orchestration links scheduled rundown intent to device execution with continuity-aware transitions.
Versio targets stations that run multiple channels with different rundown behaviors, where automation must coordinate ingest, playlist automation, and playout control across redundant server setups. It is used to reduce manual intervention by mapping scheduled items to device actions and by enforcing consistent continuity behaviors during rundown transitions. The tool’s governance shows up in its control separation between scheduling intent and execution, which supports safer operational changes.
A tradeoff is that deeper integration often requires more upfront engineering of media workflows and device mapping than UI-only automation tools. Versio fits best when a network already has defined ingest profiles, continuity rules, and device control expectations and needs repeatable operation across many channels. It is less suitable for teams that need quick, standalone automation without aligning media chain parameters and operational roles.
- +End-to-end orchestration across scheduling, ingest workflows, and playout execution
- +Automation rules can drive consistent continuity behavior during rundown changes
- +Operational separation supports safer handoffs from planning to execution
- +Monitoring and event outputs fit day-to-day broadcast operations
- –Requires detailed device and workflow mapping for each channel and facility
- –Workflow depth can make first deployment slower than basic playout automation
- –Complexity rises with multi-server redundancy and heterogeneous media paths
- –API-driven integrations can require engineering for custom edge cases
Headend operations teams
Automate live-to-air continuity across channels
Fewer manual interventions
Traffic and scheduling teams
Execute traffic changes with governed control
Lower change-related incidents
Show 2 more scenarios
Broadcast engineering teams
Standardize redundant playout operations
More repeatable operations
Coordinate playlist automation and execution across redundant playout servers with consistent behavior.
Media operations teams
Manage ingest workflows into playout
Faster asset turnaround
Use ingest and asset processing mappings so new media becomes playout-ready within the automation chain.
Best for: Fits when cable TV groups need governed, multi-channel playout automation coordinated with existing media workflows.
More related reading
Amagi Cloudport
API-firstCloud-based channel playout and origination for linear TV.
Cloudport’s automation control for run execution keeps channel schedules and operational changes synchronized during playout.
Amagi Cloudport is geared toward playlist scheduling and automated continuity, with channel-level configuration for playout runs and operational handoffs. It supports media ingest preparation for downstream playout and can coordinate run execution across outputs used for SDI or IP multicast distribution. Admin control is oriented around managing channel resources and run configurations rather than building bespoke automation flows for every station workflow.
A practical tradeoff is that deep customization of every edge case may require using Cloudport’s automation hooks rather than editing a monolithic rules engine inside the UI. Cloudport fits when multiple channels need repeatable operations with consistent governance of changes, such as daily rundown updates and standardized ingest workflows for time-delay operations.
- +Operational workflows support repeatable channel playout runs at scale
- +Automation control supports event-driven run execution and schedule changes
- +Channel configuration is centralized for consistent operational governance
- +Ingest and playout coordination reduces manual run preparation steps
- –Complex edge-case logic may need automation hooks beyond UI configuration
- –Workflow tuning can be time-consuming when playlists vary widely
- –Operational debugging across multiple outputs requires disciplined run trace review
Operations teams
Daily rundown playback with minimal touch
Fewer operator interventions
Traffic and planning teams
Faster schedule updates across channels
Shorter update turnaround
Show 2 more scenarios
Engineering teams
Extending control for custom events
More workflow flexibility
Teams connect operational triggers to Cloudport automation flows for custom run handling.
NOC and broadcast ops
Time-delay operations with controlled governance
Stable delayed output
Teams manage standardized channel runs to maintain predictable time-delay playout behavior.
Best for: Fits when broadcasters need repeatable cloud playout automation across many channels with controlled operational changes.
Grass Valley Karrera
enterpriseProduction switcher and automation control system for live broadcast.
Automated continuity control that coordinates scheduled events, switch points, and channel state transitions for playout continuity.
Grass Valley Karrera supports end-to-end channel automation that maps scheduled events to playout endpoints and operational states like live-to-air and delayed output. The workflow emphasis shows up in how it coordinates switching, continuity, and event sequencing rather than treating playout as a single step. Redundant playout server designs fit common broadcast practice for minimizing downtime during failover scenarios.
A tradeoff is that Karrera automation tends to favor broadcast engineering-led setup for channel and routing logic, which adds upfront governance work. It fits best when operators need automated continuity and strict event handling across multiple channels, not just ad hoc playback control for a small number of streams.
- +Automation-first control of playout timelines across multiple channel states
- +Redundancy-oriented workflows for minimizing downtime during server failover
- +Frame-accurate switching support for schedule-driven live-to-air operations
- +Operational sequencing supports automated continuity across event boundaries
- –Broadcast engineering setup overhead for routing and channel logic
- –Advanced integrations require careful alignment of external traffic inputs
- –Complex workflows can increase change-management load during channel updates
- –Testing for delay and switch logic needs disciplined commissioning
Headend engineering teams
Time-delay playout with strict switching
Fewer on-air continuity errors
Broadcast operations managers
Automated continuity across multi-channel schedules
Lower operator workload
Show 1 more scenario
Reliability-focused operations
Redundant playout server failover planning
Reduced service interruption
Automation workflows support operational readiness for server switchover events.
Best for: Fits when cable operators need scheduled continuity with strict switching and redundancy across many channels.
More related reading
Pebble Beach Systems Marina
enterpriseChannel playout and automation software for television operations.
As-run logging tied to executed playlist actions provides traceability during continuity troubleshooting.
Pebble Beach Systems Marina is a cable TV automation playout solution built around newsroom-style playlist control and on-air event execution. It supports automated continuity workflows for scheduled playout, with operational visibility into what ran and when.
Marina focuses on integrating playout instructions with operational control so traffic-driven changes can be enacted without manual intervention. It is a strong fit when the primary requirement is reliable channel execution under operator governance rather than ad hoc scripting.
- +Operator-driven playlist control supports consistent live-to-air outcomes
- +As-run event capture improves operational accountability during channel incidents
- +Integration-oriented workflows reduce manual steps during schedule changes
- +Automation covers day-to-day continuity operations with fewer operator actions
- –API surface and extensibility depth can be limiting without engineering involvement
- –Configuration of multiple channel variants can increase change-management overhead
- –Media ingest and format breadth may require external workflows for edge formats
- –Governance patterns for multi-operator environments may need process hardening
Best for: Fits when operations teams need controlled playlist automation for multi-channel playout with strong as-run accountability.
Cinegy Air
SMBSoftware-based playout automation for IP and traditional broadcast.
Redundant playout server deployment supports continuous operation during failover events without manual rundown restart.
Cinegy Air automates playout scheduling and channel operations for linear broadcast workflows with tight control over rundown-to-output behavior. It centers on automated continuity with media ingest and playout orchestration, plus tools for time-delay and live-to-air event handling.
The product integrates with broadcast-centric systems and supports channel workflows that require exact timing and repeatable automation runs. Administration features focus on operational governance for playout control tasks across playout objects and user roles.
- +Automation controls map cleanly to rundown execution for repeatable playout runs
- +Strong support for time-delay workflows alongside live-to-air handling
- +Operational governance supports role-based control of playout actions
- +Integration focus fits channel operations that rely on broadcast asset workflows
- –Complex channel configuration can take longer than spreadsheet-driven traffic approaches
- –Automation changes require careful rundown testing to avoid unintended event sequencing
- –EAS and SCTE-35 handling coverage can depend on specific system integrations
- –Watch folder style ingest automation is usable but needs disciplined ingest profiling
Best for: Fits when broadcast teams need automated continuity with strict rundown-to-output execution.
BroadStream XPlorer
SMBAutomation and playout control software for television channels.
As-run logging ties actual playout outcomes back to scheduled automation steps for operational reconciliation.
BroadStream XPlorer targets cable TV playout workflows where automated continuity, scheduled rundown generation, and media ingest coordination must run under tight operational change control. It supports playlist scheduling into playout engines, with mechanisms for channel branding and automation around live-to-air and time-delay operations.
The system also emphasizes operational telemetry through as-run logging and operational event capture, which helps reconcile what actually played against planned traffic. Administrators get configuration controls suited to running redundant playout operations and managing cross-channel workflows.
- +Automated continuity workflows reduce manual rundown edits during traffic cycles
- +As-run logging supports post-play reconciliation against planned playlists
- +Channel branding controls fit multi-channel operations with shared media pipelines
- +Redundant playout operations can be managed within the same automation workflow
- –Operational outcomes depend on disciplined ingest profile and watch-folder setup
- –Advanced integration requires stronger engineering effort than simpler lineup tools
- –SCTE-35 and EAS workflows are not as prominent in everyday tooling
- –Throughput tuning for high channel counts needs careful capacity planning
Best for: Fits when cable operators need coordinated playlist automation with operational logging and branded playout workflows under change control.
More related reading
NVerzion Automation
enterpriseBroadcast automation and playout control systems for television.
Rule-driven playout orchestration that ties playlist actions to continuity steps within the same operational workflow.
NVerzion Automation focuses on end-to-end playout workflow automation, with operator-facing control that connects ingest preparation to channel execution. Automation rules drive playlist handling and continuity tasks, so live-to-air and time-delay paths can follow the same runbook style.
Media handling supports common broadcast file workflows for SDI playout and multicast distribution targets. For teams that need repeatable automation with measurable operational controls, it fits operations-led integration work rather than ad hoc scripting.
- +Operator workflows map cleanly to channel playout execution steps
- +Automation rules reduce manual playlist and continuity handling
- +Integration surface supports multi-output deployments like multicast
- +Config-driven runs help standardize time-delay and live-to-air operations
- –Advanced governance and change control require disciplined release practices
- –Some traffic-style integration scenarios depend on specific connector support
- –Complex ingest-to-playout chains take effort to model end to end
- –Preview and troubleshooting tooling can feel workflow-dependent
Best for: Fits when operations teams need rule-driven playlist automation across live-to-air and time-delay channels.
Vizrt Viz One
enterpriseMedia asset management and playout automation for broadcast graphics.
Rundown-driven channel branding and graphics actions that execute alongside playlist control during playout.
Vizrt Viz One targets cable TV operations that need automated playout orchestration across multiple channels, with a focus on newsroom-friendly workflows and media chain control. The system supports playlist scheduling and automated continuity so operators can drive live-to-air, time-delay playout, and scheduled takeovers from managed configurations.
Vizrt Viz One also fits environments that need consistent channel branding and graphics automation during SDI playout and IP multicast output. Integration typically centers on connecting traffic and media ingest workflows into playout-ready rundowns, rather than building everything from scratch in the UI.
- +Playlist-driven automation for consistent scheduled and conditional switching
- +Channel branding and graphics automation tied to rundown control
- +Operational workflows geared toward media teams and playout engineers
- +Supports mixed distribution paths including IP multicast output
- –Template-heavy configuration can slow rollout across many channels
- –Operational governance requires disciplined rundown versioning practices
- –Deep traffic and billing integration may require system-specific connectors
- –Automation troubleshooting needs strong knowledge of the rundown chain
Best for: Fits when mid-size operators need controlled playlist automation across multiple channels with graphics orchestration.
More related reading
Dalet Galaxy
enterpriseUnified media workflow platform with playout and orchestration.
Workflow automation that links media asset management operations directly into playlist-driven playout execution.
Dalet Galaxy runs automated channel playout workflows that combine content ingest, playlist-driven scheduling, and live-to-air operational control. It integrates media asset management with automation steps for routing, branding insertion, and continuity handling across multiple channels.
The automation surface supports configurable workflows and extensibility points for operational triggers and downstream system handoffs. In cable TV environments, it is positioned for governance around operations, repeatable execution, and scale across redundant playout configurations.
- +Configurable playlist-driven playout workflows for multi-channel operations
- +Tight coupling between media asset management and automation steps
- +Operational controls support redundancy patterns for continuity
- +Extensibility points support integration with surrounding playout systems
- –Setup requires disciplined workflow modeling for consistent outcomes
- –Advanced template changes can take longer than expected for small edits
- –Some specialized delivery paths depend on specific configuration packages
- –Debugging workflow failures needs strong monitoring and logging practices
Best for: Fits when cable operators need governed automation across multiple channels and media workflows.
Ross Video OverDrive
enterpriseProduction control automation for live and news broadcast environments.
Continuity control with operational guardrails that keep traffic outcomes aligned with playout execution and exception handling.
Ross Video OverDrive is cable TV playout automation for facilities that need tightly governed traffic workflows tied to on-air execution. OverDrive supports channel operations that combine scheduled playlists, live-to-air control, and device orchestration for repeatable playout outcomes.
The solution fits environments that also require operational visibility via continuity controls and as-run style reporting to support troubleshooting and engineering oversight. OverDrive is typically evaluated alongside other MCR automation suites because it centers on playout control and automation behavior rather than media browsing alone.
- +Strong orchestration model for automated continuity and live-to-air control points
- +Clear operational separation between traffic instructions and playout execution logic
- +Works well in multi-channel environments that need consistent operational guardrails
- +Reporting designed to support engineering review of what ran versus what was planned
- –Depth of workflow configuration can slow rollout for teams without automation standards
- –API surface depends on integration approach and may require system-level engineering
- –Advanced edge cases can demand careful channel template management
- –Operator training can be time-consuming for traffic-to-playout exception handling
Best for: Fits when cable operators need disciplined, automated continuity across multiple channels with repeatable traffic behavior.
Conclusion
After evaluating 10 technology digital media, Imagine Communications Versio 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.
How to Choose the Right cable tv automation playout software
Cable TV automation playout software coordinates scheduled rundown intent with device-level execution so continuity stays consistent across live-to-air and time-delay channels. This buyer’s guide covers Imagine Communications Versio, Amagi Cloudport, Grass Valley Karrera, and the other six tools in the ranked field.
The selection criteria emphasize integration depth into playout workflows and operational systems, an automation control surface that can react to schedule changes, and an extensibility path that supports orchestration and API-driven automation. Each tool’s strengths are tied to its operational model for run execution, redundancy handling, and traceability through executed playlist actions.
Cable TV automation playout software for governed playlist automation, continuity control, and run execution
Cable TV automation playout software turns playlist and rundown instructions into frame-timed switching decisions, executes channel state transitions, and keeps traffic-driven outcomes aligned with playout control. Tools like Imagine Communications Versio focus on orchestration that links scheduled rundown intent to device execution while enforcing continuity-aware transitions.
Amagi Cloudport targets repeatable cloud playout automation by keeping channel schedules and operational changes synchronized through automation control for run execution. Grass Valley Karrera emphasizes automated continuity control that coordinates scheduled events, switch points, and channel state transitions across redundant playout workflows.
Integration and control surfaces for cable TV playout automation
Cable TV automation playout software must translate playlist and rundown intent into device-level execution so continuity remains consistent when schedules change mid-cycle. The feature set should be judged by orchestration control depth, repeatability for multi-channel operations, and traceability that ties executed outcomes back to scheduled steps.
Orchestration that links run intent to continuity-aware device execution
Imagine Communications Versio orchestrates scheduled rundown intent to device execution with continuity-aware transitions. Grass Valley Karrera coordinates scheduled events, switch points, and channel state transitions for playout continuity.
Automation run execution that keeps schedules and operational changes synchronized
Amagi Cloudport uses automation control for run execution that keeps channel schedules and operational changes synchronized during playout. Ross Video OverDrive maintains guardrails so traffic outcomes stay aligned with playout execution and exception handling.
As-run logging tied to executed playlist actions for reconciliation
Pebble Beach Systems Marina provides as-run logging tied to executed playlist actions to support continuity troubleshooting. BroadStream XPlorer ties actual playout outcomes back to scheduled automation steps for operational reconciliation.
Redundancy handling and continuity control during failover events
Cinegy Air supports redundant playout server deployment that keeps operation running during failover events without requiring a manual rundown restart. Grass Valley Karrera emphasizes redundancy-oriented workflows for minimizing downtime during server failover.
Extensibility and automation control surface beyond UI configuration
Imagine Communications Versio supports automation rules that can drive consistent continuity behavior during rundown changes and requires detailed workflow mapping for each channel. Amagi Cloudport supports event-driven run execution and schedule changes but can require automation hooks beyond UI configuration for complex edge cases.
Choose based on orchestration philosophy, operational governance, and troubleshooting needs
Selection should start with where orchestration logic lives and how schedule changes propagate into device actions. Some platforms emphasize orchestration depth with continuity-aware transitions, while others emphasize operational logging and reconciliation or redundancy-first failover behavior.
Map run intent to device execution and continuity transitions
If continuity-aware transitions must update correctly when a rundown changes, prioritize Imagine Communications Versio orchestration across scheduling, ingest workflows, and playout execution. If the requirement is strict switching and channel state transitions with redundancy, use Grass Valley Karrera as the primary continuity control reference.
Pick the operating model for schedule changes during playout
If channel schedules and operational changes must stay synchronized through event-driven automation control, evaluate Amagi Cloudport automation control for run execution. If traffic instructions must remain clearly separated from playout execution logic with operational guardrails, evaluate Ross Video OverDrive.
Decide how issues get diagnosed after the fact
If post-play troubleshooting needs executed truth tied to planned actions, select Pebble Beach Systems Marina because as-run logging captures traceability for continuity troubleshooting. If reconciliation requires mapping operational outcomes to scheduled automation steps, select BroadStream XPlorer to support post-play comparison.
Validate failover behavior against real rundown testing constraints
If redundant playout must keep running during failover without a manual rundown restart, test Cinegy Air in a scenario that forces failover while a rundown is active. If redundancy workflows must coordinate channel states across multiple states during server failover, validate Grass Valley Karrera with routing and channel logic.
Control the change-management load across many channels
If multi-channel variants increase governance and change-management overhead, plan for deployment mapping work when selecting Imagine Communications Versio. If workflows and playlists vary widely, plan for time-consuming workflow tuning when selecting Amagi Cloudport.
Who benefits from governed automation playout with continuity control
Cable TV operators with multiple channels and time-delay workflows need automation that can turn schedule changes into safe device actions with continuity awareness. Teams also benefit when the system captures executed truth so incidents can be reconciled to planned playlist actions.
Cable TV operators managing governed multi-channel playout
Imagine Communications Versio fits when multi-channel automation must be coordinated with existing media workflows and continuity behavior must stay consistent during rundown changes.
Broadcasters scaling repeatable cloud playout runs
Amagi Cloudport fits when operational workflows must support repeatable channel playout runs across many channels with automation control for event-driven run execution.
Broadcast engineering teams focused on redundancy and strict switching
Grass Valley Karrera fits when scheduled continuity must coordinate switch points, channel state transitions, and redundancy workflows for minimizing downtime during server failover.
Operations teams running continuity incidents and reconciliation workflows
Pebble Beach Systems Marina and BroadStream XPlorer support operational accountability by capturing as-run evidence tied to executed playlist actions or scheduled automation steps.
Teams building automated live-to-air and time-delay workflows with rules
NVerzion Automation fits when rule-driven playlist orchestration ties playlist actions to continuity steps within the same operational workflow for live-to-air and time-delay channels.
Common pitfalls in cable TV automation playout deployments
A frequent failure mode is assuming playlist automation is plug-and-play when continuity control actually depends on channel logic mapping and workflow modeling discipline. Another failure mode is deploying automation without an operational logging path that ties executed outcomes to the scheduled plan.
Treating continuity behavior as an afterthought to orchestration
Select based on continuity-aware transitions and validate switching behavior with schedule edits for Imagine Communications Versio and Grass Valley Karrera.
Relying on UI changes without validating automation hooks for edge-case run execution
Amagi Cloudport can require automation hooks beyond UI configuration for complex edge-case logic, so test those scenarios before rollout.
Skipping as-run logging validation for incident reconciliation
Deployments that lack executed evidence tied to planned actions make troubleshooting slow, so verify as-run logging behavior in Pebble Beach Systems Marina or BroadStream XPlorer.
Underestimating the change-management workload for multi-channel variants
Imagine Communications Versio requires detailed device and workflow mapping per channel and facility, so timebox workflow mapping and channel variant coverage during setup planning.
Assuming redundancy is automatic without failover testing tied to rundown execution
Cinegy Air and Grass Valley Karrera both address redundancy workflows, but setup overhead and routing alignment still require testing to prevent unintended event sequencing during rundown execution.
How We Selected and Ranked These Tools
We evaluated Imagine Communications Versio, Amagi Cloudport, Grass Valley Karrera, and seven other automation playout tools using feature coverage for orchestration and run execution at 40% weight. Ease and operational value each contributed 30% weight by reflecting how quickly teams can operate continuity workflows without excessive manual handling.
Imagine Communications Versio ranked highest because its orchestration links scheduled rundown intent to device execution with continuity-aware transitions and it includes end-to-end automation across scheduling, ingest workflows, and playout execution. The ranking also reflected how each tool’s strengths map to operational change handling, continuity control, as-run traceability, and redundancy behavior during server failover.
Frequently Asked Questions About cable tv automation playout software
How do EVS IPDirector, Imagine MCR Automation, and Grass Valley Karrera differ in orchestration from traffic schedule to device-ready playout?
Which tools provide event-driven interfaces for traffic and operational changes during rundown execution?
When should an operator choose Marina over a newsroom-agnostic playout controller?
What breaks if a cable operator lacks redundancy planning in the playout automation workflow?
Which product handles automated continuity with frame-accurate switch points during scheduled takeovers best?
How do administrators model user access and operational governance across playout control functions?
What integration approach matters most for teams that connect media ingest workflows to on-air execution?
Where does NVerzion Automation tend to fall short compared with suites that focus on more device orchestration detail?
How should operators validate as-run logging and operational telemetry before going live?
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
Technology Digital Media alternatives
See side-by-side comparisons of technology digital media tools and pick the right one for your stack.
Compare technology digital media 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.