Commissioned Research
Top 10 Best Cloud Application Infrastructure Services of 2026

GITNUXSOFTWARE REVIEW

Telecommunications

Top 10 Best Cloud Application Infrastructure Services of 2026

Compare cloud application infrastructure services for platform teams, including what Accenture, Deloitte, and Capgemini offer and tradeoffs to weigh.

18 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Cloud application infrastructure service providers build and run the platform layer that application teams depend on for provisioning, networking, RBAC, audit logging, and workload automation. This comparison helps IT leaders and architects weigh two delivery paths, consulting-led design and migration versus managed operations for ongoing throughput, change control, and API-driven extensibility across public cloud and hybrid estates.

Accenture is the best choice for enterprises that need governed multi-cloud infrastructure delivery tied directly to application release pipelines, since its managed approach links provisioning changes with governance controls and operational runbooks, while Rackspace Technology fits teams wanting hands-on managed hybrid operations with consistent production run-state support during deployment and migration.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Accenture

Accenture’s managed delivery approach links infrastructure provisioning changes to application release pipelines with governance controls and operational runbooks.

Best for: Fits when enterprises need governed infrastructure delivery and release automation across multi-cloud programs.

2

Deloitte

Editor pick

End-to-end delivery governance that ties cloud architecture decisions to operational runbooks and audit-oriented handoffs.

Best for: Fits when large enterprises need architecture, governance, and implementation support for controlled cloud migrations.

3

Capgemini

Editor pick

Enterprise cloud delivery that ties governance, provisioning automation, and operational readiness into one execution stream.

Best for: Fits when large enterprises need integrated cloud infrastructure change across security, delivery, and operations.

Comparison Table

1
AccentureBest overall
enterprise_vendor
9.3/10
Overall
2
enterprise_vendor
8.9/10
Overall
3
enterprise_vendor
8.8/10
Overall
4
enterprise_vendor
8.4/10
Overall
5
enterprise_vendor
8.3/10
Overall
6
7.7/10
Overall
7
enterprise_vendor
7.4/10
Overall
8
enterprise_vendor
7.3/10
Overall
9
enterprise_vendor
6.9/10
Overall
10
enterprise_vendor
6.6/10
Overall
#1

Accenture

enterprise_vendor

Global professional services firm with a dedicated cloud infrastructure consulting practice.

9.3/10
Overall
Features9.3/10
Ease of Use9.5/10
Value9.1/10
Standout feature

Accenture’s managed delivery approach links infrastructure provisioning changes to application release pipelines with governance controls and operational runbooks.

Accenture supports application infrastructure through end-to-end workstreams that connect target architecture, platform engineering, and delivery operations. Engagements commonly cover multi-cloud and hybrid deployment design, infrastructure as code practices, and production readiness work that includes reliability engineering and observability stack integration. Governance depth is a recurring theme, with delivery aligned to RBAC design decisions, change controls, and audit log expectations for enterprises.

A practical tradeoff is that Accenture delivery favors structured programs with clear ownership and change management, which can slow progress for teams seeking rapid, low-ceremony experimentation. Accenture fits best when an enterprise needs coordinated provisioning across environments and repeatable deployment pipelines with controlled release behavior.

Pros
  • +Strong cross-team delivery integration across cloud engineering and governance
  • +Repeatable infrastructure as code adoption for consistent environment provisioning
  • +Production operations support with observability integration and reliability focus
  • +Structured rollout practices tied to release pipelines and change controls
Cons
  • –Structured enterprise delivery cadence can slow exploratory initiatives
  • –Requires internal ownership clarity to avoid governance bottlenecks
  • –Deep platform work can add overhead compared with smaller system integrators
  • –API and automation integration depends on alignment with client tooling
Use scenarios
  • Platform engineering leaders

    Standardize environment provisioning across clouds

    Fewer deployment inconsistencies

  • Enterprise security teams

    Apply RBAC and audit-ready change controls

    Stronger compliance traceability

Show 2 more scenarios
  • SRE and operations managers

    Integrate observability for production reliability

    Faster fault isolation

    Accenture implements centralized logging and tracing workflows that support incident response.

  • Application modernization teams

    Migrate while preserving release discipline

    Lower migration risk

    Accenture coordinates infrastructure transitions with controlled release practices and rollback planning.

Best for: Fits when enterprises need governed infrastructure delivery and release automation across multi-cloud programs.

#2

Deloitte

enterprise_vendor

Big Four firm offering cloud infrastructure strategy, migration, and managed services.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

End-to-end delivery governance that ties cloud architecture decisions to operational runbooks and audit-oriented handoffs.

Deloitte’s core strength is integration depth across the infrastructure lifecycle, from target architecture and reference patterns to delivery governance and operating runbooks. Delivery often centers on infrastructure as code practices, policy-aligned security configuration, and repeatable provisioning workflows that reduce environment drift. Deloitte teams also work outward from application requirements, so container platforms, network segmentation, and observability standards land with shared conventions rather than isolated vendor setups.

A key tradeoff is that Deloitte’s value is most consistent when the organization can commit engineering time to the target standards and participate in governance reviews. Deloitte is a strong fit when workloads must be migrated with tight controls, such as regulated application portfolios or enterprises with multiple business units sharing shared platforms.

Pros
  • +Advisory-to-implementation coverage across cloud landing zone and migration execution
  • +Governance artifacts that support change control and operational handoffs
  • +Architecture standards for infrastructure provisioning and environment consistency
  • +Security configuration guidance aligned to enterprise risk and compliance controls
Cons
  • –Delivery pace depends on client participation in governance and design reviews
  • –Extensibility tooling guidance may lag fast-moving vendor service features
  • –Automation outcomes require clear ownership of repositories and pipelines
  • –Deep specialization can mean narrower fit for small teams needing self-serve setup
Use scenarios
  • CIO office and architecture teams

    Hybrid landing zone with migration governance

    Fewer drift incidents during rollout

  • Cloud platform engineering

    Infrastructure as code standards rollout

    More repeatable environment creation

Show 2 more scenarios
  • Security engineering

    Cloud security configuration and guardrails

    Improved control coverage

    Deloitte supports policy-aligned configuration so teams maintain consistent security posture across workloads.

  • Platform SRE groups

    Operational runbooks for production handoff

    Faster production stabilization

    Deloitte documents operating procedures that connect deployment pipelines to incident and change workflows.

Best for: Fits when large enterprises need architecture, governance, and implementation support for controlled cloud migrations.

#3

Capgemini

enterprise_vendor

Global systems integrator specializing in cloud-native application infrastructure services.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Enterprise cloud delivery that ties governance, provisioning automation, and operational readiness into one execution stream.

Capgemini’s strength is translating enterprise constraints into deployable cloud operating models, including standardized provisioning workflows and controlled release processes for application environments. The delivery approach typically connects application infrastructure to identity controls, audit logging expectations, and incident response runbooks so cloud changes land inside existing governance. Integration depth is often strongest when cloud work must touch the full delivery chain, from landing zone setup through environment lifecycle and production operations.

A key tradeoff is that Capgemini’s involvement can be heavier than a tooling-only provider when the target is a narrow slice like one cluster modernization without broader operational ownership. Capgemini fits best for usage situations that require coordinated changes across infrastructure, application deployment processes, and security and observability instrumentation at the same time.

Pros
  • +End-to-end delivery from architecture through production operations
  • +Strong infrastructure automation patterns for controlled environment lifecycles
  • +Governance-oriented approach to identity and audit logging integration
  • +Integration focus between runtime deployment and observability needs
Cons
  • –Can require longer onboarding for teams lacking standardized delivery pipelines
  • –Adds organizational overhead when only small infrastructure components change
Use scenarios
  • Large regulated enterprises

    Hybrid cloud runtime modernization program

    Fewer release regressions

  • Platform engineering teams

    Multi-team container platform rollout

    Consistent environment creation

Show 1 more scenario
  • Security and risk teams

    Audit-ready cloud control integration

    More controllable access

    Capgemini integrates identity-driven access patterns and logging expectations into cloud infrastructure changes.

Best for: Fits when large enterprises need integrated cloud infrastructure change across security, delivery, and operations.

#4

Wipro

enterprise_vendor

Global technology services company with cloud infrastructure consulting and implementation.

8.4/10
Overall
Features8.4/10
Ease of Use8.4/10
Value8.4/10
Standout feature

Program-managed release governance that ties deployment activity to audit-ready operational controls.

Wipro delivers cloud application infrastructure services through delivery teams that combine platform engineering, migration execution, and managed operations. The differentiator is integration depth across enterprise environments, where Wipro ties cloud deployment pipelines to governance needs like change control and auditability.

Pros
  • +Strong integration of enterprise governance into cloud delivery workflows
  • +Operational runbooks geared for change management and incident response
  • +Hybrid modernization work that maps migration sequencing to dependencies
  • +Clear handoff patterns from build to managed day-2 operations
Cons
  • –Deeper automation depends on client-provided standards and tooling
  • –Some delivery details rely on add-on components and partner availability
  • –Extensibility via APIs varies by program and workload type
  • –Throughput tuning for platform services takes careful engineering scoping

Best for: Fits when enterprises need guided infrastructure buildout plus managed operations across hybrid or multi-cloud landscapes.

#5

Cognizant

enterprise_vendor

IT services firm with cloud application infrastructure modernization practice.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Managed engineering run models that connect deployment pipelines to operational continuity across hybrid estates.

Cognizant delivers cloud application infrastructure services that combine enterprise migration, platform modernization, and ongoing engineering delivery for regulated and complex environments. Delivery is built around managed run models, infrastructure as code practices, and integration work across application stacks and deployment pipelines.

Pros
  • +Strong hybrid environment delivery with engineering-focused run support
  • +Infrastructure as code adoption in modernization and migration programs
  • +Integration delivery across application releases and infrastructure change workflows
  • +Governance-led cloud program management for regulated deployment needs
Cons
  • –Implementation success depends on client alignment on operating model
  • –Kubernetes and service integration depth varies by specific engagement scope

Best for: Fits when enterprises need managed cloud infrastructure delivery tied to governance and release engineering.

#6

Rackspace Technology

specialist

Managed cloud services provider focused on application infrastructure operations.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

Managed cloud operations for hybrid and multi-cloud application infrastructure, combining run-state support with deployment and migration execution.

Rackspace Technology is a cloud application infrastructure provider that fits teams needing managed deployment operations for enterprise workloads across hybrid and multi-cloud environments. The service portfolio centers on managed hosting, network, and application infrastructure operations with delivery support for migration, app modernization, and ongoing run-state management.

Pros
  • +Managed operational delivery helps teams run production workloads consistently
  • +Hybrid and multi-cloud deployment support reduces platform relocation work
  • +Integration with monitoring and incident response supports continuous operations
  • +Infrastructure migration and modernization services reduce workflow handoff risk
Cons
  • –Deep customization can require governance discipline across environments
  • –Cloud-native building blocks depend more on managed services configuration
  • –API-first automation coverage can feel narrower than tooling-native competitors
  • –Operational control often shifts responsibility into the managed engagement

Best for: Fits when enterprise teams need managed cloud infrastructure operations with hybrid rollout and controlled change management.

#7

Infosys

enterprise_vendor

Global IT services provider with cloud infrastructure migration and management services.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Infosys delivery combines platform integration and ongoing runbooks to maintain cloud application infrastructure after modernization.

Infosys differentiates through delivery depth across enterprise cloud application infrastructure work, pairing architecture and engineering with sustained operations support. The service portfolio centers on managed infrastructure implementation, application modernization, and platform integration for multi-cloud and hybrid deployments.

Pros
  • +End-to-end delivery from cloud architecture through managed operations
  • +Integration work spans infrastructure, deployment pipelines, and observability
  • +Governance-focused security services fit regulated enterprise environments
  • +Hybrid and multi-cloud implementation experience supports complex landscapes
Cons
  • –Console and API control depth depends on the managed offering scope
  • –Greatest gains require active client participation in architecture decisions
  • –Migration tooling and workflows can add process overhead for smaller teams
  • –Extensibility varies by engagement design and platform chosen

Best for: Fits when large enterprises need managed cloud infrastructure delivery with architecture-to-operations continuity.

#8

Avanade

enterprise_vendor

Microsoft-focused cloud infrastructure consultancy jointly owned by Microsoft and Accenture.

7.3/10
Overall
Features7.3/10
Ease of Use7.3/10
Value7.3/10
Standout feature

Operational runbook design embedded into deployment pipelines, with release checks aligned to enterprise governance needs.

Avanade brings cloud application infrastructure delivery with deep enterprise change management, pairing managed deployment workflows with long-running app modernization programs. Its core strength is integration work across Microsoft-centric estates, where application infrastructure changes need governance, release coordination, and cross-team handoffs.

Pros
  • +Enterprise release coordination for infrastructure changes across many app owners
  • +Strong governance focus with audit-friendly operational process design
  • +Infrastructure as code implementation tied to repeatable environment provisioning
  • +Integration delivery with Microsoft-aligned tooling in hybrid estates
Cons
  • –Less suited to highly experimental app platforms without defined operations
  • –Automation quality depends on upstream team maturity and pipeline readiness
  • –Integration projects can require longer engagement to standardize runbooks
  • –Hands-on speed can slow when architecture reviews span multiple org boundaries

Best for: Fits when enterprise teams need governed infrastructure rollouts and repeatable provisioning across hybrid Microsoft-heavy estates.

#9

Tech Mahindra

enterprise_vendor

IT services and consulting firm with cloud infrastructure transformation practice.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Managed engineering for repeatable infrastructure and release workflows across enterprise cloud estates.

Tech Mahindra delivers cloud application infrastructure work through managed engineering and integration services that connect enterprise systems to cloud deployment pipelines. Its core strengths show up in automation delivery for platform setup, governance alignment, and application lifecycle support across hybrid environments.

Pros
  • +Delivery engineers build application platforms with structured deployment workflows
  • +Hybrid program experience supports enterprise connectivity patterns and operations
  • +Automation focus improves consistency across environments during releases
  • +Governance alignment is handled through service and delivery procedures
Cons
  • –On-boarding can be coordination-heavy for teams without existing cloud standards
  • –Hands-on workload transfer depends on engagement scope and partner capacity
  • –Breadth of self-serve infrastructure controls can be limited versus cloud-native tools
  • –Deep Kubernetes platform customization may require ongoing implementation support

Best for: Fits when enterprise teams need managed delivery for cloud application infrastructure across hybrid environments.

#10

DXC Technology

enterprise_vendor

IT services company providing cloud infrastructure migration and managed application services.

6.6/10
Overall
Features6.6/10
Ease of Use6.7/10
Value6.5/10
Standout feature

Runbook-based operational transition that pairs change management with managed services for enterprise workloads.

DXC Technology fits enterprises that need cloud application infrastructure delivery plus ongoing integration work across complex portfolios. Its core strength is managed operations for enterprise environments, delivered alongside cloud engineering and application modernization services.

Pros
  • +Enterprise delivery experience for long-running infrastructure modernization programs
  • +Operational handoff centered on runbooks, change control, and service continuity
  • +Multi-cloud and hybrid migration planning tied to operational constraints
  • +Integration work that covers platform setup and application infrastructure interfaces
Cons
  • –Heavier engagement model can slow down rapid product-level iteration cycles
  • –Automation and API depth depend on project scope and integration choices
  • –Standard platform onboarding feels less productized than pure-play managed services
  • –Governance-heavy change processes can add overhead for low-risk environments

Best for: Fits when large enterprises need managed cloud infrastructure delivery with strong governance and operations continuity.

Conclusion

After evaluating 10 cloud application infrastructure, Accenture 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.

Our Top Pick
Accenture

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Cloud Application Infrastructure

How do integration and API workflows differ between Accenture and Capgemini for cloud application infrastructure programs?
Accenture ties infrastructure provisioning changes to application release practices through delivery automation and governance controls. Capgemini focuses on repeatable deployment pipelines that connect platform patterns and instrumentation work, with fewer emphasis points on cross-team release coordination across complex enterprise portfolios. Teams that need tight coupling between infra change management and app release gates usually select Accenture, while teams that prioritize standardized build and run pipelines usually select Capgemini.
Which provider offers the strongest SSO and RBAC alignment for enterprise cloud access controls?
Deloitte builds infrastructure design guidance around governance practices that map access policies to operational procedures, which helps align identity and role policies with change control. Wipro ties cloud deployment pipelines to auditability and change control needs, which often includes structured access management as part of operational runbooks. Avanade fits organizations with Microsoft-centric estates where release coordination and cross-team handoffs must follow consistent enterprise access control patterns.
How should data migration and environment cutover be planned when using Cognizant versus DXC Technology?
Cognizant structures migration and modernization delivery around managed run models and infrastructure automation that reduce environment drift across hybrid and multi-cloud workloads. DXC Technology emphasizes runbook-driven operations transition, so cutover planning often starts with how production operations will run after go-live. Teams focused on migration through repeatable automation usually lean toward Cognizant, while teams focused on maintaining operational continuity during transition often lean toward DXC Technology.
What admin controls and audit logging patterns differ between Rackspace Technology and Tech Mahindra?
Rackspace Technology emphasizes managed operations with operational integration for deployment automation, monitoring, and incident response, which supports admin controls tied to run-state management. Tech Mahindra delivers automation for platform setup and governance alignment across hybrid environments, which typically includes configuration controls embedded into delivery workflows. Teams that need day-2 operational governance around incidents and change windows often align with Rackspace Technology, while teams that need automation-driven control of provisioning and release workflows often align with Tech Mahindra.
When should enterprise teams choose IBM Consulting or Deloitte style governance delivery instead of Infosys managed platform integration?
Deloitte suits programs needing controlled delivery across hybrid and multi-cloud environments with infrastructure design tied to security posture and audit-oriented handoffs. Infosys fits teams that need architecture-to-operations continuity, where platform integration and runbooks support continued platform changes after modernization. Organizations that treat deployment governance as a first-class program workstream usually select Deloitte, while organizations treating sustained platform operations as the main objective usually select Infosys.
Where does Rackspace Technology tend to fall short when teams require deep customization beyond managed operations?
Rackspace Technology centers on managed hosting and day-2 operations integration, so teams needing highly customized configuration generation and nonstandard deployment workflows may find coverage limited to managed run patterns. Accenture and Capgemini typically support deeper tailoring of delivery automation to specific enterprise release practices when the program demands custom provisioning and pipeline gating logic. Teams with unconventional rollout mechanics usually validate whether Rackspace Technology’s managed operating model can accommodate the required extensibility before committing.
Which provider handles multi-cloud and hybrid onboarding with stronger deployment pipeline handoffs for operations teams?
Infosys connects observability practices like centralized logging and distributed tracing to architecture-to-operations continuity, which helps operations teams inherit the data model and runbook context. Accenture links infrastructure provisioning changes to application release pipelines with governance controls, which supports operational handoffs tied to release events. DXC Technology uses runbook-based operational transition paired with managed services, which benefits onboarding when production readiness must be formalized through operational procedures.
What breaks if infrastructure-as-code practices are inconsistent across environments when teams engage Avanade versus Wipro?
Avanade supports predictable provisioning patterns where application infrastructure changes must follow governance and release coordination in Microsoft-centric environments. Wipro ties cloud deployment pipelines to governance needs like change control and auditability, so inconsistencies can surface as process gaps around controlled release cycles. If environment provisioning varies across pipelines, governance gates can fail and operational handoffs can lose traceability, which creates higher friction during production rollout with either Avanade or Wipro.
How do extensibility and configuration management approaches differ between Accenture and Wipro for long-lived application platforms?
Accenture’s managed delivery approach links infrastructure provisioning to application release pipelines with governance controls and operational runbooks, which supports adding new services while keeping rollout governance consistent. Wipro focuses on integration depth across enterprise environments and ties deployment activity to audit-ready operational controls, which supports configuration change traceability across releases. Teams that extend platforms through controlled release gating often select Accenture, while teams that extend platforms under strict change control and auditability often select Wipro.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Cloud Application Infrastructure

Options differ most in how much control they give over provisioning and lifecycle, and how reliably they move changes into production. We focus on Deployment workflow controls, because it shows whether the platform can automate updates without surprises.

Deployment workflow controls

Why it matters

Deployment workflow controls decide whether updates follow a repeatable path with clear rollbacks. That matters when cloud application infrastructure must keep environments stable while you iterate.

How to check

Ask the demo to show one change from code/config to a running environment. Confirm whether the product supports controlled rollouts and a rollback path, and whether you can review what will change before execution.

Configuration and secret management

Why it matters

Configuration and secret management affects how consistently environments match across teams and stages. If secrets and config drift, cloud application infrastructure becomes harder to operate and audit.

How to check

In the demo, locate where environment variables, config files, and secrets live. Then trigger a small config change and verify how the platform versions it, restricts access, and records who updated it.

RBAC and audit logging

Why it matters

RBAC and audit logging determine who can provision, modify, and delete infrastructure resources. For cloud application infrastructure, governance gaps turn routine operations into risk.

How to check

Request a role setup walkthrough, including least-privilege examples for read-only versus deploy permissions. Then perform an action (like creating an environment) and check that the audit log captures actor, time, and target resource.

Runtime observability signals

Why it matters

Runtime observability signals show whether you can understand failures across the infrastructure layer. When issues cross services and environments, good signals shorten diagnosis and reduce guesswork.

How to check

Ask for a sample incident view during the demo. Verify whether it can display logs and metrics tied to a specific deployment and whether you can filter by service/environment to reach the source of the problem.

Provisioning state and drift handling

Why it matters

Provisioning state and drift handling determine whether the platform can keep reality aligned with the declared desired setup. For cloud application infrastructure, drift leads to inconsistent behavior and costly rework.

How to check

Ask the platform to show how it tracks desired state versus actual state. Then simulate a manual change to a resource (if possible) and confirm whether the product detects drift and supports reconciliation with an explicit action.

Red flags

  • Rollbacks are manual or unclear during the deployment workflow.
  • Secrets or config changes bypass versioning or audit trails.
  • Audit logs don’t clearly show actor and target resource for key actions.

Fit by situation

  • If you regularly ship configuration and code changes between environments, prioritize Deployment workflow controls.
  • If multiple teams manage infrastructure and need clear permissions, prioritize RBAC and audit logging.
  • If you expect frequent changes and want repeatable environments, prioritize Provisioning state and drift handling.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

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 Listing

WHAT 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.