Templus and SWI Group have announced an agreement to deploy 13 MW of AI infrastructure in Spain. For engineers evaluating European AI capacity, the important next step is understanding what that figure will become at the service boundary.
In its October 26 announcement, SWI describes infrastructure intended for high-density AI workloads. The release does not identify the site, define whether 13 MW measures utility demand or IT capacity, or give a commissioning date. It also refers to a leading AI platform without naming it.
This is an announced deployment agreement. The release provides no measured operating results or evidence that the full capacity is serving customers.
A deployment announcement within a broader compute launch
A separate SWI release published the same day announced SWI Compute, following its appearance at NVIDIA GTC Berlin the previous week. The group says the business is backed by 3.6 GW of power capacity across Europe and the US and has ordered approximately $1 billion of NVIDIA systems.
Those are company-reported portfolio and procurement figures. They do not specify the equipment allocation or delivery status for the Spanish agreement. Buyers should keep the project announcement and the wider platform launch distinct when assessing available capacity.
Analysis: define the unit being purchased
A megawatt figure can help describe project scale. A customer, however, needs a specification that connects the facility to a usable computing service.
For a colocation arrangement, that means identifying the electrical measurement boundary, the allocation available to the customer's racks and the responsibilities for cooling. For a managed compute service, it also means defining the accelerator configuration, network access, storage behavior and software environment included in the offer.
These are different products. Before comparing prices or reserving capacity, ask which one is being offered and which party accepts responsibility when the expected service cannot be delivered.
The Spanish announcement creates a useful point at which to request that definition. Its high-density description should lead to a technical schedule explaining the supported operating envelope, including cooling interfaces and any restrictions on workload deployment. The published release does not supply that schedule.
Connect the delivery plan to acceptance evidence
A procurement team could structure its review around the handover between facility readiness and workload readiness.
Ask the provider to identify the evidence required for each milestone. Electrical and cooling systems may be ready for equipment installation before the complete cluster is ready for customer use. The contract should explain which state triggers billing, what remains outstanding and how a customer can verify completion.
A useful acceptance plan would include a representative workload with an agreed dataset, software version and success criteria. Record how the test handles network or storage constraints, rather than treating the presence of accelerators as proof of service performance. This is a suggested purchasing control, not a test procedure disclosed by Templus or SWI.
For phased delivery, repeat that discipline at each handover. Make the capacity available in each phase explicit, together with dependencies on later construction or equipment deliveries. A portfolio total should not substitute for the delivery schedule of the service being purchased.
Make jurisdiction and recovery operational questions
The Spanish release presents sovereign AI capabilities as an intended benefit. Buyers should translate that description into specific requirements before treating it as an assurance.
Ask where customer data, backups and operational logs will be held. Establish who can administer the environment, how privileged access is authorized and what happens when a support escalation requires another organization. The answers should cover routine operation and recovery, because an emergency access procedure can matter as much as the normal hosting location.
Then examine portability. Define how a customer retrieves data, configuration and workload artifacts if a phase slips or the service no longer meets its needs. A regional deployment becomes more useful when its operating responsibilities and exit path are understandable.
The agreement adds a concrete Spanish deployment target to SWI's broader AI infrastructure strategy. The next evidence worth watching is project-specific: a defined capacity boundary, delivery milestones and an acceptance specification that connects the announced megawatts to the service customers can actually use.
Top comments (0)