NanoAvionics combines standard spacecraft platforms with constellation orders and operations partnerships. Its named programmes show several distinct routes for payload and component suppliers.
Kongsberg NanoAvionics supplies the spacecraft platform beneath a customer's satellite mission and can also take responsibility for integration and continuing operations. That combination makes it relevant to payload developers, research organisations and constellation businesses with very different purchasing needs. Its 2026 partnerships add further choices about who provides communications and who operates the mission after launch.
The company's Lithuanian origins remain central to its identity, but its commercial scope now sits within the larger Kongsberg organisation. A supplier assessment should follow the particular legal entity and deliverable, rather than combine parent-group resources, individual satellite orders and service partnerships into one undifferentiated measure of scale.
NanoAvionics' current corporate page identifies Kongsberg NanoAvionics UAB in Vilnius, company 303353414, and names Kongsberg Defence & Aerospace as its parent. It also lists US and UK entities and Lithuanian engineering and mission-control locations. Atle Wøllo is identified as CEO. This is a multinational operating structure with a Lithuanian spacecraft-development centre.
The page reports 220-plus qualified engineers, which is a company-reported engineering population rather than a dated total employee count. It also presents cumulative satellite and customer measures. This profile does not turn those promotional counters into annual production, staffing or revenue figures. Comparable standalone annual revenue and total employees remain unreported in the primary material used here.
Kongsberg's group-company list labelled April 2026 gives its NanoAvionics UAB stake as 98.82%. That dated disclosure supports a controlled-subsidiary description. It should not be silently replaced by the minority-retention percentages in older acquisition announcements or presented as a freshly checked September share register.
For a customer, the practical distinction concerns responsibility. A Lithuanian bus supplier, a US subsidiary and a wider Kongsberg service team may contribute to the same programme while undertaking different obligations. The order should identify which entity supplies the spacecraft, which owns the relevant service commitment and how the parties manage changes across those boundaries.
The satellite-bus catalogue lists 6U, 8U, 12U and 16U CubeSat platforms alongside the MP42D, MP42 and MP42H microsatellite families. Light, Mid and Max configurations provide different starting points within those families. Standardisation therefore describes an organised product range, rather than a single identical spacecraft supplied for every payload.
A hypothetical atmospheric-instrument developer might begin by asking whether a standard platform can accommodate its instrument and the information service it intends to deliver. The proposal needs to separate standard platform content from instrument-specific integration. A constellation customer adds another question: which elements can remain unchanged across successive spacecraft and which require individual work.
That separation is commercially important because recurring manufacture and initial integration have different cost structures. A low unit price means little if every satellite requires substantial new engineering. Conversely, a more developed initial package may reduce repeated work later. The useful comparison concerns the complete programme and its acceptance milestones, rather than the smallest platform label.
NanoAvionics' mission-services description includes launch procurement and integration, documentation and logistics, and satellite ground operations. It describes its own mission-control software and connections to commercial ground-station networks. These are distinct services that can accompany a bus purchase.
For a research organisation, outsourcing them can change the size and responsibilities of the internal project team. The customer can concentrate on the instrument and scientific result while buying a defined spacecraft and operations package. A company that already operates satellites may want a narrower arrangement and retain more activities itself.
The proposal should therefore connect each handover to a deliverable: accepted spacecraft, completed launch integration, initial contact, commissioned platform and continuing service. These stages have different meanings. A spacecraft that has established communications has passed a valuable milestone, but the customer may still be waiting for the evidence required to accept its instrument or data product.
The 31 March 2026 FlyLab announcement reports two-way communications with two satellites built for the French aerospace research organisation ONERA after their 30 March launch. It identifies FlyLab-1 as an 8U spacecraft and FlyLab-2 as 6U, with different research payloads. Both were entering commissioning at the time of that release.
This is a useful example of two related spacecraft supporting one research programme without being identical products. The supplier relationship combines platform manufacture with the customer's distinct instrument objectives. The release's launch and initial-contact evidence should remain separate from later scientific results or completion of the planned experiments.
A prospective payload company can use that distinction when shaping its own enquiry. It should explain the instrument's required output and the evidence needed at handover, rather than request a generic satellite similar to a named research mission. SATLANTIS' payload-centred business offers a complementary view of how the payload and platform sides of an imaging programme can occupy different commercial roles.
Kongsberg's 3 April 2025 SpinLaunch contract announcement describes a €122.5 million agreement for 280 microsatellites and a partnership including two prototypes and serial-production development. It also says Kongsberg Defence & Aerospace took a minority investment in SpinLaunch. The customer relationship and the investment are separate transactions with different commercial effects.
This programme is particularly relevant to component suppliers because it links development work to a larger intended production run. Repeatability, documentation and the ability to support controlled changes become commercially important alongside the first delivered component. The MDA–Airbus repeat-antenna order illustrates the separate evidence value of a follow-on order in an established constellation supply chain.
A current Kongsberg Meridian update says the initial customer-link mission is progressing toward an October 2026 launch. That remains a future programme milestone at this review. The same update describes a broader government-communications offering, which should not be counted as an additional disclosed order for every prospective constellation.
The 18 March 2026 Flexell Space agreement illustrates a different route. NanoAvionics is to design and manufacture solar arrays for Hanwha Systems satellites, while Flexell performs final quality inspection and acceptance testing for the Korean customer requirements. The companies describe a multimillion-euro contract without publishing an exact value.
Here, NanoAvionics supplies a defined subsystem rather than the complete spacecraft. The named division of manufacturing and acceptance work matters to another component business considering an international partner: local customer access and final verification can form a distinct contribution alongside the hardware itself.
The 15 April 2026 KSAT partnership combines NanoAvionics platforms with ground connectivity, mission operations and data delivery. The companies say KSAT already operates several NanoAvionics customer satellites. This relationship concerns the continuing operational service around the spacecraft, including the people and infrastructure needed after launch.
A customer evaluating that package can compare the outsourced service with the cost of maintaining its own operations organisation. It needs a clear service boundary and reporting arrangement for the mission it actually buys. The partnership announcement supplies the commercial direction; the proposed mission agreement supplies the particular coverage and responsibilities.
The 17 February 2026 Kepler agreement concerns optical connectivity and hosted-payload opportunities. It describes a non-exclusive preferred European bus relationship and optional access to Kepler's relay and computing services. Later higher-capacity access is expressly subject to availability and agreed commercial terms.
These are complementary commercial choices rather than interchangeable guarantees. A customer might need a manufactured bus, a managed mission, an optical-network service or a combination. NanoAvionics' value proposition is the ability to assemble that programme around a defined payload and customer outcome. Understanding the separate contracts and milestones makes its expanding offer easier to evaluate and gives industrial partners a precise place to contribute.
Primary sources reviewed 7 September 2026. Ownership percentage retains the parent list’s April 2026 date; engineering counter is not total staffing. Future Meridian launch and optional network capacity remain prospective.
Suggest a correction