GITNUXSOFTWARE ADVICE
Cybersecurity Information SecurityTop 9 Best Proksi Software of 2026
Top 10 Best Proksi Software ranking with technical criteria and tradeoffs for proxy setup and testing, including Oxylabs Proxy Manager, Smartproxy, Bright Data.
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.
Oxylabs Proxy Manager
Policy-based allocation tied to a proxy inventory data model for repeatable automation.
Built for fits when teams need controlled proxy allocation with API automation and governance..
Smartproxy
Editor pickAPI-first proxy provisioning and per-request routing configuration for automated jobs.
Built for fits when automation teams need API-controlled proxy routing with governance controls..
Bright Data
Editor pickAPI-driven proxy configuration that maps routing and identity controls into automation-ready parameters.
Built for fits when integration-heavy teams need proxy automation with RBAC and audit logging..
Related reading
Comparison Table
This comparison table maps Proksi Software tools across integration depth, data model, and the automation plus API surface used for provisioning. It also contrasts admin and governance controls such as RBAC, audit log coverage, and configuration patterns that affect throughput and sandboxing. The goal is to show concrete tradeoffs in schema design, extensibility, and operational control rather than feature lists.
Oxylabs Proxy Manager
API-managedAPI-driven proxy management that serves authenticated proxy access with programmatic configuration for routing, credentials, and usage control.
Policy-based allocation tied to a proxy inventory data model for repeatable automation.
Oxylabs Proxy Manager is suited for proxy operations that require repeatable provisioning and deterministic allocation. The data model groups proxy resources into inventory and ties them to routing configuration and usage policies so automation can request specific capabilities rather than ad hoc endpoints. The API supports machine-driven configuration changes, which helps teams integrate proxy allocation into crawlers, scrapers, or monitoring pipelines.
A key tradeoff is higher configuration discipline. Teams need clear schemas for allocation rules and project boundaries or automation will create many overlapping configurations. It fits situations where multiple services must share proxy inventory with controlled assignment and where governance requirements demand RBAC and audit trails.
- +API-driven provisioning enables automated proxy allocation workflows
- +Data model ties proxy inventory to routing and usage policies
- +RBAC and change controls support controlled multi-team administration
- +Supports rotation and reconfiguration without manual endpoint edits
- –Requires upfront schema and project structure for clean automation
- –Complex rule sets can increase operational overhead
Ad tech operations teams
Automate partner endpoint scraping routes
Lower manual routing changes
Enterprise data engineering teams
Manage shared proxy pools across services
Consistent allocation across pipelines
Show 2 more scenarios
Security and governance teams
Audit proxy changes and access
Clear change accountability
Admin controls and audit visibility track who modified allocation rules and when.
QA automation teams
Reproducible test traffic routing
More repeatable test outcomes
Sandbox-like configuration sets map proxy assignments to test suites for repeatability.
Best for: Fits when teams need controlled proxy allocation with API automation and governance.
More related reading
Smartproxy
automation APIProvisioning and credential-based proxy access through a programmatic interface that supports automation for rotation and target-specific routing.
API-first proxy provisioning and per-request routing configuration for automated jobs.
Smartproxy fits organizations that need integration depth between proxy routing and downstream systems like crawlers, validators, and ETL jobs. The API surface supports programmatic selection and configuration of proxy usage so automation can apply policy at request time. A structured data model for proxy credentials and pools enables repeatable provisioning and repeatable runs.
A key tradeoff is that finer routing behavior depends on API-driven configuration rather than a purely manual console workflow. Smartproxy is a strong fit when automation needs consistent proxy selection and predictable throughput under job schedulers, CI pipelines, or batch fetchers.
- +API-driven proxy provisioning for job schedulers and ETL pipelines
- +Per-request configuration reduces routing drift across automated runs
- +IP pool management supports repeatable sourcing for datasets
- +Operational controls help enforce governance during high-volume runs
- –Advanced routing requires API configuration instead of console-only setup
- –Workflow design needs careful credential and pool mapping
Growth analytics teams
Schedule large crawl jobs with stable routing
More stable dataset collection
Data engineering teams
Feed ETL pipelines with controlled proxy access
Repeatable pipeline sourcing
Show 2 more scenarios
Security and compliance teams
Restrict proxy usage via admin governance
Tighter usage governance
RBAC-style access control and auditable operations support controlled proxy consumption.
QA automation teams
Run deterministic browserless tests through proxies
More deterministic test behavior
Automation can switch IP pools predictably for test scenarios and regression runs.
Best for: Fits when automation teams need API-controlled proxy routing with governance controls.
Bright Data
enterprise APIProxy infrastructure with automated access controls and API integration for allocation handling and request routing.
API-driven proxy configuration that maps routing and identity controls into automation-ready parameters.
Bright Data’s integration depth shows up in its automation and API surface for proxy provisioning and request routing, which fits teams that already run orchestration layers. The data model treats target endpoints, browser or HTTP modes, and delivery constraints as structured configuration inputs rather than ad hoc proxy settings. Throughput management and session persistence controls are handled via request parameters, which reduces custom gateway code. Admin governance is covered with RBAC boundaries and audit logs that record administrative and operational changes.
A tradeoff is that richer configuration and data model options require stronger engineering discipline to maintain stable request schemas across environments. Bright Data is a strong match when automated pipelines must scale while preserving control over geolocation, identity, and request behavior. It is less suitable when an organization only needs a minimal static proxy list with no automation or audit trail requirements.
- +API-first proxy provisioning and routing for automation workflows
- +Structured data model for request configuration and target selection
- +RBAC and audit logs for governance over proxy operations
- +Extensibility across scraping, crawling, and enrichment pipelines
- –Schema-heavy configuration increases maintenance effort
- –Advanced controls demand engineering time for stable operations
- –Governance features add complexity to day-to-day administration
Platform engineering teams
Route requests by geolocation and identity
Consistent behavior across environments
Growth and research teams
Automate large-scale web collection
Higher throughput with fewer manual steps
Show 2 more scenarios
Security and compliance teams
Audit proxy configuration changes
Clear operational change history
Track admin actions through audit logs and limit access with RBAC roles.
Data engineering teams
Run enrichment pipelines with schema inputs
More stable ingestion jobs
Integrate Bright Data outputs into ETL stages with repeatable request configuration.
Best for: Fits when integration-heavy teams need proxy automation with RBAC and audit logging.
Webshare
API accessSelf-serve proxy accounts with API-based management features that allow scripted authentication and usage tracking.
Programmatic proxy endpoint provisioning with identity rotation controls via API
Webshare provides a proxy and data egress layer with an API surface for provisioning proxy endpoints and managing routing configuration. Integration depth is driven by a programmatic workflow for rotating identities and managing request parameters at scale.
The data model centers on proxy settings, authentication, and session-like attributes that map cleanly to automation. Admin governance focuses on access control and operational visibility, including audit logging and role-based permissions for management actions.
- +API-first provisioning for proxy endpoints and configuration changes
- +Identity rotation controls map to automation workflows
- +Config schema supports request parameterization and routing
- +Audit logs support traceability for administrative actions
- +Role-based access controls limit who can change proxy settings
- –Automation requires careful mapping of routing parameters to schema
- –Throughput tuning can require deeper platform-specific experimentation
- –Operational visibility depends on correct log retention configuration
Best for: Fits when teams need API-driven proxy provisioning and governance for automated traffic routing.
ProxyRack
pool managementProxy pool access with account-based controls that support scripted endpoint selection for high-throughput automation.
API-driven proxy provisioning and rotation tied to configurable session behavior.
ProxyRack provisions proxy endpoints and rotates credentials through an API-driven workflow rather than manual console changes. ProxyRack’s administration model emphasizes configuration of targets, session behavior, and access boundaries for teams.
The solution centers on automation and extensibility for integrating proxy selection, switching, and routing into existing systems. Governance features include role-based access controls and audit visibility for administrative actions across environments.
- +API-first provisioning for proxy endpoints and rotation workflows
- +Configurable routing controls for target selection and session behavior
- +RBAC support for separating admin duties across teams
- +Audit logging for administrative changes and governance tracking
- –Data model documentation can limit schema-first automation planning
- –Automation depends on correct configuration of rotation and session settings
- –Operational visibility into per-request outcomes needs external logging
- –Complex setups may require careful environment segregation
Best for: Fits when teams need automated proxy provisioning with RBAC and audit visibility.
Proxy-Seller
automation endpointsProxy services with hosted endpoints and scripted authentication patterns designed for automated traffic distribution.
API-based proxy provisioning with rotation aligned to an explicit proxy usage data model.
Proxy-Seller fits teams that need controlled proxy provisioning for workloads that consume proxies through scripted automation. It focuses on an operational data model for proxy identities, endpoints, and usage status, which supports repeatable configuration and auditing.
The integration depth is expressed through an API surface and automation flows for requesting and rotating proxies without manual steps. Admin and governance controls center on access boundaries, configuration management, and traceability through audit-oriented operational records.
- +API-driven proxy provisioning supports automated rotation and workload scheduling
- +Structured data model tracks proxy endpoints and usage status for repeatable operations
- +RBAC-style access boundaries support delegated operations across teams
- +Audit-oriented operational records improve traceability for proxy requests
- –Throughput can be constrained by per-request provisioning flows
- –Schema customization appears limited for niche proxy metadata requirements
- –Automation depends on API correctness since failures surface as operational errors
- –Sandboxing proxy workflows may be limited for safe testing of integration changes
Best for: Fits when teams need API-based proxy provisioning with governance and audit trails.
IPRoyal Proxy Network
network proxiesProxy network offering account credentials and programmatic usage patterns for automated request handling and allocation changes.
Managed proxy provisioning with rotation controls driven by account configuration
IPRoyal Proxy Network is a proxy network solution focused on integration breadth through provisioning, authentication, and rotation controls. The product centers on a configurable data model for proxy endpoints, credentials, and usage constraints that supports repeatable automation patterns.
Governance relies on admin controls tied to account-level access boundaries and operational reporting. API and automation surface are designed around feeding request workflows with managed proxy lists rather than manual endpoint handling.
- +Provisioning workflow supports repeatable proxy endpoint configuration
- +Rotation and routing controls map to automation-friendly request patterns
- +Account-level governance supports separation of access for teams
- +Operational reporting helps trace usage against configured endpoints
- –Data model granularity can feel limited for multi-tenant RBAC designs
- –Automation depth depends on available API coverage for edge cases
- –Audit log detail may not match workflows needing per-request provenance
Best for: Fits when teams need controlled proxy provisioning with automation hooks for request workflows.
Genproxy
rotating proxiesProxy access service with programmatic-friendly account credentials for rotation and endpoint selection in automated systems.
API-based provisioning of proxy identities tied to routing and rotation policies
Genproxy is a proxy and connectivity management tool positioned for team-level control of outbound access. It provides configuration, provisioning, and automation hooks for rotating proxy endpoints and managing routing behavior.
Genproxy emphasizes an integration-first approach with an API surface and structured data model for managing proxy identities, targets, and usage policies. Governance is handled through admin controls and audit-style visibility for changes and operational activity.
- +API-first provisioning for proxy identities and routing policies
- +Config-driven proxy rotation controls for predictable outbound behavior
- +Structured data model for managing proxy targets and associations
- +Admin controls that support role-based separation of duties
- +Automation surface suitable for orchestration and scheduled changes
- –Automation depends on correct schema mapping for proxy and policy objects
- –Throughput tuning requires careful configuration to avoid bottlenecks
- –RBAC and audit log depth may not cover every custom governance need
Best for: Fits when teams need API-driven proxy provisioning with governance and repeatable configuration.
Privatix
proxy serviceProxy service that exposes authenticated proxy access for scripted usage where endpoint assignment needs to be automated.
RBAC-protected API provisioning with audit logs for proxy configuration and access changes.
Privatix provisions and routes proxy access using a managed configuration and identity layer. Integration centers on an API and automation hooks that map proxy usage to a defined data model.
Administrative control focuses on RBAC-driven governance and traceable audit logging for access and configuration changes. Throughput depends on how schemas and connection pools are configured per tenant and route.
- +API-first provisioning supports repeatable proxy setup from automation scripts
- +RBAC controls segment access to proxy definitions and management actions
- +Audit logs capture configuration and access events for governance reviews
- +Config schema separates tenant settings from routing and auth details
- –Integration depth depends on API coverage for every proxy parameter
- –Data model rigidity can add overhead when building custom routing schemes
- –Automation surface appears less granular for per-request policy changes
- –Admin controls require careful schema design to avoid policy sprawl
Best for: Fits when teams need API-driven proxy provisioning with RBAC governance and audit logging.
How to Choose the Right Proksi Software
This buyer’s guide covers Oxylabs Proxy Manager, Smartproxy, Bright Data, Webshare, ProxyRack, Proxy-Seller, IPRoyal Proxy Network, Genproxy, and Privatix, with a focus on how each tool exposes proxy control via API and configuration.
The guide compares integration depth, the proxy data model used for allocation and routing, and the available automation and API surface for provisioning, rotation, and retirement. It also maps admin and governance controls such as RBAC and audit logging to practical multi-team operations.
API-managed proxy endpoints, identities, and routing policies for automated workloads
Proksi Software tools provision authenticated proxy endpoints and pair them with routing and identity controls so automated systems can request proxy access without manual endpoint edits. These tools solve proxy assignment drift by tying proxy inventory, credentials, and routing rules to a defined configuration schema.
Oxylabs Proxy Manager represents this approach with a policy-based allocation model backed by proxy inventory tied to routing and usage policies. Bright Data applies the same automation pattern through API-driven proxy configuration that maps routing and identity controls into automation-ready parameters for collection workflows.
Integration, data model control, automation surface, and governance controls
The fastest automation outcomes come from tools that expose the proxy inventory and routing rules as a documented API surface. Smartproxy and Webshare emphasize API-first provisioning and per-request or session-style configuration so orchestration systems can set intent on every run.
Governance features matter when multiple teams can change routing behavior. Oxylabs Proxy Manager, Bright Data, Webshare, and Privatix include RBAC and audit-oriented visibility so administrative actions remain traceable and restricted to authorized roles.
Policy-based proxy inventory tied to routing and usage rules
Oxylabs Proxy Manager maps proxy inventory to routing and usage policies so automated workflows can create, rotate, and retire routes based on stable policy objects. Proxy-Seller and IPRoyal Proxy Network also track endpoints and usage status with an explicit model, but Oxylabs couples allocation behavior directly to inventory policies for repeatable automation.
API-first provisioning with programmatic endpoint and credential assignment
Smartproxy and Webshare provide API-driven proxy endpoint provisioning and scripted configuration changes so job schedulers and ETL pipelines can manage proxy access without console steps. Bright Data and Oxylabs also emphasize API-driven proxy provisioning, with Bright Data focused on schema-driven routing and Oxylabs focused on inventory allocation workflows.
Per-request routing configuration to reduce automation drift
Smartproxy supports per-request configuration so routing controls stay consistent across automated runs. Bright Data and Webshare route configuration through structured inputs, which helps keep target selection and request parameters aligned with automation outputs.
Rotation controls linked to explicit session behavior or policy objects
ProxyRack rotates credentials through an API-driven workflow and ties rotation to configurable session behavior for predictable switching. Oxylabs Proxy Manager supports rotation and reconfiguration without manual endpoint edits by using inventory and allocation rules connected to routing behavior.
RBAC and audit logs for multi-team admin governance
Bright Data, Oxylabs Proxy Manager, and Privatix protect proxy configuration and access with RBAC and audit logging so changes can be reviewed for governance. Webshare and ProxyRack also include role-based access controls and audit visibility, which helps limit who can change proxy settings.
Schema and data model structure for provisioning extensibility
Bright Data’s structured data model for request configuration and target selection fits teams that treat routing as a configuration schema. Genproxy and Privatix also provide structured data models for proxy identities, targets, and tenant settings, which supports repeatable configuration when automation needs clean object boundaries.
Choose by automation contract, schema fit, and governance depth
Selection works best when the proxy tool’s API and data model match the automation contract used by internal systems. Oxylabs Proxy Manager and Smartproxy excel when orchestration needs programmatic provisioning and stable routing intent with rotation and retirement logic.
Governance should be validated against how admin duties are split across teams. Bright Data and Privatix add RBAC plus audit logging for configuration and access changes, which is critical when multiple roles can affect routing behavior.
Map the required automation workflow to the tool’s API surface
List the automation steps needed for proxy access, including provisioning, routing configuration, rotation, and retirement. Oxylabs Proxy Manager and Smartproxy fit when automation must create and reconfigure routes programmatically, while Webshare and ProxyRack fit when scripted endpoint provisioning and identity rotation controls need to be managed through an API.
Validate the data model fit for proxy inventory, identities, and routing policies
Confirm how the tool represents proxy inventory, credentials, and routing rules as configuration objects. Oxylabs Proxy Manager stands out with a policy-based allocation model tied to proxy inventory and usage policies, while Bright Data relies on schema-heavy structured request configuration for target selection and routing identity controls.
Decide whether per-request routing control is required
Require per-request routing configuration when workloads vary target selection and routing parameters across runs. Smartproxy supports per-request configuration to reduce routing drift, while Webshare and Bright Data route configuration through structured schema inputs that can be generated per job.
Set governance requirements and match them to RBAC and audit logging behavior
Define which roles can change routing and proxy access configuration, and require RBAC plus audit logs for administrative actions. Bright Data and Privatix focus on RBAC and audit logging for proxy operations, and Oxylabs Proxy Manager also combines RBAC with operational auditability for controlled multi-team administration.
Plan for schema workload and operational overhead before committing
Estimate how much engineering time is acceptable for schema-heavy configuration and rule maintenance. Bright Data and Oxylabs both emphasize structured configuration, and Oxylabs can add overhead when rule sets become complex, while Webshare can require careful mapping of routing parameters into its schema.
Test rotation and session behavior using the tool’s rotation model
Check how rotation relates to session-like behavior and how switching behaves under automation. ProxyRack explicitly ties rotation to configurable session behavior, while Oxylabs supports rotation and reconfiguration without manual endpoint edits through its inventory allocation rules.
Teams that need controlled proxy provisioning with API governance
Proksi Software tools fit organizations that want authenticated proxy access driven by automation, not manual endpoint handling. These tools matter most when proxy allocation must match routing policy objects and when multiple teams must share configuration controls.
The strongest matches come from the best_for segments, including Oxylabs Proxy Manager for controlled API automation and governance, Smartproxy for API-controlled proxy routing for automated jobs, and Bright Data for RBAC and audit logging in integration-heavy environments.
Automation teams that need controlled proxy allocation with governance
Oxylabs Proxy Manager fits when teams need policy-based allocation tied to proxy inventory and usage policies so automation can create, rotate, and retire routes. Its RBAC and operational auditability support controlled multi-team administration when routing behavior must be changed by authorized roles.
Job schedulers and ETL pipelines that need API-controlled routing per run
Smartproxy fits when API-first proxy provisioning and per-request routing configuration are required for consistent automated jobs. Its IP pool management and operational checks support repeatable sourcing for dataset collection at high volume.
Integration-heavy teams that need RBAC and audit logging across proxy operations
Bright Data fits when proxy automation must include RBAC plus audit logs for oversight during collection, crawling, and enrichment workflows. Its structured data model for request configuration maps routing and identity controls into automation-ready inputs.
Teams that want scripted endpoint provisioning and identity rotation controls
Webshare fits when proxy endpoint provisioning and identity rotation controls must be managed via API workflows. It includes audit logs and role-based permissions for management actions and supports configuration schema for request parameterization.
Organizations that require RBAC-protected API provisioning with traceable audit logging
Privatix fits when RBAC-protected API provisioning and audit logging for configuration and access changes are required for governance reviews. It separates tenant settings from routing and authentication details through its configuration schema.
Schema mismatch, governance gaps, and missing per-request control
Common failures come from selecting a proxy tool whose configuration schema does not match the automation system’s object model. Teams often overestimate how much routing flexibility is available without careful schema mapping.
Governance mistakes also occur when RBAC and audit logging are not aligned to how admin duties are split. Several tools provide governance controls, but some operational visibility relies on correct log retention configuration or external logging.
Assuming automation works without aligning to the proxy configuration schema
Bright Data and Oxylabs Proxy Manager both use schema-heavy configuration patterns, so routing stability depends on setting up correct policy and object structures before scaling. Webshare also requires careful mapping of routing parameters to its schema to avoid configuration drift.
Underestimating governance complexity in multi-team environments
Bright Data, Oxylabs Proxy Manager, and Privatix include RBAC and audit logging, so governance needs should be defined before rollout. ProxyRack and Webshare can limit who can change proxy settings, but operational visibility can depend on how logs are retained and interpreted.
Ignoring per-request routing requirements and relying on static routing
Smartproxy supports per-request configuration, which reduces routing drift when targets and routing parameters change across automated runs. If per-request changes are required, tools without clear per-request routing configuration can force less reliable configuration patterns.
Overcomplicating rotation rules without validating session behavior under automation
Oxylabs Proxy Manager supports rotation and reconfiguration without manual endpoint edits, but complex rule sets can increase operational overhead. ProxyRack ties rotation to configurable session behavior, so session behavior needs validation for throughput and correctness under automated switching.
Expecting full per-request provenance without external logging
ProxyRack notes that operational visibility into per-request outcomes can require external logging, so relying only on internal audit visibility can miss request-level provenance. IPRoyal Proxy Network also ties audit detail to account-level reporting, which may not satisfy teams needing per-request provenance.
How We Selected and Ranked These Tools
We evaluated Oxylabs Proxy Manager, Smartproxy, Bright Data, Webshare, ProxyRack, Proxy-Seller, IPRoyal Proxy Network, Genproxy, and Privatix on features, ease of use, and value using the provided capability descriptions and stated standout strengths. Each tool received an overall rating treated as a weighted average where features carried the most weight and ease of use and value each contributed equally. This editorial scoring framework favors automation and control depth because proxy allocation and routing behavior must be reliable at scale.
Oxylabs Proxy Manager separated itself from lower-ranked tools through policy-based allocation tied to a proxy inventory data model for repeatable automation. That capability lifted the features score the most because it directly links provisioning, rotation, and retirement workflows to an explicit inventory and routing policy model. It also improved ease of use outcomes by reducing manual endpoint edits and routing drift during automation.
Frequently Asked Questions About Proksi Software
Which Proksi tools provide API-first proxy provisioning and per-request routing configuration?
How do the tools model proxy inventory so automation can rotate and retire endpoints consistently?
What options exist for SSO, RBAC, and audit logs for administrative changes?
Which products best support data migration when moving proxy inventory and routing rules from a legacy system?
How do admin controls differ across tools for managing who can change routing behavior?
Which platforms support extensibility through integration breadth and schema-driven inputs?
What is the typical workflow for setting up proxy rotation through an API instead of a console?
Which tools are better aligned with high-throughput scraping where throughput depends on request routing controls?
When reliability issues occur, what configuration surfaces usually explain failures like invalid sessions or mismatched identities?
Conclusion
After evaluating 9 cybersecurity information security, Oxylabs Proxy Manager 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
Cybersecurity Information Security alternatives
See side-by-side comparisons of cybersecurity information security tools and pick the right one for your stack.
Compare cybersecurity information security 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.