GITNUXSOFTWARE ADVICE
Music And AudioTop 9 Best Produce Music Software of 2026
Top 10 Produce Music Software ranking with technical comparisons for beatmakers and producers, covering LoopCloud, Krotos Toolbox, Mixed In Key.
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.
LoopCloud
API-first provisioning of render jobs tied to versioned project sessions.
Built for fits when studios need API automation for session-to-render throughput..
Krotos Toolbox
Editor pickBatch automation driven by reusable presets bound to audio asset parameters.
Built for fits when audio teams need repeatable processing with controlled configuration and pipeline automation..
Mixed In Key
Editor pickKey and harmonic compatibility analysis that produces pairing-ready metadata for track workflow organization.
Built for fits when music teams need repeatable library tagging with export-driven automation..
Related reading
Comparison Table
This comparison table maps Produce Music Software tools across integration depth, including studio workflows, file formats, and how each product exposes APIs for automation. It also contrasts data model and schema design, plus the practical automation and API surface area for provisioning, extensibility, and configuration. Admin and governance controls are compared via RBAC coverage, audit log availability, and how each system supports team management under controlled throughput.
LoopCloud
loop libraryLoop and sample management app that organizes instruments and audio clips for fast retrieval during production sessions.
API-first provisioning of render jobs tied to versioned project sessions.
LoopCloud runs repeatable music workflows by linking session configuration to render and asset steps. The data model treats a project as a tracked unit that can be transformed into render jobs with defined inputs and outputs. Automation uses an API surface designed for provisioning work items, submitting jobs, and monitoring throughput rather than manual UI clicks.
A tradeoff appears in how tightly the workflow maps to LoopCloud’s supported DAW and render pipeline. Studios with highly custom toolchains may need to wrap their own glue around LoopCloud’s job and asset schema. LoopCloud fits best when multiple engineers need consistent session-to-render execution, plus integration points that can be scripted.
- +API-driven job submission with monitored job state
- +Project and render objects map to a clear workflow schema
- +Automation supports provisioning steps across studio environments
- +RBAC-oriented multi-user operations with controlled access
- –Workflow flexibility depends on LoopCloud-supported DAW integrations
- –Custom audio toolchains require additional orchestration glue
Music production ops teams
Automate session-to-render across multiple rooms
Higher throughput and fewer manual steps
Mix engineers
Standardize bounce and stem export workflows
More consistent mix deliverables
Show 2 more scenarios
Studio admins
Govern access across departments
Lower risk from uncontrolled access
They apply RBAC and enforce controlled provisioning for users and groups that can submit jobs.
Build and workflow developers
Integrate external CI for render orchestration
Automated delivery artifacts
They call the API to create jobs and move outputs into downstream publishing systems.
Best for: Fits when studios need API automation for session-to-render throughput.
More related reading
Krotos Toolbox
audio processingProduction plugins for sound processing with project-level repeatability and batch-friendly preset workflows.
Batch automation driven by reusable presets bound to audio asset parameters.
Krotos Toolbox fits teams that run frequent sound redesign passes and need repeatable configurations across multiple projects. The data model groups audio assets with parameter sets, which supports dependable batch execution instead of one-off edits. Admin and governance controls align best with controlled handoffs because configuration changes can be tracked through project-level structure and reusable presets.
A tradeoff appears in automation depth because API-based orchestration depends on the available integration surface rather than fully open schema access. Krotos Toolbox is a strong fit when teams want high-throughput processing of existing libraries and need consistent parameter provisioning for later review cycles.
- +Asset-centric data model links audio inputs to parameter sets
- +Batch processing supports repeatable sound design runs
- +Configuration and presets reduce drift across projects
- –Automation depends on integration surface availability for full external control
- –Schema extensibility can feel constrained for bespoke pipeline objects
- –Fine-grained RBAC and audit granularity may be limited for large orgs
Sound design teams
Reprocess libraries with consistent parameter sets
Less rework, faster iteration
Post-production supervisors
Standardize reviewable processing outputs
Safer approvals, fewer mismatches
Show 2 more scenarios
Studio pipeline engineers
Automate batch processing steps
Higher throughput across projects
Integration hooks and parameter schemas support automation of repeatable audio tasks.
Small audio departments
Manage sound assets without custom tools
More consistent deliveries
A structured asset and preset workflow reduces manual configuration errors during handoffs.
Best for: Fits when audio teams need repeatable processing with controlled configuration and pipeline automation.
Mixed In Key
music analysisHarmonic mixing analysis tool that computes musical key and tempo data to guide structured arrangement workflows.
Key and harmonic compatibility analysis that produces pairing-ready metadata for track workflow organization.
Mixed In Key turns audio analysis into a consistent data model for musical key and compatibility, which supports repeated batch tagging across large libraries. The core capabilities include key detection, chord and harmonic context generation for track pairing, and outputs that can be imported into downstream playlists and arrangement workflows. Integration breadth is mainly through file and library operations, with extensibility expressed through how metadata exports map to external tools rather than through a native RBAC-first admin layer.
A key tradeoff is limited API and webhook visibility for system-level orchestration, which can constrain governance and multi-system automation in teams with strict audit log requirements. Mixed In Key fits best when DJs or music teams need repeatable offline analysis at high throughput for library curation and project planning, not when they need real-time automation via an exposed API surface.
- +Harmonic metadata generation supports consistent track pairing and sequencing
- +Batch processing improves throughput for library-wide key tagging workflows
- +Exportable analysis outputs integrate via file and metadata mappings
- –Automation and API surface appear limited for external provisioning systems
- –Admin and governance controls like RBAC and audit logs are not the focus
- –Workflow integration relies more on exports than on direct system hooks
DJ operations teams
Batch tag tracks for set planning
Faster harmonic workflow planning
Producer teams
Group stems by harmonic compatibility
Cleaner remix sequencing
Show 1 more scenario
Music supervisors
Curate catalogs by key metadata
Reduced curation time
Applies structured key outputs to speed catalog filtering and reduce manual cross-checking.
Best for: Fits when music teams need repeatable library tagging with export-driven automation.
Runway
media generationAI-assisted media generation platform that includes audio tools and production workflows for generating music assets.
Project-based asset management tied to an API automation surface for generation and edits.
Runway targets production media workflows with model access plus tooling around prompt-driven generation and editing. Its integration depth centers on a defined data model for media assets and projects, and an extensibility surface that supports automation of creative tasks. Runway also provides governance hooks through permissioning and operational logging, which helps larger teams audit and control access to generation outputs.
- +Model and media asset data model for consistent project-level organization
- +API surface supports automation of generation and editing workflows
- +RBAC-style permissions for separating creators from operators and admins
- +Audit-oriented activity trails for governance over outputs and changes
- –Workflow automation often depends on prompt and asset conventions
- –Limited visibility into model internals beyond runtime inputs and outputs
- –Automation patterns require careful schema mapping for asset metadata
- –Throughput management needs manual controls for batch and queue behavior
Best for: Fits when teams need automated media generation workflows with API-driven control and auditability.
Unison
audio syncAudio synchronization and analysis tool used to align performances and manage take-level audio structure.
Event-driven web hooks tied to Unison’s versioned asset and review schema.
Unison schedules and coordinates audio production workflows across collaborators using an API-driven project data model. It maps assets, versions, and reviews into a structured schema so automation can run on consistent entities.
Integration depth is supported by connectors and web hooks that keep downstream tools synchronized with state changes. Admin controls cover user roles, provisioning boundaries, and audit visibility for workflow-altering actions.
- +Schema-based data model links assets, versions, and review states
- +API surface supports automation on entity changes and workflow events
- +Web hooks and integrations reduce manual sync across tools
- +RBAC boundaries separate editing, review, and admin responsibilities
- +Audit log records workflow changes and access-relevant events
- –Complex workflows require careful configuration of schemas and permissions
- –Automation depends on correct event wiring and idempotent handlers
- –Deep customization needs engineering time for API and integration logic
Best for: Fits when teams need controlled automation around audio asset lifecycles.
Ableton Live
DAWDAW workflow tool with project files, automation lanes, and extensible control surfaces for reproducible audio production.
Clip-level automation recording in Session View with looping that stays editable across Arrangement.
Ableton Live fits producers and small studios that prioritize fast session workflows and tight audio-to-MIDI iteration. The integration depth is centered on Live’s internal routing model and controller mapping, with automation lanes, clip envelopes, and track-level modulation.
The data model is built around projects containing Arrangement and Session views with clips, devices, and automation data that can be recorded and edited. Automation and extensibility rely on device parameters, MIDI control surfaces, and supported scripting interfaces rather than a general-purpose external API.
- +Session and Arrangement share the same clip and automation data model
- +Automation lanes record, edit, and loop with sample-accurate playback
- +Extensive MIDI mapping for controllers and custom performance workflows
- +Device parameter automation supports deep sound design iteration
- –External automation lacks a general-purpose administrative API surface
- –No RBAC model or audit log for multi-user governance inside projects
- –Scripting and extensibility focus on performance control, not enterprise provisioning
- –Project state changes are harder to track automatically outside Ableton
Best for: Fits when solo or small teams need repeatable session automation without external governance controls.
Logic Pro
DAWDAW with track automation, project management, and audio editing structures designed for repeatable composition workflows.
Automation lanes that record and play back parameter changes across channel strips and instruments.
Logic Pro is differentiated by deep macOS integration, tight access to Apple audio frameworks, and extensive automation inside the project data model. It supports arrangement, MIDI, and audio workflows with automation lanes, parameter recording, and dependable offline bounce for repeatable output.
Extensibility comes through AU plug-in hosting, Logic Pro plug-in development, and scripting hooks via Apple automation technologies. Governance is largely local to the Mac, with project-level organization and iCloud-driven collaboration rather than centralized RBAC and admin controls.
- +AU plug-in hosting with stable routing and automation mapping
- +Comprehensive automation lanes for instrument and mixer parameters
- +Project data model preserves edits for repeatable renders
- +Mac-native workflows integrate with Apple audio and device tooling
- –No centralized RBAC or tenant admin for teams
- –Automation APIs are limited compared with server-first music platforms
- –Cross-machine governance depends on project file handling
- –Limited audit-log and policy enforcement beyond local workflows
Best for: Fits when teams need local, project-centric automation and AU extensibility on macOS.
FL Studio
DAWDAW with pattern-based sequencing, automation support, and project organization for iterative production of music deliverables.
Automation lanes tied to piano roll events and plugin parameters across the project timeline.
FL Studio from Image-Line targets music production with a workflow built around its pattern-based and piano roll arrangement model. Automation is centered on channel and clip automation lanes, plugin parameter automation, and tight tempo and time signature handling during playback.
The plugin ecosystem and internal routing support deep integration inside a single project, with shared transport and automation timing across instruments and effects. However, FL Studio offers limited documented API and external data model control compared with DAW tools that expose provisioning, RBAC, and audit-log governance for automation at scale.
- +Pattern and piano roll arrangement model supports fast iteration workflows.
- +Channel and clip automation lanes handle detailed parameter movements.
- +Plugin parameter automation tracks with transport and tempo changes.
- –External automation API surface is limited versus automation-first DAWs.
- –Project data model schema access is not exposed for programmatic provisioning.
- –Administration controls for team governance like RBAC are not a documented focus.
Best for: Fits when production stays inside one studio setup and automation is mostly project-local.
Reaper
automation-first DAWDAW designed for automation-heavy workflows with project scripting and extensible behaviors for controlled production pipelines.
Metadata-driven project templates that output consistent produce music releases.
Reaper renders produce music assets from structured metadata in a browser UI and supports file-based exports for production workflows. Integration depth centers on how Reaper’s data model maps releases, stems, and licensing metadata into repeatable project outputs.
Reaper supports automation through configurable templates and repeatable generation steps, with an API surface that is oriented around remote project creation and asset processing. Governance controls focus on workspace-level access rules and project ownership boundaries rather than fine-grained per-object RBAC.
- +Structured metadata drives consistent release output across projects
- +Repeatable generation templates reduce manual editing steps
- +Automation supports remote processing for asset creation pipelines
- +Workspace permissions define project ownership boundaries
- –Fine-grained RBAC is limited for nested objects like stems
- –Audit log detail is shallow for automation and access events
- –API surface favors batch processing over interactive edit control
- –Schema customization options are narrower than spreadsheet-style imports
Best for: Fits when teams need metadata-driven asset generation with controlled ownership boundaries.
How to Choose the Right Produce Music Software
This buyer's guide covers Produce Music Software tools built for session-to-render automation and audio workflow repeatability, including LoopCloud, Krotos Toolbox, Mixed In Key, Runway, Unison, Ableton Live, Logic Pro, FL Studio, and Reaper.
The guide maps evaluation criteria to concrete mechanisms like API-driven job submission, event-driven web hooks, export-driven metadata workflows, and local DAW automation lanes so selection targets integration and control depth rather than generic editing features.
Produce Music Software that turns session work into repeatable assets, metadata, and render outcomes
Produce Music Software systems coordinate how audio and project artifacts move through production steps, including analysis, tagging, generation, versioning, rendering, and export. The core value is reducing manual drift by using a defined data model and a controlled automation surface, then applying governance like RBAC and audit logging where teams need it.
Tools like LoopCloud formalize projects, render jobs, and monitored state so DAW sessions can be processed consistently. Mixed In Key focuses on key and harmonic compatibility analysis that outputs metadata for pairing, sequencing, and library organization through batch processing.
Evaluation criteria for integration depth, automation surface, and governance controls
Produce music workflows fail at scale when the automation surface does not map cleanly to a stable schema for projects, assets, parameters, and results. Evaluation should prioritize how the tool expresses that schema and how automation interacts with it across batch throughput and state changes.
Governance matters when multiple operators touch the same assets, because RBAC boundaries and audit log visibility determine who can trigger renders, edits, and version changes. LoopCloud and Unison show what strong admin control looks like when orchestration depends on consistent entity lifecycles.
API-first render and processing workflow tied to versioned sessions
LoopCloud maps project sessions and render objects into a workflow schema and supports API-driven job submission with monitored job state. This makes session-to-render throughput repeatable when studios need automated processing rather than manual render tracking.
Event-driven entity lifecycle automation via web hooks and versioned schemas
Unison coordinates audio asset lifecycles using an API-driven project data model that includes assets, versions, and review states. Its event-driven web hooks connect schema entities to downstream sync so workflow changes propagate based on versioned events.
Batch automation driven by reusable audio processing presets and asset-bound parameters
Krotos Toolbox uses an asset-centric data model that links audio inputs to parameter sets and supports batch processing through reusable presets. This design reduces parameter drift across repeated sound design runs and batch jobs.
Exportable analysis metadata for library tagging and pairing-ready organization
Mixed In Key generates key and harmonic compatibility metadata using batch processing and outputs results that integrate through export and metadata mappings. This supports high-throughput library workflows where automation starts from analyzed attributes rather than direct DAW control.
Project-level asset management and API automation for generation and edits with audit visibility
Runway defines a data model for media assets and projects and provides an API surface for automation of generation and edits. It also includes permissioning and activity trails so audit-oriented governance covers outputs and changes.
Local DAW automation lanes for parameter recording with controlled iteration inside a project
Ableton Live and Logic Pro store automation changes inside their project models through automation lanes and controller or AU plug-in mapping. Ableton Live records clip-level automation in Session View with looping that stays editable across Arrangement, while Logic Pro records parameter changes across channel strips and instruments.
Metadata-driven project templates for consistent release output with workspace ownership boundaries
Reaper uses structured metadata and repeatable generation templates to produce consistent release outputs across projects. Its governance focuses on workspace permissions and project ownership boundaries rather than nested-object RBAC, which fits teams that need controlled ownership but not granular per-stem rights.
Decision framework for selecting a tool that matches the production control model
Start with the control plane needed by the workflow, since tools divide sharply between server-style automation and project-local automation. LoopCloud, Unison, and Runway expose automation through API surfaces tied to project and media data models, while Ableton Live and Logic Pro center automation lanes inside the DAW project.
Then validate that the data model maps to real entities like projects, assets, parameters, versions, jobs, and results so automation stays deterministic. Finally, check governance coverage by confirming RBAC and audit log behavior for the actions operators will perform, such as render submission and workflow-altering changes.
Match the automation surface to the workflow trigger type
If production requires external systems to submit and monitor processing runs, choose LoopCloud for API-driven render job submission tied to versioned project sessions. If workflows depend on state changes across asset versions and review steps, choose Unison for event-driven web hooks tied to a versioned asset and review schema.
Validate the data model against the entities that must stay stable
LoopCloud’s Project and render objects map to a clear workflow schema, which reduces mismatch between DAW sessions and downstream rendering. Runway’s project-based asset data model supports consistent media organization for generation and edits, which matters when automation needs predictable asset metadata.
Check how batch repeatability is achieved for sound processing
If repeatability is mostly about parameterized audio processing, evaluate Krotos Toolbox because it binds audio inputs to parameter sets and runs batch automation from reusable presets. If repeatability is about library organization and pairing metadata, evaluate Mixed In Key because it produces key and harmonic compatibility outputs intended for export-driven tagging workflows.
Confirm governance coverage for multi-user operations and audit needs
For studios that need controlled access across operators and admins, LoopCloud and Unison provide RBAC-oriented multi-user boundaries and audit-friendly operational patterns. For teams running automated generation and edits, Runway adds permissioning and activity trails that track governance over outputs and changes.
Decide whether automation stays inside the DAW project or exits to the platform
If automation is mostly clip-level performance iteration inside one environment, Ableton Live and Logic Pro keep automation lanes and parameter changes inside the project model. If external orchestration and controlled processing are the priority, Reaper’s metadata-driven templates and workspace permissions fit, while Ableton Live and Logic Pro do not provide centralized RBAC and audit-log governance for multi-user automation.
Plan for integration effort where control depends on supported connectors
LoopCloud’s workflow flexibility depends on supported DAW integrations, so custom audio toolchains require orchestration glue beyond the core render API. Unison automation depends on correct event wiring and idempotent handlers, so the integration plan must include schema and permission mapping for entity changes.
Which production teams should pick which tool based on their control needs
Produce music software selection is driven by how automation must run and who must control it. Tools built around API automation, event hooks, and versioned schemas target production pipelines that move assets through repeatable processing steps.
DAW-centric tools like Ableton Live and Logic Pro fit when automation stays local to a project and governance is not managed through centralized RBAC and audit logs. Library-wide metadata tagging fits tools like Mixed In Key that output pairing-ready harmonic information for workflow organization.
Studios needing session-to-render throughput via API orchestration
LoopCloud fits because it provides API-first provisioning of render jobs tied to versioned project sessions and supports monitored job state for reliable processing queues. This approach targets teams that automate render workflows instead of manually checking progress.
Audio production teams running repeatable batch sound processing with controlled parameters
Krotos Toolbox fits because it links audio inputs to parameter sets and drives batch automation from reusable presets. This supports consistent repeatability across projects where configuration drift breaks outcomes.
Music teams building faster library workflows through harmonic tagging
Mixed In Key fits because it generates key and harmonic compatibility metadata and supports batch processing for library-wide tagging. Exportable analysis outputs enable pairing-ready metadata for sequencing and set planning.
Teams automating media generation and edits with audit-oriented control
Runway fits because it uses a project-based asset data model tied to an API automation surface for generation and editing. Permissioning and audit-oriented activity trails support governance over outputs and changes.
Collaborative audio pipelines that require lifecycle automation around assets, versions, and reviews
Unison fits because it schedules and coordinates workflows using an API-driven project data model that maps assets, versions, and review states. Its event-driven web hooks help keep downstream tools synchronized when workflow-altering events happen.
Common selection and integration pitfalls across production automation tools
Most failures come from mismatches between automation goals and the tool’s exposed control surface. Some tools automate processing and governance through API and schemas, while DAWs automate performance and parameter changes inside project models without centralized multi-user admin control.
Another recurring issue comes from assuming every tool offers deep external automation or granular RBAC and audit log detail. Mixed In Key and Reaper focus on metadata-driven workflows and ownership boundaries, while Ableton Live and Logic Pro emphasize local automation lanes rather than platform-level governance.
Selecting a DAW automation tool for enterprise-style RBAC and audit requirements
Ableton Live and Logic Pro center automation lanes and project-centric organization but do not provide a centralized RBAC model or audit-log governance for multi-user operations. For governance-heavy automation, tools like LoopCloud and Unison focus on RBAC-oriented boundaries and audit-friendly operational patterns tied to workflow actions.
Assuming external automation is available when automation is export-driven or file-based
Mixed In Key automation is primarily file and export driven, which limits external provisioning through direct system hooks. If automation must be orchestrated through an API, LoopCloud and Unison provide API and event surfaces tied to job or versioned schema entities.
Overestimating schema extensibility for bespoke pipeline objects
Krotos Toolbox provides an asset-centric data model with schema and preset workflows, but schema extensibility can feel constrained for bespoke pipeline objects. Unison also requires careful configuration of schemas and permissions, so complex custom entity models require engineering time for API and integration logic.
Ignoring event wiring and idempotency in event-driven automation
Unison automation depends on correct event wiring and idempotent handlers, so incomplete wiring can cause inconsistent state synchronization. LoopCloud’s monitored job state reduces ambiguity for processing queues, which helps avoid manual recovery when orchestration fails.
Building a workflow around interactive edit control when the API is batch-oriented
Reaper’s API surface favors batch processing and remote project creation for asset creation pipelines, and its audit log detail is shallow for nested-object automation and access events. If interactive edit governance and fine-grained audit trails are required, LoopCloud and Unison provide more explicit workflow state and audit-friendly operational patterns tied to entity actions.
How We Selected and Ranked These Tools
We evaluated LoopCloud, Krotos Toolbox, Mixed In Key, Runway, Unison, Ableton Live, Logic Pro, FL Studio, and Reaper using a criteria-based scorecard that separated features, ease of use, and value, with features carrying the most weight in the final result. We then applied editorial weighting so features account for the largest share while ease of use and value each influence the outcome strongly. This scoring reflects how these tools actually behave in production workflows, including API automation and job or asset state handling rather than only editing capability.
LoopCloud stood apart because its API-first provisioning of render jobs ties monitored job state to versioned project sessions, which directly improves session-to-render throughput and predictability. That capability lifted LoopCloud most in the features category where integration depth and automation control are the primary selection drivers.
Frequently Asked Questions About Produce Music Software
Which produce music tools support API automation for multi-step workflows like session-to-render or media generation?
How do these tools handle integrations with existing DAW sessions, especially for automation and parameter changes?
What tool choice works best for batch processing audio assets with repeatable configuration and controlled parameters?
Which tools are designed for asset lifecycle governance with admin controls and audit visibility?
How do data migrations work when switching from manual tagging or local workflows to a schema-driven system?
Which produce music software provides event-driven synchronization between systems using web hooks or connectors?
What tool fits teams that need structured music library tagging based on key and harmonic metadata instead of DAW-style editing?
Where do these tools differ in handling automation fidelity and editability after export or rendering?
What common failure mode occurs when automation templates and data models do not match, and how do tools mitigate it?
Conclusion
After evaluating 9 music and audio, LoopCloud 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
Music And Audio alternatives
See side-by-side comparisons of music and audio tools and pick the right one for your stack.
Compare music and audio 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.