Cloud computing costs under Section 174: dev is SRE, prod is not

Cloud spend splits along one line: compute that supports software development is a Section 174 SRE expenditure, and compute that runs released software for customers is an ordinary operating expense deductible under Section 162. IRS guidance in the capitalization era (Notice 2023-63) said so expressly — costs of computers and hardware, "including... an amount paid or incurred to another party for the right to use computers" for software development, are SRE costs — and the principle carries into Section 174A, which changed the recovery of domestic SRE costs, not their definition. The statute is at 26 U.S.C. §174.

Which environments fall on which side

SRE side. Development environments; automated test and QA environments; staging and pre-release environments used to validate builds; CI/CD pipeline compute; sandboxes for prototyping; training runs and experiment compute for models under development; and the development share of shared services (source control, artifact registries, observability on dev clusters). These costs are incident to the development activity and follow it — including into the 15-year foreign pool when the development team they support is offshore.

Operating side. Production environments serving customers; disaster-recovery replicas of production; production monitoring and logging; content delivery; and compute behind customer support. Running released software is not developing it — the same boundary that keeps maintenance labor out of the SRE pool.

The genuinely mixed. A production environment that also hosts A/B tests of features under development, or "canary" infrastructure, can be split by any reasonable, consistently applied allocation — usage metering or resource tagging beats a flat percentage. Under a 60-month election, an inflated SRE share defers your own deductions; with foreign teams, it inflates the 15-year pool. The general allocation standards are covered in cost allocation methods.

Does the classification still matter under expensing?

For a purely domestic company expensing under Section 174A, dev and prod cloud spend are both currently deductible and the split is bookkeeping. It keeps real cash consequences in four situations: foreign development teams (their supporting cloud spend amortizes over 15 years); a 60-month capitalization election; states that have not conformed to expensing and still require addback (see state conformity); and the open 2022–2024 years, where treating dev-environment spend as a current expense understated the capitalized pool — and, later, the catch-up deduction under the transition rules. Reclassification across those years is an accounting-method question, generally fixed prospectively via Form 3115 rather than amended returns.

One caution against over-inclusion: cloud spend is an SRE cost because it supports research activity, not because engineers touch it. Corporate IT workloads — email, HR systems, the data warehouse serving finance — are neither dev nor prod product infrastructure, and belong in neither analysis.