Types of data centers

Reading order

Read a Swedish hall file as a set of dimensions before you reach for a type noun. Write who owns the servers, who owns and operates the building, and whether several customers share the white space. Then write whether the public product is a cloud region, a retail colo contract, an owner-occupied campus, or a development still buying land. Only then ask whether high-density or AI language is a design envelope, an installed kit list, or a slogan.

Keep geography and power in their own cells. A hall in SE1 Luleå, SE2 Sundsvall, SE3 Stockholm or SE4 Malmö sits in a bidding area that shows transmission constraints in the wholesale price. That area is not a type. A megawatt figure is not a type either until you know whether it is IT, facility, site, utility or unclear. If the file mixes two patterns, record both. DataCenterSweden does not force a single exclusive type field that would mislabel mixed campuses.

• Who owns the IT load.
• Who operates the building.
• Whether retail customers share the hall.
• Whether the public cloud region is the product.
• Whether the design target is high-density compute.

How Swedish files treat type language

Swedish planning and environmental files do not grant a commercial type. A municipal detaljplan, read through Boverket’s Planning and Building Act guidance, regulates land use and building rights. It does not certify that a building is colocation, hyperscale or an AI factory. A building permit is a later municipal paper. Neither paper answers the network owner. The owner cares about load, voltage and the connection point. Svenska kraftnät enters only at transmission scale, and the indicative capacity map is still not a type stamp.

Hyperscale, in ordinary industry use, describes an owner-operated campus at large scale. Colocation describes a hall where several customers place equipment. A cloud region is a commercial product with availability zones; it may sit on owner-occupied halls, leased halls, or a mix that the operator does not pin to municipalities. HPC and AI describe workload and density more than they describe a landlord model. Edge describes a location and latency pattern, not a voltage class. One Swedish campus can carry more than one of those patterns over time.

National energy mix and local connection remain separate from type. Energimyndigheten’s description of the Swedish electricity system is useful context. A hydropower-rich national picture does not tell you whether a colo hall in Falkenberg or a cloud hall in Staffanstorp can connect next year. Skatteverket’s energy-tax rules follow activity and statutory conditions, not a marketing type. Inspektionen för strategiska produkter screens certain investments on activity and investor facts, not on whether a press release said hyperscale.

Retail colo, wholesale colo and build-to-suit are commercial wrappers around the same physical questions: power, cooling, fiber and neighbours. Calling a development modular or prefabricated does not shorten Boverket’s procedure or Naturvårdsverket’s environmental path. Calling it edge does not create spare megawatts in SE4. The type word is a starting index. The establishment file is still land, grid, plan, environment and a dated capacity cell.

What named primary sources show

Amazon Web Services said AWS Europe (Stockholm) opened on 12 December 2018, with three Availability Zones in Sweden. The cited launch pages do not publish municipalities and do not state facility megawatts. The region is therefore a documented cloud product without a municipal pin in this register. Treating the API name eu-north-1 as three separately counted campuses would invent a geography the operator did not print.

Microsoft said the Sweden datacenter region opened on 16 November 2021, with Azure and Microsoft 365 described as available, and named Gävle, Sandviken and Staffanstorp. Facility megawatts are not in the cited materials. Those three municipalities are three geographies, not one campus total. Later community PDFs still name the same municipalities and discuss local projects as company materials. They are not a type certificate and not a capacity disclosure.

Bahnhof describes Pionen as a colocation hall under Vita bergen on Södermalm, a converted civil-defence shelter. Capacity is not stated on the cited pages. That is an inner-city retail-colo pattern, not a hyperscale campus. Conapto said Stockholm 4 South opened on 5 September 2024 and that, together with Stockholm 2 South, the campus offered 5,200 square metres of computer rooms and 24 MW of power. A Stockholm 2 South sheet states 4 MW for five rooms; that phase figure is stored separately and is not added on top of the campus figure.

EcoDataCenter’s Falun site page markets the campus and states 80 MW available power. The 2025 annual report says buildings C and D were commissioned and that site capacity increased from 29 MW to 41 MW as of the balance-sheet date, and that once E and F are operational the campus total will amount to 65 MW. Those sentences are separate rows and are not added together. The same operator also markets Falun for HPC and AI. evroc’s 3 February 2025 notice is a land and building-rights purchase in Arlandastad with a design of up to 16,000 GPUs and no megawatt figure.

Common misreads

The most expensive misread is to treat type as a substitute for capacity. A cloud-region opening proves that a commercial product exists on a date. It does not prove municipal locations, hall megawatts, or that three availability zones are three campuses you may add. A colo brand proves a business model. It does not prove spare IT load. An HPC marketing line on a Falun page does not convert the 41 MW, 65 MW and 80 MW sentences into one larger number.

A second misread is to treat geography as type. Luleå is in SE1 and Staffanstorp is in SE4. That tells you which wholesale price area applies. It does not tell you that northern halls are hyperscale and southern halls are edge. A third misread is to treat a land purchase as a commissioned type. evroc’s GPU design envelope is a design claim. Commissioning is not documented in the cited notice.

• Using one exclusive label for a mixed campus.
• Adding EcoDataCenter’s 41 MW, 65 MW and 80 MW sentences.
• Treating AWS availability zones as three municipal campuses.
• Reading a GPU design envelope as commissioned megawatts.
• Using a bidding area as a hall type.

What to ask next

Ask the operator or the file which pattern is contracted today, not which word appears in a headline. If the product is a cloud region, ask which municipalities are published and which remain unpublished. If the product is retail colo, ask how much of the stated power is commissioned white space versus a campus envelope. If the product is owner-occupied, ask whether any MW figure is IT load, facility load, or unexplained.

Then move sideways. The AI and HPC page tests density and GPU language. The cooling page tests water and heat rejection. The capacity methodology page tests whether two megawatt cells may be compared. The municipal planning pages test whether the detaljplan actually allows the use you just named. Type language that cannot survive those questions is a slogan, not a classification you can store.

• Which pattern is contracted, and on which date?
• Is every MW figure labelled IT, facility, site, utility, or unclear?
• Which municipalities did the operator actually name?
• Is HPC or AI a design target, an installed kit, or a marketing line?
• Which other Swedish paper — plan, grid, environment — still has an empty cell?

What this does and does not prove

This page proves that Swedish halls in the reviewed set already show mixed patterns, and that exclusive type lists will mislabel them. It proves that AWS published a region without municipalities, that Microsoft named three municipalities without facility megawatts, that Bahnhof published an inner-city colo without a MW figure, and that EcoDataCenter published several Falun megawatt sentences that must stay un-added.

It does not prove a national census of hall types. It does not prove that colocation is smaller than hyperscale in Sweden, or that AI is a separate building class. It does not allocate spare megawatts by type. It does not turn a land-purchase notice into an operating cloud region. Empty type cells stay empty. Unknown capacity stays unknown and points back to the named source gap.

Use the page as a classification method. If a later primary source names a municipality, a megawatt boundary, or a contracted workload, store that as a dated row. Do not retrofit the older launch page to invent a type that the operator did not print. The method is the proof. The slogan is not, and an empty type cell stays empty until a dated source fills it.