Your cloud bill has a way of growing faster than your revenue. One month it is a line item; a few quarters later it is a board-level conversation. You are not alone: in Flexera's 2025 State of the Cloud Report, respondents estimated that 27% of their cloud spend was wasted, 84% called managing cloud spend a challenge, and respondents reported roughly a fifth of workloads and data already repatriated out of the public cloud. The software company 37signals famously acted on the same frustration, replacing about $3.2 million in annual cloud spend with roughly $600,000 of its own servers and reporting savings near $2 million a year. Dropbox's earlier exit from public cloud saved it about $75 million over two years, by its own S-1 account.
So the math can work. But most teams model the move as a swap of one monthly bill for a smaller one, and that misses the real finance story. Moving from managed cloud to owned hardware in a colocation rack converts operating expense into capital expense. Your cash timing, your profit and loss, your tax return, and your bookkeeping all change shape. Get the accounting right and the tax code subsidizes a big share of the move. Get it wrong and you expense things you should capitalize, miss elections you cannot take retroactively, and discover a surprise sales-tax bill on the hardware.
Here is how to think through the switch like an owner, not just an engineer.
Why Repatriation Is Back on the Table
The public cloud is priced for elasticity: instant scaling up and down, billed by the drink. That is a bargain for spiky workloads and an expensive way to rent capacity you use flat-out, month after month. For steady, predictable workloads, owned or colocated hardware frequently wins on total cost. An Andreessen Horowitz analysis of the "cost of cloud" paradox argued that at scale, repatriated workloads can run at roughly one-third to one-half the cost of their public-cloud equivalents.
Two important qualifiers before you start pricing racks. First, almost nobody leaves entirely. IDC research consistently finds that only about 8 to 9 percent of organizations pursue full-scale repatriation; the real trend is selective, with steady-state workloads moving to owned hardware while spiky or experimental workloads stay in the cloud. Second, the savings cases you read about come from companies with constant, high-utilization footprints. If your usage swings wildly or you are pre-product-market fit, elasticity is still worth the premium.
The planning question is therefore not "cloud or colo" but "which workloads belong where" — and what each answer does to your books.
What Opex-to-Capex Actually Means for Your Books
Today, your cloud spend is beautifully simple accounting: every invoice is an ordinary operating expense, deducted as incurred. Cash out and expense recognition move in lockstep, and there is nothing to track on the balance sheet.
Owned hardware breaks that simplicity three ways:
- Cash timing changes. You pay for years of capacity up front instead of renting it monthly. A $40,000 server purchase hits your bank account in week one.
- Expense timing changes. For books and usually for tax, that $40,000 is not a $40,000 expense. It becomes a fixed asset, and the cost reaches your profit and loss gradually through depreciation.
- Tracking burden changes. Every asset needs an in-service date, a cost basis, a depreciation method, and eventually a retirement entry. Cloud bills need none of that.
This mismatch surprises owners twice: first when year-one profit looks worse than the cash story suggests (big cash out, small depreciation expense), and again at refresh time, when a rack of fully depreciated servers still runs fine but nobody recorded what anything originally cost. Both surprises are preventable with the setup described below.
Your New Depreciation Schedule, Piece by Piece
Servers and network gear are 5-year property
Under the Modified Accelerated Cost Recovery System (MACRS), computers, servers, switches, and related peripheral equipment are 5-year property. In plain terms: the IRS expects you to spread the deduction over six tax years (the half-year convention puts half a year's depreciation in year one and the tail in year six), not to write the whole rack off on purchase day.
That default schedule is only the starting point, because two much faster options are available for most small businesses.
Section 179: expense up to $2.5 million in year one
Section 179 lets you elect to expense qualifying equipment immediately instead of depreciating it. Under current law the limit is $2.5 million of equipment placed in service per year, with the benefit phasing out once you place more than $4 million in service (both figures indexed for inflation). A single rack of servers falls laughably far below those ceilings, so for most readers the practical answer is: you can deduct the full hardware cost in year one if you want to.
Three catches to know. First, Section 179 cannot create or increase a tax loss; your deduction is capped at your taxable income from the business, though unused amounts carry forward. Second, you must affirmatively elect it on Form 4562 — it is not automatic. Third, if the equipment's business use drops to 50% or less within its recovery period, part of the benefit is recaptured as income. For dedicated production servers that last risk is remote, but document business use anyway.
100% bonus depreciation is back
For qualifying property acquired after January 19, 2025, 100% bonus depreciation is available again, letting you deduct the full cost in the placed-in-service year. Unlike Section 179, bonus depreciation has no taxable-income cap, so it works even in a loss year, and it applies automatically unless you elect out by asset class.
For a straightforward server purchase, Section 179 and bonus depreciation often reach the same destination — a full year-one deduction — by different roads. The differences matter at the edges: bonus covers used equipment too (with conditions), has no annual dollar ceiling, and interacts differently with state returns. Model both with your CPA before filing, because several states decouple from federal bonus depreciation and will make you add part of it back on the state return.
The small stuff: the $2,500 de minimis safe harbor
Cables, rails, small switches, and sub-$2,500 items do not each need their own depreciation schedule. The de minimis safe harbor lets you expense items costing $2,500 or less per invoice ($5,000 if you have audited financial statements), provided you have a written expensing policy in place at the start of the year and attach the annual election to your return. Set the policy up before you start buying, and the miscellaneous hardware just flows through as supplies.
What Stays Ordinary Expense
Not everything about the move gets capitalized. Your colo arrangement itself remains reassuringly opex-like:
- Rack space, power, and bandwidth billed monthly are ordinary operating expenses, just like rent and utilities.
- Cross-connects, IP transit, and remote-hands fees are services consumed as delivered — expense as incurred.
- Hardware warranties and support contracts are generally expensed over their term, not added to the asset.
- Egress and migration costs — the fees to pull data out of the cloud, the consultants who help you move, the weeks of running both environments in parallel — are current expenses, not part of any asset's basis.
One GAAP wrinkle for accrual-basis businesses: a colocation contract can contain an embedded lease under ASC 842 if it conveys control of specific space or capacity. That does not change your tax return, but it can put a right-of-use asset and a lease liability on a GAAP balance sheet. If you produce GAAP financials for lenders or investors, have your accountant run the embedded-lease analysis on the colo agreement rather than assuming it is all service expense.
What Goes Into the Asset's Basis (and What Does Not)
The number you depreciate — the asset's basis — is more than the server's sticker price. Capitalize the costs of getting the asset to its intended use: the purchase price, freight and delivery, sales tax, installation labor, and the initial configuration that makes it production-ready. Costs of merely evaluating the move — the planning study, the vendor bake-off, the trip to tour the data center — are expensed. Training your team on the new environment is expensed. Data migration labor is expensed.
This distinction is where repatriation projects quietly leak tax benefits in both directions. Some owners expense the entire hardware purchase and understate assets; others capitalize weeks of planning and migration consulting that should have been deducted immediately, deferring deductions they could have taken now. Sort every migration invoice into one of two piles — "part of the asset" or "expense of the period" — before it hits the books, and the depreciation schedule builds itself correctly.
A symmetry worth noting for the cloud side you are leaving: under ASC 350-40, certain implementation costs for cloud arrangements that are service contracts are capitalized and amortized over the arrangement term rather than expensed immediately. Moving in either direction involves capitalization judgment calls; document yours.
The Sales-Tax Surprise on the Hardware
Cloud services and physical servers are taxed under completely different regimes, and the difference bites. Servers you buy for your own use are taxable purchases of tangible property in most states, so add 6 to 10 percent to the hardware quote for sales or use tax unless you have verified otherwise.
You may have read that states hand out data-center sales-tax exemptions. They do — but those programs are built for hyperscale builds, not for a rack or two. Minnesota requires at least 25,000 square feet and $30 million of investment; Pennsylvania's program contemplates $25 to $50 million plus a $1 million payroll; Texas sets the bar around $200 million; Kansas at $250 million. A small business furnishing a colo cage will not clear any of those thresholds. Budget the sales tax, capitalize it into the asset's basis, and move on.
Five Mistakes That Blow Up the Tax Math
1. Expensing the whole purchase. The most common error. Without a Section 179 or bonus claim on Form 4562, a $40,000 server order is not a $40,000 deduction — it is a 5-year asset. The fix is an election, not a journal entry.
2. Forgetting the add-ons to basis. Freight, installation, and sales tax belong in the depreciable basis. Leaving them out permanently forfeits part of your deduction (or your Section 179 claim).
3. Missing the elections. Section 179 must be elected; the de minimis safe harbor requires both a written policy at the start of the year and an annual election statement. Elections you skip cannot be reconstructed at audit time.
4. Ignoring state decoupling. Your federal return and your state return may tell different stories. Several states limit or disallow bonus depreciation, which means tracking a separate state depreciation schedule. Ask about your state before you assume the federal answer carries over.
5. Running without an asset register. No list of what you own, when it went into service, and what basis remains means every refresh, disposal, and audit becomes archaeology. A server retired early with remaining basis generates a loss you can only claim if you know the basis.
A Bookkeeping Setup That Survives the Move
The unglamorous backbone of the whole project is a fixed-asset register — one row per asset with description, serial number, location (which rack, which facility), in-service date, total capitalized basis, depreciation method, elections claimed, and accumulated depreciation. Update it the day each server goes live, not at year-end.
In the chart of accounts, give the move its own geography: a Computer Equipment fixed-asset account with an Accumulated Depreciation contra account, plus distinct expense accounts for colo fees, cloud services, bandwidth, and hardware maintenance. When the P&L shows cloud spend falling as colo fees and depreciation rise, you can see the trade working — and at renewal time you can price the refresh against three years of actuals instead of guesses.
Reconcile monthly: new assets added, depreciation expense posted, disposals removed with any gain or loss recognized. And keep a refresh reserve in your planning — budget for a three-to-five-year replacement cycle even if the current gear hums along, because the next capex hit should never be a surprise. If you keep your books in plain text, the asset register can live alongside the ledger under version control, so every basis adjustment has a history; the documentation shows how others structure theirs.
Run the total-cost comparison over at least three years: hardware plus colo plus power plus bandwidth plus the staff time to rack, patch, and monitor, minus the tax shield from depreciation or immediate expensing, versus the projected cloud run-rate including egress. Do that honestly, workload by workload, and whatever answer comes out is one your books can support.
Simplify Your Infrastructure Bookkeeping
As you trade a cloud bill for racks, assets, and depreciation schedules, keeping clean fixed-asset records is what turns the move into real savings instead of a tax-season scramble. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready — your asset register and your ledger in one auditable place. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
