Saab’s October 2025 Giraffe 1X order provides a clear radar purchasing signal: a named product, the US Army as contracting customer, an approximate $46 million value and deliveries planned to begin in 2026. The source also identifies a security-cooperation purpose, meaning the contracting organisation and eventual users should not be treated as the same field.
For sensor companies and integrators, that detail is more useful than placing the award in an undifferentiated list of counter-drone deals. A radar purchase describes one equipment category. The broader customer solution may involve vehicles, software, training and support under arrangements that need their own evidence.
French and UK records for the same radar family make the commercial distinction easier to see. They show different combinations of hardware, integration and lifecycle services without establishing that those scopes apply to the US order.
The US order establishes a bounded supplier relationship
In its 28 October 2025 announcement, Saab said the Army awarded Saab, Inc. a contract worth approximately $46 million to provide Giraffe 1X radars in support of security-cooperation partners. It reported booking the order in the third quarter of 2025 and expected deliveries to start during 2026.
Those dates describe different stages. The quarter identifies when the supplier recorded the order. The October date identifies its public announcement. The delivery statement supplies a planned starting period.
The release does not identify all recipients, a unit quantity or a per-radar price. It therefore supports a customer and product relationship without providing the inputs for a unit-cost comparison.
For a commercial tracker, the security-cooperation description should remain attached to the order. Recording it simply as equipment for US Army units would remove a material qualification supplied by the source itself.
A product family can support several purchasing contexts
Saab’s Giraffe 1X product page describes the radar as applicable to several surveillance and protection roles, including counter-UAS. That is the manufacturer’s account of the product family’s intended uses.
The range of described applications does not mean every customer order purchases the same configuration or supporting services. The commercial package depends on the particular buyer and agreement.
This is a useful point for smaller sensor businesses studying established competitors. A product family may recur across announcements while the route to market changes. In one case the radar supplier contracts with a government authority; in another it participates in a consortium or provides equipment for integration by another business.
The relevant comparison is therefore not only which radar appears in the announcement. It is which organisation selects the product, which company owns the wider delivery and what work the contract includes.
France supplies a named vehicle-integration example
On 18 May 2026, Saab described a joint contract with Scania France for the French procurement authority, DGA. The disclosed scope included 17 Giraffe 1X radars: one for test and evaluation and sixteen associated with Scania vehicles. Saab also named spares, training and support within the agreement.
The companies formed a consortium for the contract’s duration, with radar deliveries planned for 2026–2027. That is a more detailed industrial relationship than the US release provides.
The DGA’s own 18 May account described eight Varda systems ordered on 14 April 2026 following an initial eight ordered on 29 December 2025. It identified Giraffe 1X integrated with Scania vehicles and placed the acquisition within its rapid-acquisition approach.
DGA said it chose available equipment requiring limited changes because an immediately available French solution was absent. This adds a buyer-side explanation of the acquisition choice: availability and adaptation effort were explicit in the public rationale.
The different counts are understandable when the objects being counted remain explicit. The buyer described sixteen vehicle systems. Saab’s account additionally identified a radar for evaluation. An analyst should preserve that distinction instead of presenting the figures as contradictory or adding them into a new total.
The consortium changes the supplier conversation
The French record makes a partnership visible at the delivery level. The customer’s solution combines the radar business’s product with another manufacturer’s vehicle and supporting work.
For a company offering services into a comparable programme, that structure changes the potential customer map. The government remains the ultimate buyer, but a relevant commercial relationship may sit with the consortium or one of its members.
An illustrative integration-services supplier would need to establish which party owns the work it proposes to perform. An introduction to the radar manufacturer is useful only if that manufacturer has responsibility for the relevant part of the delivery. The public consortium announcement helps identify the organisations, while the detailed allocation of work remains a matter for the actual commercial discussion.
The example also shows why partner announcements deserve their own reporting. A named consortium reveals how companies are combining capabilities for a specific contract. That is distinct from a general memorandum expressing an intention to explore future collaboration.
UK records show support as a separately visible purchase
A UK Ministry of Defence award notice published in August 2022 described two Giraffe 1X radars and contractor logistic support. It recorded an award decision on 20 June 2022 and a value of £5,607,360 excluding VAT.
That historical notice is useful here because it explicitly combines equipment with support. It is not a current opportunity, and its value cannot be used as a price list for the later US or French purchases.
The inclusion of services changes how a contract amount should be interpreted. Dividing a package value by the number of radars would attribute all the associated support to the hardware. Even where a quantity is disclosed, the resulting figure may not describe the equipment’s unit price.
For a supplier assessing the market, support also creates a different time horizon from an initial shipment. The customer needs an arrangement for the product’s use over time. The public record can establish that such work was purchased without revealing its detailed staffing or commercial margin.
Keep buyer roles and product scope together
The Drone Coalition chronology provides another example in which an administering purchaser and an intended recipient occupy different positions. Its procurement arrangements differ from this radar order, but the comparison illustrates why a database needs both roles.
The same discipline applies to architecture. A radar order, a vehicle-integration agreement and a complete counter-drone system purchase cover different scopes. Grouping them under the same topic can help readers discover related coverage, while the article itself must retain the distinction.
Our SAPIENT analysis discusses the related question of interfaces and integration responsibility. It does not establish which standard or configuration is used by the US order.
The next evidence concerns execution of each agreement
The US announcement’s delivery schedule begins in 2026. Subsequent buyer or supplier reporting would be needed to establish what had actually shipped or been accepted. The French consortium has its own stated delivery period, and the UK notice supplies a separate historical support example.
Following each agreement independently produces a clearer view of the business. It allows a reader to see repeated use of a product family while understanding the different buyers, partners and services involved.
The Giraffe 1X story is therefore an example of how sensor demand appears through several commercial arrangements. Its usefulness comes from those specific relationships, rather than treating every radar headline as the purchase of an identical complete defense system.