Home / Engines / Deployment Cost & TCO

Registry-priced deployment cost & TCO

Standalone pricing for a composed node: module, drives, PoE switch, carrier and supply from the price registries. Camera lines use a representative planning assumption (class E) for the resolution class unless you override the unit price. Missing listings stay null — the hardware subtotal and TCO stay incomplete, never zero. Method: methodology. The same engine prices the Architecture Designer and Full Deployment Planner BOM rollups.

Method v1.2.5 · data verified 2026-09-29 · registries: module-prices, drive-prices, poe-switch-prices, carrier-prices, psu-prices, camera-class-prices, storage-host-prices, production-carriers · methodology

01 · Describe the deployment

Platform
Nodes
1
2
4
Cameras
2
4
8
16
Camera class
720p
1080p
4K
Drive (optional)
Drives / node (with a drive chosen)
PoE switch
Carrier
PSU rating key
System power (W)
Power scope
system_partial
system
Horizon (years)
Energy rate ($/kWh)
Duty (h/day)
Camera unit override ($)
Allowances (class E, opt-in)

03 · How this works

What is priced

Compute modules come from the module price registry — class C where a dated vendor or distributor listing exists, never class B, which is reserved for EdgeAIStack measurements. Drives, PoE switches, carriers, PSUs and storage hosts come from their own price registries under the same listing taxonomy. Cameras use resolution-class planning allowances (class E) unless you override the unit price. Quantities are yours: the engine prices the composition you describe and never re-picks hardware.

Incomplete, never zero

An unpriced line contributes nothing and makes the hardware total incomplete; it is never counted as zero. The TCO is still published as a lower bound with the missing lines named, and every null price or quantity says why in its note.

An undiscounted sum

TCO is capex (hardware plus opt-in allowances) plus the yearly operating cost times the horizon. No discount rate, financing, carbon, ROI, cloud comparison, certification or volume discount is applied — each is listed under exclusions because there is no defensible source.

Full rules, the completeness contract and what is excluded: methodology. Raw price registries: module-prices.json, drive-prices.json, poe-switch-prices.json, carrier-prices.json, psu-prices.json, storage-host-prices.json, camera-class-prices.json.

04 · FAQ

Why is a missing price null instead of zero?
Because zero would silently understate the total. An unpriced line contributes nothing to the hardware figure, the note on that line names the reason (no dated listing for the SKU, no supply sized for the platform, a quantity of zero), the hardware total is flagged incomplete, and the TCO is published as a lower bound with the missing lines listed rather than as a complete figure.
Is the TCO discounted?
No. TCO is an undiscounted sum: capex (hardware plus any opt-in capital allowances) plus the yearly operating cost multiplied by the horizon in years. No discount rate, financing, carbon, ROI, cloud comparison, certification or volume discount is applied; each is listed under exclusions because there is no defensible source for it.
Where do the prices come from, and how old are they?
Dated vendor or distributor listings in the price registries (class C) for compute modules, drives, PoE switches, carriers, PSUs and storage hosts; each priced line carries its listing and date, and the registries’ verified date is stamped on this page and in every result. Camera lines are resolution-class planning allowances (class E) unless you override the unit price. Developer-kit compute lines carry a production note when the BOM is built from dev-kit listings.
Do Architecture Designer and this page price the same way?
Yes. This engine is the site’s sole cost owner: Architecture Designer and Full Deployment Planner call it for the BOM, the cost total and the energy OPEX, and nothing is re-priced from legacy tables. The standalone inputs here map onto the same composed path the designer uses, so the same composition prices the same on both pages.