Operators of buildings that house, power and cool other companies' servers. It has no schema of its own: companies here are mapped on the Cloud, data centre and data platform providers schema, and what it does not cover is recorded as gaps.
© 2026 System Atlas · Built by MIOSA
Free to map your own company · Members $300 a yearHow automatable each primitive is, estimated from the 0 organizations mapped in public on the Cloud, data centre and data platform providers schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.
| Primitive | Layer | Automation | Peers on software | Software parts named most |
|---|---|---|---|---|
Lead generation Demand: winning customers | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Proposals and quoting Demand: winning customers | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Service catalogue Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Planning and scheduling Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Hardware and power purchasing Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Service operations Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Quality control Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Fleet and estate Supply: making or delivering the offer | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Logistics and fulfilment Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Capacity planning Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Cooling and facility operations Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Regions and availability zones Supply: making or delivering the offer | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Uptime and incident response Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Hardware lifecycle Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Account and workload onboarding Customers: keeping them | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Accounts and usage records Customers: keeping them | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Retention and renewal Customers: keeping them | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Billing and invoicing Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Collections and receivables Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Payments and payables Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Payroll Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Cash and treasury Money: getting paid and paying | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Hiring People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Onboarding and training People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Scheduling and capacity People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Reporting and dashboards Systems: tools and data | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Data management Systems: tools and data | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Legal and contracts administration Control: rules the company runs under | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Management cadence Direction: deciding where it goes | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Learning and improvement Direction: deciding where it goes | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.
Counts of what public research has found and sourced, each part with its source on the organization’s profile. They say what is known, not how much of the industry exists.
Focused research on the organizations with the fewest mapped parts in data centre operators and colocation; what it finds is public for everyone.