GITNUXSOFTWARE ADVICE
Video Games And ConsolesTop 8 Best Rc Plane Simulator Software of 2026
Ranked roundup of top Rc Plane Simulator Software for flight practice, with technical notes and tradeoffs for RealFlight, RCFlightSim, and ArduPilot.
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.
RealFlight
Physics-based RC flight model with controller-driven aircraft handling and tuning.
Built for fits when flight training needs repeatable simulation setups without enterprise automation..
RCFlightSim
Editor pickScenario projects combine aircraft setup and environment parameters into versionable run definitions.
Built for fits when teams need repeatable RC flight scenarios with automation for training and tests..
ArduPilot
Editor pickMAVLink-driven command and telemetry interface with parameter provisioning for deterministic runs.
Built for fits when teams need MAVLink-based automation and mission execution parity..
Related reading
Comparison Table
The comparison table maps Rc Plane Simulator software across integration depth, focusing on how each tool connects to flight stacks, simulators, and toolchains through configuration surfaces and API options. It also compares the data model and schema design for telemetry, mission state, and parameters, plus automation and API surface areas for repeatable tests and provisioning. Admin and governance controls are assessed through RBAC scopes and audit log coverage to clarify how teams manage access and change history.
RealFlight
RC simulatorProvides RC flight simulation software that supports realistic plane physics, control tuning, and model setup for RC aircraft workflows.
Physics-based RC flight model with controller-driven aircraft handling and tuning.
RealFlight provides a physics-driven RC flight experience using a controller connection for throttle, pitch, roll, and yaw style inputs. The content model centers on aircraft and flight environments, with configuration focused on simulation parameters and control bindings rather than external data schemas. Integration depth is strongest at the device input layer and at asset consumption for models and scenarios. Extensibility is oriented toward adding or selecting simulation content, not building automated orchestration around a formal API surface.
A clear tradeoff is limited administration and data governance, since RealFlight workflows are structured around local simulation sessions. RealFlight fits teams that need repeatable training flights and repeatable aircraft setup, but not teams that require RBAC, audit logs, or sandboxed automation against flight telemetry. A typical usage situation is training pilots or validating handling characteristics by running the same aircraft and environment configuration across sessions. Another fit case is hobbyist or instructor-led workshops that manage control presets and model selections without backend automation.
- +Controller input mapping supports consistent control feel
- +Physics-based flight handling for aircraft training and practice
- +Large aircraft and terrain library for varied simulation sessions
- –Limited documented API and automation surface for integrations
- –Minimal admin governance controls like RBAC and audit logs
- –Asset workflow focuses on simulation selection, not telemetry data models
Flight instructors
Run repeatable training flights
Faster coaching feedback loops
RC pilots
Practice maneuvers on the same aircraft
More consistent in-air handling
Show 2 more scenarios
Training operations teams
Session-based curriculum planning
Reduced variance between sessions
Teams configure control bindings and scenarios for structured practice sessions without backend orchestration.
Modellers and demo hosts
Show aircraft behavior in venues
Clearer model comparisons
Hosts select aircraft assets and environments to demonstrate handling differences to groups.
Best for: Fits when flight training needs repeatable simulation setups without enterprise automation.
RCFlightSim
RC simulatorProvides an RC flight simulation app focused on RC aircraft dynamics and controller-driven flight playback for RC plane training.
Scenario projects combine aircraft setup and environment parameters into versionable run definitions.
RCFlightSim fits teams that need controlled simulator throughput for operator training and verification runs. The data model centers on scenario definitions, aircraft configuration, and environment parameters that can be reloaded for repeatability. Scenario runs support automation via scripting hooks and configurable settings, which helps standardize experiments across sessions.
A key tradeoff is that deeper automation requires disciplined scenario schema design to keep configuration drift out of test results. RCFlightSim works best when training curricula or test plans already exist and need conversion into a versioned set of scenarios with repeatable aircraft parameters.
- +Scenario configuration supports repeatable runs for training verification
- +Scripting hooks enable automation around inputs and mission playback
- +Project data model keeps aircraft and environment settings organized
- +Multi-user workflow supports coordinated simulator sessions
- –Automation depth depends on strict scenario schema discipline
- –Complex model tuning can slow onboarding for new scenario authors
- –Governance controls are limited without external RBAC and audit tooling
Flight training instructors
Run standardized lesson scenarios
Consistent skill assessment
Simulation test engineers
Regression test flight handling tweaks
Controlled regression signals
Show 2 more scenarios
RC hardware lab teams
Validate transmitter input mappings
Fewer setup mismatches
Use automation hooks to exercise input profiles and confirm control behavior across sessions.
Aviation clubs
Coordinate multi-user practice sessions
Aligned practice objectives
Distribute scenario projects so multiple pilots train under the same environment and aircraft settings.
Best for: Fits when teams need repeatable RC flight scenarios with automation for training and tests.
ArduPilot
autopilot toolingProvides open autopilot firmware plus configuration and tuning utilities that integrate with simulation backends via standardized parameter and telemetry schemas.
MAVLink-driven command and telemetry interface with parameter provisioning for deterministic runs.
ArduPilot maps a simulator aircraft to the same sensor, navigation, and control interfaces used on real hardware, which improves transfer from bench testing to field tuning. The data model centers on vehicle parameters and mission data, with a deterministic naming and type system that external tools can set before a run. MAVLink message streams carry telemetry, status, and command acknowledgements, so automation can validate state transitions. Extensibility includes onboard scripting and external companion control through the same message contracts.
A tradeoff appears in governance and operations, because ArduPilot expects careful coordination of parameter state across simulator restarts. Automation workflows must manage configuration drift, since parameters, frames, and mission items can silently change behavior if not versioned. It fits teams that need repeatable test runs with programmatic telemetry checks and scenario-based mission uploads rather than only visual aircraft rendering.
- +MAVLink command and telemetry model enables test automation and state validation
- +Parameter-driven configuration supports repeatable flight behavior tuning
- +Onboard scripting and companion integration support automation beyond GUI actions
- +Mission-aware execution mirrors autopilot navigation and control behaviors
- –Parameter drift risk increases when simulator resets without schema versioning
- –Admin controls like RBAC and audit logs are not built into the core stack
Controls engineers
Tune autopilot gains against simulated flights
Repeatable tuning across scenarios
Simulation QA teams
Automate mission regressions for RC planes
Fewer navigation regressions
Show 2 more scenarios
Aerospace developers
Integrate custom companion controllers
Higher test harness throughput
Use the MAVLink schema to command waypoints, log telemetry, and orchestrate test harnesses.
Ops and labs
Standardize parameter provisioning across rigs
Reduced configuration drift
Apply named parameters before runs and document configuration snapshots per scenario.
Best for: Fits when teams need MAVLink-based automation and mission execution parity.
INAV Configurator
configuration toolingINAV Configurator provides a configuration UI and tooling for INAV-capable firmware setups that can be used with simulator backends via exported parameters.
Direct device configuration via INAV parameter read and write over the configurator connection.
In the RC plane simulator toolset, INAV Configurator centers on configuration-first workflows for INAV-driven craft. It provides a structured parameter and sensor configuration experience aligned to INAV firmware concepts, which improves portability of settings between simulators and target builds.
Configuration management supports repeatable setups through import and export of firmware parameters. Integration depth is strongest through device communication and firmware-flavored schemas rather than through third-party automation frameworks.
- +Firmware-aligned data model maps INAV parameters to configuration screens
- +Parameter import and export supports repeatable setup transfer between sessions
- +Device connection enables direct reading and writing of INAV configuration
- –Automation and API surface for external provisioning is limited
- –No documented RBAC or audit log controls for shared team use
- –Schema extensibility for custom fields relies on INAV parameter structures
Best for: Fits when small teams need controlled INAV parameter configuration without building custom tooling.
Betaflight Configurator
configuration toolingBetaflight Configurator offers a desktop configuration workflow and parameter export that supports automation via scripting on the device settings data model.
Profile import and export for repeatable configuration snapshots.
Betaflight Configurator connects to Betaflight firmware over a serial link to read and write flight-controller configuration. It exposes a structured configuration model with feature toggles, rates, and control parameters mapped to a Betaflight schema.
Configuration changes can be exported and imported as text profiles, enabling repeatable simulator setup and consistent parameter sets. Automation and API access are limited to manual configuration workflows rather than a documented programmatic interface.
- +Direct serial integration for reading and writing controller parameters
- +Text-based profile export enables reproducible configuration sets
- +Clear separation of configuration groups like rates, filtering, and modes
- +Works offline once profiles and target parameters are defined
- –No documented REST API for external automation or provisioning
- –No RBAC or audit log for multi-user configuration governance
- –Limited extensibility beyond Betaflight-supported configuration fields
- –Batch updates require scripting outside the configurator workflow
Best for: Fits when pilots and hobby teams need repeatable Betaflight config profiles for RC plane simulation.
ArduPilot Mission Planner
firmware automationArduPilot firmware tooling exposes parameter and mission data structures that can be scripted for repeatable integration tests with RC simulation environments.
Parameter and mission file interchange that preserves ArduPilot frame, mode, and behavior semantics.
ArduPilot Mission Planner targets RC plane simulation workflows by pairing Mission Planner with ArduPilot firmware and a rich parameter and mission data model. It supports hardware-in-the-loop style planning using telemetry connections, waypoint and survey mission generation, and automated checklist steps for repeatable test runs.
The tool’s integration depth comes from direct firmware parameter handling, log analysis hooks, and scripted mission upload flows that map cleanly to ArduPilot concepts like frames, modes, and behaviors. Automation and extensibility center on repeatable configuration provisioning through parameter sets, mission files, and data extracted from recorded telemetry logs.
- +Tight integration with ArduPilot parameters, modes, and mission data model
- +Mission planning supports repeatable waypoint and survey generation workflows
- +Telemetry and log handling enable verification loops for simulated flights
- +Scriptable upload and config workflows via mission and parameter artifacts
- –Simulation fidelity depends on the external simulator and connection setup
- –Automation surface is mostly file based rather than a full remote API
- –Complex parameter sets increase governance and change control burden
- –UI-centric workflows can limit high-throughput batch experimentation
Best for: Fits when teams need controlled ArduPilot mission provisioning and log-based validation without custom backend work.
TRAX Flight Controller Configurator
RC configurationTRAX flight-related tooling focuses on repeatable configuration data for RC flight systems and can be used to standardize simulator test setups.
Staged configuration workflow aligned to Traxxas flight controller parameter sets.
TRAX Flight Controller Configurator targets Traxxas flight controller setup and uses a UI-first configuration flow tied to the controller’s expected parameters. It centers on a concrete configuration data model that maps flight controller settings into a staged configuration you can apply to a device.
Integration depth is mainly through the on-device configuration path rather than broad third-party schema ingestion. Automation and extensibility appear constrained to the configurator workflow, with no clearly documented external API surface for provisioning or RBAC.
- +Direct mapping from flight controller parameters to configurable fields
- +Device-oriented workflow reduces mismatch risk during controller setup
- +Configuration staging supports controlled application to hardware
- –Limited evidence of external API for automation and provisioning
- –No documented RBAC or admin governance controls for teams
- –Extensibility appears tied to the built-in configuration schema only
Best for: Fits when RC pilots need repeatable flight controller configuration without external tooling.
EdgeTX Companion
radio provisioningEdgeTX Companion supports radio configuration export and import flows that can be integrated into automated RC test provisioning pipelines.
Model configuration schema and provisioning workflow tailored to EdgeTX aircraft setups.
EdgeTX Companion focuses on simulator-centric integration for RC plane workflows tied to EdgeTX ecosystems. It pairs a structured data model for aircraft setup with configuration tooling used for model and control mapping.
Automation coverage emphasizes repeatable configuration, consistent schema handling, and extensibility for simulator use cases. The experience is anchored in configuration discipline rather than UI-only interaction.
- +Tight EdgeTX-focused configuration workflows for repeatable RC plane simulator setups
- +Consistent model data structure supports controlled configuration changes
- +Extensibility via project-driven additions to cover simulator-specific needs
- –Automation and API surface are limited compared with general-purpose integration tools
- –RBAC and audit log controls are not oriented toward enterprise governance
- –Throughput for bulk model edits depends on manual configuration patterns
Best for: Fits when hobbyist teams need EdgeTX-aligned simulator provisioning with controlled configuration changes.
How to Choose the Right Rc Plane Simulator Software
This buyer’s guide covers RC plane simulator software options and configuration tooling, including RealFlight, RCFlightSim, ArduPilot, INAV Configurator, Betaflight Configurator, ArduPilot Mission Planner, TRAX Flight Controller Configurator, and EdgeTX Companion.
The focus stays on integration depth, the data model behind repeatable simulator runs, automation and API surface, and admin and governance controls like RBAC and audit logging.
RealFlight emphasizes physics-based control feel and repeatable setup workflows, while ArduPilot emphasizes MAVLink messaging and parameter-driven automation paths.
RC plane simulator software that turns controller inputs into repeatable flight tests
RC plane simulator software provides a physics or flight-stack environment where controller inputs and aircraft parameters generate repeatable flight outcomes inside defined venues and scenarios. Teams use it to validate tuning changes, training protocols, mission logic, and controller mapping without burning hardware time.
Some tools focus on end-to-end simulation sessions like RealFlight and RCFlightSim, where scenario definitions and asset libraries drive consistent playback. Other tools act as configuration and integration layers like ArduPilot, INAV Configurator, and Betaflight Configurator, where simulator runs depend on exporting and provisioning firmware parameter schemas and mission artifacts.
Evaluation criteria for integration depth, data model control, and automation readiness
Integration depth determines whether simulator setup stays manual or becomes reproducible via parameters, telemetry streams, and scriptable provisioning artifacts. Tools built around explicit schemas like ArduPilot and MAVLink support deterministic test automation when state validation is required.
Data model design controls whether scenarios and configurations can be versioned, shared, and applied consistently. Admin and governance controls matter when multiple authors create scenarios, tune parameters, and need traceability beyond UI changes.
MAVLink command and telemetry model for automation
ArduPilot provides MAVLink-driven command and telemetry interfaces that support state validation in automated test runs. This lowers friction for integration-based workflows compared with tools that mainly focus on simulation selection and controller input mapping, like RealFlight.
Parameter-driven configuration schema for repeatable behavior
ArduPilot and ArduPilot Mission Planner anchor runs to parameter and mission semantics like frames, modes, and behaviors. INAV Configurator also maps INAV parameters into a firmware-aligned configuration model that supports import and export to transfer setups between sessions.
Scenario projects as versionable run definitions
RCFlightSim builds scenario projects that combine aircraft setup and environment parameters into versionable run definitions. This supports repeatable training and test verification with less reliance on manual re-entry of setup details.
Controller-to-physics tuning loop for consistent control feel
RealFlight uses a physics-based RC flight model driven by controller input mapping and aircraft handling tuning. This is a strong fit when the main goal is consistent training muscle memory and control response rather than enterprise governance or telemetry-centric automation.
Config import and export artifacts for controlled snapshots
Betaflight Configurator provides text-based profile export and import for reproducible configuration sets. EdgeTX Companion similarly focuses on a structured aircraft setup model for repeatable provisioning patterns in EdgeTX workflows.
Admin governance signals like RBAC and audit logs
Most reviewed tools lack built-in RBAC and audit log controls for multi-user governance. ArduPilot notes missing RBAC and audit logging in the core stack, and Betaflight Configurator also lacks RBAC and audit logs, so governance may require external controls around configuration artifacts.
Extensibility via scripting hooks and automation surface
RCFlightSim includes scripting hooks for automation around inputs and mission playback. ArduPilot supports onboard scripting and companion integration for automation beyond GUI actions, while INAV Configurator and TRAX Flight Controller Configurator mainly expose device configuration workflows without a broadly documented external API surface.
Decision framework for choosing the right tool based on automation and control depth
Start by identifying the integration target and the level of control needed over the data model. MAVLink automation pushes the decision toward ArduPilot and ArduPilot Mission Planner, while versionable scenario projects push the decision toward RCFlightSim.
Next, map governance requirements to each tool’s admin controls and automation surface. When RBAC and audit logs are needed, the reviewed configurators and simulators generally require external governance around exported profiles and parameter artifacts.
Choose the orchestration style: scenario projects or firmware stacks
Select RCFlightSim when teams need scenario projects that package aircraft setup and environment parameters into versionable run definitions. Choose ArduPilot when the run must reflect autopilot mission-aware execution and navigation logic via its parameter and MAVLink model.
Verify the automation surface matches the test workflow
If automation needs command and telemetry streams for state validation, use ArduPilot because MAVLink messaging provides an explicit data model for automated verification. If automation focuses on repeatable playback tied to scenario inputs, use RCFlightSim because it includes scripting hooks for mission playback.
Lock down configuration portability with schema-aligned exports
For firmware-aligned parameter portability, use INAV Configurator because it supports parameter import and export aligned to INAV firmware concepts. For Betaflight setups, use Betaflight Configurator because it exports structured configuration groups as text profiles that support consistent re-application.
Plan for governance when RBAC and audit logs are missing
Treat missing RBAC and audit logs as a design constraint in tools like RealFlight, ArduPilot, INAV Configurator, and Betaflight Configurator. Build governance around versioned scenario projects and configuration artifacts, then restrict who can update those artifacts outside the simulator environment.
Match simulation fidelity needs to controller tuning workflows
Select RealFlight when flight training depends on physics-based aircraft handling and controller input mapping for consistent control feel. Select tools with scenario or mission semantics like RCFlightSim or ArduPilot when the goal is repeatable training verification or mission logic parity.
Confirm extensibility expectations before committing to custom integration
For scripting-driven automation, prioritize RCFlightSim scripting hooks and ArduPilot companion or onboard scripting integrations. For device-oriented configuration workflows, rely on INAV Configurator, TRAX Flight Controller Configurator, and EdgeTX Companion where external API automation is constrained and extensibility centers on their built-in schemas.
Tool selection by team type and workflow outcome
Different tools suit different workflow outcomes, from physics-driven training consistency to mission-aware automation with telemetry validation. The best fit depends on whether the simulator run is managed as a scenario project or as an autopilot mission execution test.
Most tools support controlled configuration via exported artifacts, but governance features like RBAC and audit logging are limited across the set, so governance-heavy teams need an external change-control approach.
Flight training programs focused on consistent control feel
RealFlight fits because controller input mapping and physics-based flight handling support repeatable aircraft handling practice without requiring MAVLink-centric automation. It is also a better match than tools like Betaflight Configurator when training output matters more than mission file semantics.
Training and QA teams that run repeatable scenario tests
RCFlightSim fits because scenario projects combine aircraft setup and environment parameters into versionable run definitions. The included scripting hooks support automation around inputs and mission playback without requiring a full MAVLink integration.
Autopilot-centric teams that need mission parity and telemetry validation
ArduPilot and ArduPilot Mission Planner fit because MAVLink messaging and parameter-driven configuration enable deterministic runs and state validation. This segment benefits from mission-aware execution that mirrors autopilot navigation and control behaviors.
Teams focused on INAV or Betaflight parameter portability without building custom tooling
INAV Configurator fits when controlled INAV parameter configuration is needed with parameter import and export for repeatable setup transfer. Betaflight Configurator fits when repeatable Betaflight configuration snapshots are needed through text-based profile export and import.
Hobbyist and EdgeTX-aligned workflows that standardize radio and aircraft mapping
EdgeTX Companion fits when simulator provisioning must stay aligned with EdgeTX ecosystems using a structured aircraft setup model. TRAX Flight Controller Configurator fits pilots who want staged, controller-parameter-aligned configuration without relying on external automation APIs.
Pitfalls that derail repeatability, governance, and automation in RC plane simulator setups
Several tools reviewed here focus on configuration and simulation workflows that do not automatically translate into enterprise governance or programmatic provisioning. The most common failure mode is assuming every tool has the same automation and admin capabilities.
A second failure mode is mixing loose scenario discipline with tools that rely on schema discipline for automation reliability. That mistake shows up as manual rework when scenarios are not maintained as versionable definitions.
Assuming there is an enterprise-grade API and RBAC for every option
RealFlight, Betaflight Configurator, and TRAX Flight Controller Configurator lack documented external automation APIs and RBAC style governance in their core workflows. For automation and control depth, use ArduPilot when MAVLink and parameter provisioning need to be scriptable and state-validated.
Using scenario projects without enforcing schema discipline for repeatable runs
RCFlightSim automation depends on consistent scenario schema discipline, so scenario authors must keep aircraft and environment fields aligned across projects. Teams that cannot enforce that discipline should shift toward ArduPilot where parameter-driven configuration supports deterministic behavior tuning.
Relying on parameter values without controlling parameter drift across runs
ArduPilot highlights parameter drift risk when simulator resets happen without schema versioning, which causes behavior changes even when mission logic stays the same. Use parameter provisioning artifacts from ArduPilot Mission Planner and keep parameter sets versioned with each run definition.
Expecting governance features like audit logs inside configurators
INAV Configurator and Betaflight Configurator provide configuration flows and export or import, but they do not provide documented RBAC or audit log controls for shared team governance. Teams should manage change control around exported profiles and mission files outside the configurator interface.
Choosing controller tuning fidelity while needing mission-aware telemetry automation
RealFlight excels at physics-based aircraft handling and controller input mapping, but it is oriented toward simulation setup and assets rather than telemetry-centric integration. For mission-aware automation and state validation, prefer ArduPilot or ArduPilot Mission Planner.
How We Selected and Ranked These Tools
We evaluated RealFlight, RCFlightSim, ArduPilot, INAV Configurator, Betaflight Configurator, ArduPilot Mission Planner, TRAX Flight Controller Configurator, and EdgeTX Companion using a criteria-based scoring approach that rewards features for integration depth, automation and data model control, and operational clarity of configuration workflows. Each tool also received separate scores for ease of use and value, and the overall rating is a weighted average where features carry the most weight at 40 percent while ease of use and value each account for 30 percent. This scoring reflects editorial research using the provided feature descriptions, constraints, and standout capabilities rather than any hands-on lab testing or private benchmarks.
RealFlight separated itself through physics-based flight handling tied to controller input mapping and aircraft handling tuning, which directly lifted features and eased the path to consistent training sessions. That strength aligns with the highest practical outcome for its target workflow, which is repeatable simulation setup rather than telemetry-driven automation and governance.
Frequently Asked Questions About Rc Plane Simulator Software
Which RC plane simulator software supports MAVLink-based automation for mission execution?
What tool set is best for repeatable scenario runs with versionable run definitions?
How do configuration exports and imports differ between firmware configurators and simulator-focused tools?
Which simulator tool is more suitable for flight training when the goal is physics-based aircraft handling tuning?
What integration mechanism is typically used to connect configurators to devices or firmware parameters?
Which tool supports the cleanest log-based validation loop after a simulator run?
Which options support admin controls like RBAC, audit logs, or provisioning governance for teams?
What is the practical tradeoff between UI-first configurators and API-first automation for setting up a simulator environment?
How do EdgeTX-aligned workflows handle model and control mapping compared with other simulator-centric tools?
Conclusion
After evaluating 8 video games and consoles, RealFlight 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
Video Games And Consoles alternatives
See side-by-side comparisons of video games and consoles tools and pick the right one for your stack.
Compare video games and consoles 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.