PXPXS RESEARCH
Public companyResearch currentFresh

Mercury Systems Inc

By Published by PXS Research Updated

Autonomy Platforms · Physical AI

SignalTRIMReviewed 26 Oct 2026
Current thesis

Autonomy Platforms exposure in Physical AI.

Mercury Systems is a merchant supplier of ruggedized, ITAR-controlled, DMEA-trusted embedded computing — Common Processing Architecture and OpenVPX boards, BuiltSECURE and BuiltSAFE mission processors, RF modules, and secure microelectronics. It sells almost entirely as a subcontractor to U.S. defense primes. The product is the mission-compute brain inside radar, electronic-warfare, counter-UAS, missile-defense, space, and effector programs — not a commercial server and not a prime platform. Demand is no longer the open question. After the fiscal 2026…

Catalysts

C-UAS record backlog conversion; DoD C-UAS/ISR awards; largest-ever Common Processing Architecture order (per Grok); defense electronics procurement acceleration

Invalidation

Historical execution issues recur; margin compression worsens; C-UAS program delays

Latest change

· Target moved from $115.72 to $115.14.

Capital in context

Mapped funds and investors

Direct relationships supported by published evidence.

Reported holdings as-of

No sourced relationships mapped yet.

Disclosed investment history

No sourced relationships mapped yet.

Showing up to four relationships in each group. ETF weights describe the fund’s portfolio, not ownership of this company. Private investment history does not establish current ownership.

Institutional positioning

ins-$30.5M · 13F 17+/8-×0.0 · short↑0.35

Current snapshot
Social sentiment reference

X: defense analysts mixed — C-UAS thesis strong but MRCY execution history is a recurring concern; turnaround gaining traction per recent order wins

Lower-confidence snapshot
Valuation reference

Target price: $104.47

Dated research target
Research rigor

Moat & position

Evidence Grade
Inferred
Moat Durability
Qualification barrier
Toll Road Tier
Strong proxy
Timestamped research update

Deep research update

7,887 words · Updated 21 Oct 2026 · 17 sources

Business

Mercury Systems makes ruggedized embedded computing systems for defense platforms — signal processing modules, avionics computers, radar processing electronics, electronic warfare subsystems. Sells to defense primes (Raytheon, L3Harris, Northrop, BAE Systems) who integrate into radar, EW, ISR, and C-UAS systems.

Mercury Systems manufactures ruggedized embedded computing systems (SBC/VPX modules) for defense primes (Raytheon, L3Harris, Northrop, BAE Systems). Modules provide signal processing for radar, electronic warfare, C-UAS systems, and avionics.

Mercury Systems Inc manufactures ruggedized embedded computing systems (Single Board Computers, VPX modules, signal processing subsystems) for defense primes. Core product: mission processing modules that provide signal fusion, radar processing, electronic warfare filtering, and sensor data processing for C-UAS systems, AESA radars, ISR platforms, and defense autonomy applications. Sells into Raytheon, L3Harris, Northrop Grumman, BAE Systems, and Lockheed integration chains.

Mercury Systems makes ruggedized, trusted, defense-qualified embedded computing — single-board computers (SBC), VPX/OpenVPX modules, signal-processing subsystems, and the Rugged Trusted BuiltSECURE (RTB) secure-server line. These are the "brains" of radar, electronic-warfare, missile-defense, C-UAS and ISR platforms. Sells to the defense primes (Raytheon/RTX, L3Harris, Northrop, BAE, Lockheed) as a merchant sub-tier supplier.

ParameterValueSource Confidence
FY25 revenue$912.0Mmeasured (10-K XBRL)
FY25 gross margin27.9%measured
FY25 GAAP op income-$19.6Mmeasured
FY25 net income-$37.9Mmeasured
FY26 Q3 revenue$235.8M (+11.5% YoY)measured (10-Q XBRL)
FY26 Q3 gross margin29.3%measured
FY26 Q3 GAAP op income+$5.2Mmeasured
FY26 Q3 net income-$2.9Mmeasured
Q3 bookings$348M (+74% YoY)derived (Q3 call)
Book-to-bill1.48xderived
Backlog (RPO)$859.8Mmeasured (10-Q XBRL)
Total backlog~$1.6B (+18% YoY)derived (Q3 call)
FY26 revenue guide$950–960Mderived (guidance)
Adj EBITDA margin guidemid-teens %derived (guidance)
Q4 FY26 earningsAug 18, 2026derived (IR/X)
FY25 R&D$67.6M (7.4% of rev)measured

Mercury Systems is a merchant supplier of ruggedized, trusted, defense-qualified embedded computing — Common Processing Architecture (CPA) / OpenVPX boards, BuiltSECURE / BuiltSAFE mission processors, RF/microwave modules, and secure microelectronics. It sells almost entirely as a subcontractor to U.S. defense primes (and, in some cases, directly to the U.S. government). The product is the mission-compute “brain” inside radar, EW, C-UAS, missile-defense, space, and effector programs — not a commercial server and not a prime platform.

See parameter table. Additional balance-sheet facts from EX-99.1: inventory $366.968M (37.3% of FY26 rev), goodwill $942.419M (40.6% of assets $2,322.776M), deferred revenues $149.565M. International operations were 2% of FY26 net revenues (vs 5% in FY25/FY24) as Swiss manufacturing moved to Cicor (asset sale closed 30 Apr 2025; 5-year exclusive EMS agreement). Geographic order-origination still shows Europe unaffiliated $39.3M.

  • monetization model: One-time hardware sales plus engineering/services; no subscription/SaaS disclosed (FY25 10-K Item 1; sec.gov ; acc. UNKNOWN).
  • revenue mix: Single reportable segment = 100% of revenue; product-line/customer % UNKNOWN from segment note (FY25 10-K segment/revenue note; acc. UNKNOWN). Streams include embedded processing, RF/microwave, secure mission systems, services.
  • who pays: U.S. DoD and defense prime contractors buying for government programs; allied international governments (FY25 10-K Business/customer concentration; acc. UNKNOWN).
  • margin_value_capture: Gross/operating margin UNKNOWN here; value accrues in qualified defense electronics hardware and services (FY25 10-K MD&A; acc. UNKNOWN).
  • customer classes: Government - Program Buyers, Space & ISR Program Buyers, Defense prime contractors (OEMs/integrators) (FY25 10-K Business/customer concentration; acc. UNKNOWN).

Mercury Systems monetizes by selling ruggedized, security-sensitive electronics and subsystems into defense and aerospace programs. In its Form 10-K, Mercury historically describes itself as operating as one reportable segment supplying open-architecture, high-performance sensor processing, mission computing, RF, secure storage, and display technologies. The company earns revenue from:

  • Product sales of embedded modules, subassemblies, and integrated subsystems.
  • Engineering and development work under defense contracts.
  • Support, repair, and lifecycle services tied to qualified hardware.

The economic model is closer to a defense electronics design-in plus program lifecycle model than a volume components model: Mercury gets designed into a program, qualifies its hardware, and then benefits from multiyear procurement, sustainment, and replenishment demand.

Mercury reports a single operating segment, so there is no clean segment-level revenue split. However, the 10-K and MD&A typically disclose revenue by customer type, contract type, and in some periods by product area. I would model the business this way based on the company’s disclosures, but the percentages require direct exhibit verification:

Revenue viewApproximate mixSource status
Reporting segment100% one segmentMerc 10-K, Item 1 / Segments note — needs primary source validation for exact reported language
Product vs. servicesProduct ~75–85%; services/development ~15–25%10-K MD&A — needs primary source validation
Contract type: fixed-price~80–90%10-K revenue-recognition note — needs primary source validation
Contract type: cost-reimbursable~10–15%10-K MD&A — needs primary source validation
Contract type: time-and-materials~1–3%10-K MD&A — needs primary source validation

The exact revenue mix varies year to year because development contracts and lower-margin fixed-price work can inflate or deflate recognized revenue.

Mercury’s monetization model is:

  1. Design-in — sell hardware that becomes embedded in a prime contractor’s radar, electronic-warfare, missile, C4I, or unmanned system.
  2. Qualification and production — follow the design-in with multiyear production orders.
  3. Sustainment — provide repairs, upgrades, and obsolescence management.

This is a lifecycle monetization model. The company receives revenue at each phase, but revenue recognition is often tied to performance obligations and contract milestones, especially for fixed-price development programs.

Mercury historically generated gross margins in the high-20s to low-30s percent range. The recent trend is not uniform:

MetricFY2024FY2023Source
Revenue$835.9M — needs primary source validation$973.9M — needs primary source validationMercury 10-K for FY2024, filed August 2024, EDGAR index: sec.gov (accessed 2025-05-20, accession not independently resolved)
Gross margin~26–27% — needs primary source validation~29–30% — needs primary source validationMercury 10-K MD&A, same source as above
Operating marginNegative due to restructuring, impairment, and execution charges — needs primary source validationNegative to slightly positive — needs primary source validationMercury 10-K MD&A, same source
Net incomeNet loss — exact loss needs primary source validationNet loss — exact loss needs primary source validationMercury 10-K, same source

The margin story is important: if Mercury’s gross margin is falling on lower revenue, fixed-price development work and program mismatches are eating the economics. That is not a typical high-quality defense prime profile; it is an execution problem.

The ultimate payer is often the U.S. Department of Defense, through prime contractors or directly. Intermediate payers are prime defense contractors that embed Mercury products into their systems. Mercury also sells to allied governments, intelligence-community customers, and to a lesser extent commercial aerospace or industrial customers where defense-grade ruggedization is required.

Do not treat this list as a formal customer-concentration table. The 10-K names major primes and defense customers in discussion of its markets and risks. Candidate names that appear in Mercury’s 10-K or investor disclosures include:

  • Lockheed Martin
  • Northrop Grumman
  • RTX / Raytheon
  • L3Harris Technologies
  • BAE Systems
  • General Dynamics
  • Boeing
  • U.S. Army
  • U.S. Navy
  • U.S. Air Force
  • Missile Defense Agency

The top-customer revenue concentration percentage requires the formal customer-concentration note in the 10-K. The company may report direct or indirect federal-government exposure. The exact percentage must be pulled from the filing and marked needs primary source validation if not independently retrieved.

Mercury sells to:

  1. U.S. Department of Defense agencies — Army, Navy, Air Force, Missile Defense Agency, and other defense organizations.
  2. U.S. intelligence and classified customers — secure storage and mission processing.
  3. Prime defense contractors — Lockheed Martin, Northrop Grumman, RTX, L3Harris, BAE Systems, General Dynamics, Boeing, and others.
  4. Allied international customers and foreign military sales — through prime contractors or direct sales.
  5. Space and missile system integrators — radiation-tolerant or rugged electronics.
  • Prime contractor program manager — wants merchant, open-architecture, qualified hardware that accelerates development and reduces program risk.
  • Government acquisition officer — wants supply-chain security, export control, cybersecurity, and program accountability.
  • System integrator or subsystem supplier — wants a qualified, repeatable hardware/software platform.
  • Sustainment and depot manager — wants long-term availability, repair, and obsolescence management.

The core buyer motivation is risk reduction in mission-critical systems, not lowest price. That supports incumbent stickiness.

Mercury Systems, Inc. (Nasdaq: MRCY) is a U.S. defense electronics supplier. Its public materials describe the company as a provider of mission-critical processing, embedded computing, secure communications, and sensor-processing products for aerospace and defense applications. This is a primary-source-level description from the company’s own product and investor materials, but it is not a financial claim.

Source:

Accessed 2026-04-26.

This matters because MRCY is not a broad industrial conglomerate or a commercial semiconductor company. It is a defense-focused embedded electronics firm whose revenue base depends heavily on U.S. defense budgeting, platform programs of record, and prime contractors.

Exact segment-level revenue mix cannot be verified in this session without retrieving the 10-K. Mercury has historically operated with a relatively consolidated reporting structure. A live verification question is whether Mercury reports:

  • a single operating segment, or
  • multiple segments such as products/services, or
  • disaggregated revenue by product line.

No exact percentage should be used in a conviction model until the 10-K disclosure is retrieved. The current value is: needs primary source validation.

Source to retrieve and verify:

  • Mercury Systems SEC EDGAR company directory:

sec.gov

Accessed 2026-04-26.

From the company’s own public product descriptions, MRCY’s offerings fall broadly into:

  • embedded processing modules and single-board computers,
  • rugged mission computers and display systems,
  • secure data storage and data-transfer products,
  • RF and microwave modules,
  • advanced microelectronics packaging,
  • software-defined signal processing solutions.

These are not financial claims, but they define the business model.

Source:

mrcy.com

Accessed 2026-04-26.

Mercury’s monetization is primarily hardware- and engineering-driven. It does not operate a SaaS-style recurring revenue model. The customer pays for:

  • development engineering and non-recurring engineering,
  • production hardware units,
  • aftermarket support, spares, and repair services.

The financial split between product revenue and service/engineering revenue must be taken from the 10-K. Exact percentages are needs primary source validation.

This is an important structural point for investors: MRCY’s revenue is lumpy, program-based, and dependent on defense procurement cycles. It is not a subscription business with predictable monthly recurring revenue.

MRCY’s gross margin and operating margin are central to any investment thesis. The company has faced public pressure from an activist investor and has undergone restructuring. Qualitatively, the market concern has been that:

  • gross margin has been under pressure from supply-chain costs, program mix, and fixed-price contracts,
  • operating margin has been pressured by elevated engineering costs and restructuring charges,
  • inflation and labor costs have affected profitability.

But specific gross margin and operating margin values are needs primary source validation.

Source to retrieve:

Mercury Systems 10-K and 10-Q filings via the SEC EDGAR directory above.

Do not build a conviction score on memory of “mid-30s gross margin” or “single-digit operating margin” without confirming the exact filing.

The paying customers are defense prime contractors and, directly in some cases, the U.S. government and allied governments. Mercury sells into platforms and programs where the ultimate funding source is government defense procurement.

This is structural, not a customer-name claim. Exact customer names and revenue concentrations are needs primary source validation.

I will not invent customer names. The SEC 10-K business section and revenue-concentration disclosures must be checked for exact named customers. Common industry participants such as Lockheed Martin, RTX, Northrop Grumman, BAE Systems, L3Harris, Boeing, and government agencies are plausible counterparties in this sector, but the claim that any specific one is a top MRCY customer is not asserted here without a filing source.

Top-customer claim status: needs primary source validation.

MRCY sells to:

  • U.S. Department of Defense program offices,
  • prime defense contractors,
  • allied governments and foreign military sales,
  • defense electronics manufacturers.

This is structural. Exact customer-class revenue splits are needs primary source validation.

The buyer is not a retail consumer. The relevant archetypes are:

  • Prime program manager: cares about schedule, compliance, technical performance, and price.
  • Government program executive officer: cares about mission capability, cost, and supply-chain security.
  • Engineering lead at a prime: cares about processor architecture, size, weight, power, and compatibility.
  • Logistics/sustainment buyer: cares about spares, support, and long-term availability.

No specific customer names are asserted here because live 10-K retrieval was not possible. The required approach is:

  1. Open the MRCY 10-K.
  2. Check Item 1 and the revenue-concentration footnote.
  3. Identify customers disclosed as material.
  4. Check the annual report’s discussion of major programs and prime contractors.

Until that retrieval occurs, all named-customer claims are needs primary source validation.

Revenue and scale

TTM revenue $967M; net income -$14.1M (slight loss); shares out 60.04M; market cap $6.84B. Company in execution transition post-CEO change (2024).

FY26 Q2 (ended Dec 2025): ~$250–260M revenue estimate from TTM burn (~$967M TTM / 4 = ~$240M/Q baseline); net income -$14.1M TTM (company at break-even / slight loss); fiscal year ends June (so FY26 ends June 2026, Q3 due ~Aug 2026). Analyst consensus $101.50 target (11% upside from $105 current, Jun 20 basis). Market cap $6.96B, inst_own 103.79% (overheld).

FY2025 (ended 06-27-2025): revenue $912.0M, gross margin 27.9%, GAAP operating loss -$19.6M, net loss -$37.9M (10-K XBRL). FY2026 Q3 (ended 03-27-2026): revenue $235.8M (+11.5% YoY), gross margin 29.3% (+140bps vs FY25 full-year; +230bps YoY per earnings call), GAAP operating income +$5.23M — first positive GAAP quarter, net loss narrowed to -$2.9M (from -$15.1M in Q2). FY26 guidance raised to ~$950–960M revenue and mid-teens adjusted EBITDA margin. Q4 FY26 earnings print scheduled Aug 18, 2026 (imminent binary catalyst).

FY2026 (53 weeks ended 03 Jul 2026): net revenues $983.622M vs FY2025 $912.020M (+7.85% headline; +5.82% extra-week-adjusted). Gross profit $281.165M → GM 28.58% (+68 bps vs FY25 27.90%). GAAP operating income +$0.280M (first full-year GAAP operating profit after FY25 -$19.627M). GAAP net loss -$29.673M (-$0.50/sh) vs -$37.904M. Q4 FY26 revenue $289.782M (+6.1% YoY vs $273.106M), GM 30.57%, GAAP operating income $14.465M (5.0% OM), GAAP NI $0.798M. Adj. EBITDA FY26 $150.192M (15.27%, +217 bps) / Q4 $48.518M (16.7%). R&D FY26 $59.736M (6.07% of revenue). Cash $214.306M, long-term debt $441.500M, net debt $227.2M (down 19.5% YoY after a $150M revolver paydown). All GAAP figures: 8-K EX-99.1 filed 2026-08-18 + 10-K XBRL CIK 0001049521.

Thesis connection

C-UAS systems (radar + EW + signal processing) require MRCY's ruggedized modules; every Sentinel radar, LTAMDS AESA, AN/TPY-2 uses custom signal processing compute that must be mission-qualified. MRCY supplies the "brain" layer of defense sensor electronics.

C-UAS systems (radar + EW + processing) require MRCY's qualified modules; $3.1B DoD C-UAS appropriation creates demand pull; 7-10 year qualification cycle = backlog visibility once won; MIL-SPEC qualification moat prevents easy switching.

$3.1B DoD C-UAS budget appropriation (FY26–FY28) drives procurement acceleration for radar and signal processing electronics. MRCY's modules are embedded in multiple defense primes' programs of record. MIL-SPEC qualification creates 7-10 year platform lock-in; switching suppliers requires complete system redesign.

The 08-16 note set four falsification tests for the Aug 18 print (Q4 rev < $235M; GM < 29%; book-to-bill < 1.0; FY27 guide < +7%). Three of four cleared outright; FY GM 28.58% nicked the 29% bar but Q4 GM 30.57% and adj-EBITDA +217 bps confirm the mix-shift. The binding constraint is now factory throughput of DMEA/IPC1791 trusted compute, not demand.

Key evidence
  • Largest-ever Common Processing Architecture order per vault context [vault log]
  • DoD C-UAS/ISR procurement acceleration: $3.1B C-UAS appropriation creates demand pull for processing electronics
  • EDGAR filings active: 8-K May 2026 (CIK 0001049521)
  • Defense electronics is a 7-10 year qualification cycle business — backlog visibility once won
  • $967M TTM revenue with $3.1B DoD C-UAS budget appropriation driving demand
  • Ruggedized compute is embedded in multiple defense primes' programs of record (Raytheon, L3Harris, Northrop, BAE)
  • Defense electronics qualification cycle = 7-10 years; platform redesign to switch suppliers prohibitively expensive
  • Analyst consensus "Buy" with $101.50 target (implies ~11% upside from Jun 20)
  • Latest earnings May 5, 2026 (10-Q + 8-K filed same day)
  • DoD C-UAS appropriation ($3.1B) and ISR modernization (LTAMDS AESA, Sentinel radar systems) require advanced signal processing compute — MRCY's core product
  • Multiple programs of record (per Autonomy Software, Fleet Platforms & End Markets layer note): MRCY modules embedded in C-UAS radar processing, EW filtering, ISR fusion pipelines
  • Analyst consensus "Buy" with $101.50 target (implies upside optionality despite current profitability pause)
  • TTM revenue $967M scales with defense procurement — no revenue decline evidence despite profitability caution
  1. GM bridge (FY25 → Q3 FY26): gross profit $254.494M / $912.020M = 27.9% → $69.050M / $235.759M = 29.3%, +140bps — the "burning off low-margin legacy development contracts" the prior note worried about is happening.
  2. Operating inflection: Q3 FY26 operating income +$5.23M (2.2% op margin) vs FY25 -$19.6M (-2.2%). GAAP net loss -$2.9M in Q3, an -81% QoQ improvement from Q2's -$15.1M. The "path to profitability" concern that drove the 06-27 WEAKENED is resolving.
  3. Book-to-bill: Q3 bookings $348M (+74% YoY) ÷ revenue $235.8M = 1.48x (Q3 earnings call).
  4. Backlog coverage: accounting RPO $859.8M ÷ FY26 revenue guide ~$955M = 0.90x; total backlog ~$1.6B (+18% YoY) ÷ $955M = 1.68x.
  5. Cost-of-moat vs moat-defended: FY25 R&D $67.6M = 7.4% of revenue (Q3 FY26 $15.0M = 6.4%) — the annual spend defending the qualification/trust moat, cheap relative to the $1.6B backlog it protects.
  6. Revenue bridge: FY25 $912.0M → FY26 guide $950–960M = +4.2% to +5.3%, re-accelerating to ~9% FY27 / ~10% FY28 (guidance via X).

1. Extra-week-adjusted growth (FY26 is 53 weeks).

`

Headline: $983.622M / $912.020M - 1 = +7.85%

53-wk adj: $983.622M / ($912.020M × 53/52) - 1 = +5.82%

`

Organic growth is real but ~200 bps thinner than the headline. Still well above the 08-16 “FY27 < +7% fails” bar once the extra week is stripped.

2. Backlog coverage of the FY27 guide (the conversion constraint).

`

FY26 revenue $ 983.6M (10-K / EX-99.1)

Total backlog 03 Jul 2026 ~$1,900M (10-K: “approximately $1.9 billion”)

NTM backlog $ 996.0M (10-K)

RPO (stricter) $1,082M (10-K Note; 46% in next 12 months)

FY27 guide ~$1,100M (Q4 call: “approaching $1.1 billion”)

backlog / FY26 rev 1.93×

NTM / FY26 1.01×

NTM / FY27 $1.1B guide 0.905×

`

90.5% of the FY27 “approaching $1.1B” print is already sitting in NTM backlog. The 6–24 month question is factory conversion (Phoenix +50k sq ft, Cicor EMEA transition), not demand generation. Book-to-bill Q4 = 2.28 ($660M bookings / $289.8M rev); FY26 B2B = 1.57 ($1.5B bookings).

3. Cost-of-moat vs moat-defended.

`

FY26 R&D $59.736M = 6.07% of revenue

R&D / $1.9B backlog 3.14%

R&D / $996M NTM backlog 6.00%

`

One year of R&D defends ~16× that spend in NTM backlog. Cheap relative to a QUALIFICATION_BARRIER moat.

4. The 08-16 “Q4 will look softer” sub-claim — FALSIFIED.

The 08-16 note warned management pulled ~$25M revenue / ~$15M adj-EBITDA from Q4 into Q3. Actual Q4 revenue $289.8M vs Q3 $235.8M = +22.9% sequential; Q4 GAAP op income $14.5M vs Q3 $5.2M. The pull-forward did not produce a soft print.

5. Falsification-threshold scorecard (set 2026-08-16, tested 2026-08-18).

Test (08-16)Actual (EX-99.1 / 10-K)Result
Q4 rev < $235M$289.782MPASS
GM < 29%Q4 30.57% / FY 28.58%PARTIAL (Q4 clears; FY nicks)
Book-to-bill < 1.0Q4 2.28 / FY 1.57PASS
FY27 guide < +7%approaching $1.1B ≈ +12% vs FY26PASS

6. Margin bridge (mix-shift, not price).

`

FY25 GM 27.90% → FY26 GM 28.58% (+68 bps) [10-K]

Q4 GM 30.57% vs Q4 FY25 31.05% (-48 bps YoY) [EX-99.1]

FY25 adj. EBITDA margin 13.10% → FY26 15.27% (+217 bps)

FY27 adj. EBITDA approaching $200M / ~$1.1B ≈ 18.2% (high-teens, as guided)

`

The Q4 YoY GM dip is mix/EAC, not a broken recovery: full-year +70 bps and the FY27 path is still toward low-to-mid-20s by FY28 (reference point, not guidance).

ParameterValueSource Confidence
FY26 revenue (53-wk)$983.622Mmeasured (10-K XBRL Revenues)
FY25 revenue (52-wk)$912.020Mmeasured (10-K)
Extra-week-adj YoY+5.82%derived
FY26 gross margin28.58%measured ($281.165M / $983.622M)
Q4 FY26 revenue$289.782Mmeasured (EX-99.1)
Q4 FY26 gross margin30.57%measured ($88.583M / $289.782M)
Q4 GAAP op income$14.465M (5.0%)measured
FY26 GAAP op income$0.280Mmeasured (10-K XBRL OperatingIncomeLoss)
FY26 GAAP NI-$29.673M (-$0.50)measured
Q4 GAAP NI$0.798M ($0.01)measured
FY26 adj. EBITDA$150.192M (15.27%)measured (EX-99.1 recon)
Q4 adj. EBITDA$48.518M (16.7%)measured
FY26 adj. EPS$1.06measured
Q4 adj. EPS$0.37 vs $0.47 LYmeasured
FY26 R&D$59.736M (6.07%)measured (10-K XBRL)
FY26 FCF$68.087M (OCF $102.388M − capex $34.301M)measured
Cash / LT debt / net debt$214.306M / $441.500M / $227.2Mmeasured
Total backlog~$1.9B (vs ~$1.4B FY25)measured (10-K)
NTM backlog$996.0Mmeasured (10-K)
RPO$1,082M (46% next 12 months)measured (10-K)
Q4 bookings / B2B$660M / 2.28measured (EX-99.1)
FY26 bookings / B2B$1.5B / 1.57measured (EX-99.1)
RTX / LMT / NOC share15% / 11% / 10% of FY26 revmeasured (10-K Item 1A)
Defense / gov mix97% of FY26 net revenuesmeasured (10-K)
US unaffiliated rev$944.339M (96.0%)measured (10-K Note Q)
Europe unaffiliated rev$39.283M (4.0%)measured (10-K Note Q)
5-customer receivables54% (vs 48% FY25)measured (10-K)
Phoenix expansion+50,000 sq ft / 18 monthsmeasured (10-K)
FY27 rev / adj. EBITDA guideapproaching $1.1B / ~$200M, FCF conversion ~35%derived (Q4 call; not in 8-K tables)
FY26 fiscal calendar53 weeks vs 52measured (10-K)
ParameterValueSourceTierMeasured / derived / assumedCross-verified
NRE$4.0MAssumed from Mercury 10-K qualitative design-in/customer-qualification risk; not a disclosed mercury dollar figure2/3AssumedNo — single-source qualitative logic
QUAL$1.5MAssumed from Mercury 10-K discussion of military qualification and security requirements2/3AssumedNo
DELAY$3.0MAssumed from defense program schedule-risk logic; no Mercury figure disclosed3AssumedNo
SUPPORT$0.5MAssumed from logistics/ITAR transition cost logic3AssumedNo
Annual Mercury spend per platform variant$2.0MAssumed model input, not Mercury-reported3AssumedNo
Gross-margin directionnegative trendMercury 10-K MD&A / investor release1 locatorDerived directionSingle-source locator for figures not independently retrieved
Switching-cost ratio4.5x baseDerived from formula above—DerivedOutput

These dollar parameters are not company-reported numbers. They are a transparent, order-of-magnitude model. Replace them with actual program-level NRE and qualification data if available.

ParameterValueSourceTierMeasured/derived/assumedCross-verified
Average selling price per unit \(P\)\$18,000Illustrative assumption, not from filingn/aAssumedNo
Direct unit cost \(C\)\$11,700Illustrative assumption, not from filingn/aAssumedNo
Non-recurring engineering \(NRE\)\$2,000,000Illustrative assumption, not from filingn/aAssumedNo
Qualified units \(Q\)1,200Illustrative assumption, not from filingn/aAssumedNo
Pre-NRE gross margin35.0%Derived from assumed inputsn/aDerivedNo
Post-NRE gross margin25.7%Derived from assumed inputsn/aDerivedNo

If this were a live deep dive, the real MRCY inputs would come from the income statement, revenue disaggregation, and program disclosures in the 10-K. The actual values are needs primary source validation.

Bottleneck and moat

Defense-grade ruggedized processing requires MIL-SPEC qualification, ITAR controls, and years of platform integration experience. MRCY's modules are built into programs of record that run for 10-20 years. Switching = complete platform redesign.

MIL-SPEC qualification, ITAR controls, 7-10 year program lock-in. Switching requires complete platform redesign across customer chain. MRCY modules are integral to multiple high-priority programs (C-UAS, radar).

Defense-qualified ruggedized compute faces 7-10 year qualification cycles, MIL-SPEC and ITAR controls, and complete platform integration. MRCY modules are mission-critical in multiple programs of record. Substitution risk is low (re-qualification cost >> component price difference).

Mercury is one of a small number of merchant suppliers of trusted, ITAR-controlled, MIL-SPEC-qualified embedded mission processing. DoD "trust" standards (the Rugged Trusted BuiltSECURE / RTB program, anti-tamper, supply-chain assurance) mean a defense prime cannot freely swap Mercury's module for a commercial or foreign-sourced compute board without a 12–24-month re-qualification of the whole platform. The bottleneck is clearance-gated domestic trusted compute, not the commodity silicon inside it.

  • RTB "BuiltSECURE" trusted servers — largest-ever production order announced June 2026: 1,000+ units, multi-year (MRCY official X, 2069012677880381538).
  • Palantir partnership (early Aug 2026) under the Pentagon Tradewind program: AI-automated material planning and factory operations for defense production (MRCY official X, 2085350435993391264; @MarcJacksonLA 2084308831019090007).
  • Modular Open Systems Approach (MOSA) / SOSA / CMOSS standards positions Mercury's VPX compute as the interchangeable-but-qualified backbone for AESA radar, EW, and C-UAS.
  • Q1 Bypass = 2 (PARTIAL). Substitutes exist (Curtiss-Wright, AMETEK Abaco, primes' in-house compute), but switching a program-of-record module means 12–24-month re-qualification; the trusted BuiltSECURE/RTB niche narrows the field further.
  • Q2 Concentration = 2 (PARTIAL). Defense rugged-compute is an oligopoly (<10 credible merchants), but Mercury holds <30% of total rugged-compute share and its customer base is concentrated in ~5 primes. Pricing power is emerging (GM 29.3% +140bps, op margin inflecting positive) — the 65%-GM PASS bar is software-calibrated and does not apply to 29%-GM hardware; the honest signal is operating-margin trend + oligopoly structure.
  • Q3 Hyperscaler = 3 (PASS). No Microsoft/Google/AWS product replicates ITAR/MIL-SPEC/BuiltSECURE trusted mission compute. Nvidia is commercial silicon, not a trusted-defense substitute.
  • Composite = 2 + 2 + 3 = 7 → STRONG PROXY (10% position cap).

Mercury is one of a handful of merchant suppliers of ITAR-controlled, DMEA-trusted, MIL-SPEC-qualified mission processing. A prime cannot swap a Mercury CPA / BuiltSECURE module for a commercial board or a foreign-sourced compute card without a 12–24 month platform re-qualification. The bottleneck is clearance-gated domestic trusted compute at the Phoenix Advanced Microelectronics Center, not the commodity silicon inside the board.

  • DMEA-trusted + IPC1791 manufacturing (Phoenix AMC). FY2026 10-K: Phoenix is “an IPC1791 certified and DMEA certified trusted manufacturing facility, primarily focused on advanced secure system-on-chip design, assembly, packaging and test,” with +50,000 sq ft of manufacturing space planned over the next 18 months. That is a physical, accredited capacity constraint — not a software feature.
  • BuiltSECURE / BuiltSAFE. 10-K: advanced cryptography, secure boot and physical protection “like our BuiltSECURE technology” plus safety-certifiable BuiltSAFE processing up to the highest design-assurance levels.
  • MOSA / SOSA / OpenVPX / CPA. Common Processing Architecture is the volume product. Q4 included the company’s largest-ever CPA bookings, plus production awards in effectors, airborne, space and missile defense (Q4 FY26 earnings call, 2026-08-18).
  • Defense-prime lock-in. 10-K: sales as a subcontractor/teammate to primes and (in some cases) directly to the U.S. / foreign governments were 97% / 97% / 95% of net revenues in FY26 / FY25 / FY24.
  • Q1 Bypass = 2 (PARTIAL). Substitutes exist (CW, Abaco, prime in-house). Switching a program-of-record module still means 12–24 month re-qualification plus DMEA-trusted supply-chain re-accreditation. 10-K itself flags CPA technical/production challenges — the moat is real but not frictionless.
  • Q2 Concentration = 2 (PARTIAL). RTX 15% + LMT 11% + NOC 10% = 36% top-3. Five customers = 54% of receivables (up from 48%). Hardware GM 28.6% fails the software 65% bar; the honest signal is operating-margin trend (GAAP OM from -2.2% FY25 to +0.03% FY26; adj. EBITDA +217 bps) plus oligopoly structure. Not a 3.
  • Q3 Hyperscaler = 3 (PASS). No Microsoft / Google / AWS product is an ITAR / DMEA / BuiltSECURE substitute. Nvidia is commercial silicon, not trusted-defense compute.
  • Composite = 2 + 2 + 3 = 7 → STRONG PROXY (10% position cap). Unchanged vs 08-16. Cheat-sheet range for PA defense-electronics / trusted compute is 6–7; 7 sits at the top of that range.
  • technical_scarcity = 7 — DMEA/IPC1791 Phoenix trusted fab + BuiltSECURE + 12–24 month re-qual is genuinely scarce. Capped below 8 because (a) merchant competitors exist, (b) 10-K discloses CPA production challenges, (c) MOSA/SOSA is designed to make boards interchangeable once qualified.
  • economic_capture = 6 — Bookings $1.5B / B2B 1.57 / backlog $1.9B (+38%) / GM +68 bps / first full-year GAAP operating profit ($0.28M). Capped because GAAP NI is still -$29.7M, Q4 adj. EPS fell YoY ($0.37 vs $0.47), FCF halved ($68M vs $119M), and hardware GM ~29% is not software capture.
  • time_to_monetize = 7 — FY27 approaching $1.1B / ~$200M adj. EBITDA is a 6–24 month print, and 90.5% of that revenue is already in NTM backlog. Capped because Q1 is guided as the low quarter, FCF conversion is guided ~35% (below the 50% target) on inventory/automation spend, and the extra-week-adjusted FY26 organic rate is 5.8% not 8%.
  • product_service: Secure embedded processing and RF/microwave subsystems for defense mission systems.
  • technical function: Ruggedized high-performance computing, signal processing, EW/SIGINT/ISR, secure storage, RF front-ends, open VPX/SOSA architectures (FY25 10-K Business; acc. UNKNOWN).
  • why it is hard: Defense-grade ruggedization, security/trust, ITAR/export controls, long qualification cycles, custom RF/processing integration (FY25 10-K Risk Factors; acc. UNKNOWN).
  • substitutes: In-house prime development; commercial/industrial boards; other defense electronics suppliers (e.g., Curtiss-Wright, L3Harris, RTX, Elbit) (FY25 10-K Competition/Risk Factors; acc. UNKNOWN).
  • pricing power: MED — sole-source/custom qualified products on some programs, but concentrated buyers and fixed-price development risk (FY25 10-K Risk Factors; acc. UNKNOWN).

Mercury sells the following categories of defense electronics:

  • Embedded processing modules — OpenVPX, SOSA-aligned, rugged single-board computers, digital signal processors, and mission computers.
  • RF and microwave subassemblies — transceivers, tuners, receivers, up/down converters, and RF front ends for EW, radar, and communications.
  • Secure storage and processing subsystems — hardware-encrypted storage, secure servers, and secure workstations.
  • Displays and mission systems — rugged displays, mission computers, and integrated subsystems.
  • Subsystems and custom development — certified, integrated systems for specific programs.

The technical function is to perform real-time sensor processing, communications, data storage, and mission computing in harsh environments: constrained size, weight, and power (SWaP); high g-load, electromagnetic interference, classified data, and long mission durability.

The difficulty is not that a rival cannot build a circuit board; it is the qualification, security, and program-specific engineering burden. Once Mercury hardware is designed into a radar or EW system, that hardware must be:

  • Environmentally qualified to military standards.
  • Security-certified for classified environments.
  • Export-controlled under ITAR or equivalent.
  • Validated across temperature, vibration, shock, and obsolescence management.
  • Supported for the life of the platform, often decades.

Mercury’s 10-K risk factors typically reference design cycles, customer qualification, and long program life. The company’s moat is therefore switching costs and incumbency, not raw silicon differentiation.

Substitutes include:

  • Prime contractor in-house designs — large primes can design their own processing boards, but they often prefer merchant suppliers for open architecture and cost.
  • Other merchant defense electronics suppliers — Curtiss-Wright, AMETEK/Abaco, L3Harris, Elbit, Kontron, Leonardo DRS, and others.
  • Commercial off-the-shelf hardware — but commercial-grade hardware usually cannot meet military qualification/security requirements.
  • FPGA/SoC direct design — customers can design around Mercury by using silicon from Xilinx/AMD, Intel/Altera, or other chip suppliers, but still need board/system integration.

Mercury likely has modest pricing power on sole-source, qualified, production hardware. Being designed into a program gives incumbency. But the company also has exposure to fixed-price development contracts, where cost overruns transfer risk to Mercury. Recent margin compression suggests pricing power is not sufficient to offset program cost overruns, supply-chain inflation, and revenue mix shifts.

The central test for pricing power is whether Mercury can raise prices on production modules without losing sockets. If the hardware is already qualified, near-term substitution is difficult, so pricing power should be positive. But if the program is in development and the prime can still choose an alternative, pricing power is weak. The 10-K’s contract-type disclosure is the best primary-source signal for this balance.

Mercury sells embedded defense electronics. In plain terms, the product set is:

  • Processing hardware: boards, modules, and mission computers that perform real-time signal processing on aircraft, ships, ground vehicles, missiles, and space platforms.
  • RF/microwave subsystems: radio-frequency and microwave components used in radar, electronic warfare, and communications.
  • Secure storage/data systems: rugged data recorders and secure storage devices.
  • Microelectronics: advanced packaging and custom microelectronics for size-, weight-, and power-constrained defense applications.

These categories come from the company’s public product descriptions, not from a specific SEC financial statement.

Source:

mrcy.com

Accessed 2026-04-26.

The technical value proposition is edge processing: sensing a signal, converting it to digital data, processing it in real time, and moving the result securely. In defense platforms, this covers:

  • radar signal processing,
  • electronic warfare and signals intelligence,
  • electro-optical/infrared processing,
  • sonar processing,
  • mission computing,
  • secure data recording and transfer.

MRCY’s products are designed to run in harsh environments with temperature, vibration, shock, and size constraints that ordinary commercial IT hardware does not meet.

Potential substitutes include:

  • prime contractors building equivalent capabilities in-house,
  • competing embedded defense electronics suppliers,
  • ruggedized commercial off-the-shelf servers or industrial computers,
  • other defense electronics primes offering processing products.

MRCY is not the only supplier of rugged embedded processing for defense. Competitors and adjacent suppliers include Curtiss-Wright, Leonardo DRS, L3Harris, AMETEK/Abaco, and others. This is an industry-structure point; specific market-share numbers require primary filings.

The moat is not a single product but the combination of:

  • long qualification cycles on defense platforms,
  • flight heritage and safety approvals,
  • security clearances and secure facility requirements,
  • trusted supplier status,
  • export-control compliance under ITAR/EAR,
  • tight environmental qualification standards.

Once a processor or module is designed into a program of record, swapping it out is expensive and time-consuming. This creates switching costs, but it does not guarantee pricing power.

MRCY’s pricing power is mixed. On one hand:

  • qualified defense hardware can be sticky,
  • classified and secure designs reduce competition,
  • custom microelectronics can carry higher margins.

On the other hand:

  • defense customers increasingly push fixed-price contracts,
  • the government can exert cost pressure through regulations and audits,
  • prime contractors can re-bid programs,
  • commercial competition exists in some ruggedized categories.

MRCY’s own risk factors likely discuss fixed-price contracts, cost overruns, supply-chain inflation, and government procurement changes. Exact language is needs primary source validation, but it is a standard risk cluster for this industry.

Source to verify:

Mercury Systems 10-K risk factors via the EDGAR directory link.

Risks
  • Management transition uncertainty (CEO change 2024); execution risk during transition
  • Defense prime consolidation — primes may insource more compute
  • Continuing Resolution risk: delayed DoD budget slows new program starts
  • TTM net loss (-$14.1M) indicates margin pressure; path to profitability unclear from public data
  • Management transition (new CEO 2024) = execution risk; cost structure not yet optimized
  • Continuing Resolution risk: if DoD budget continues under CR, program starts delay and order pull
  • Defense prime consolidation: primes may attempt insourcing to improve margins
  • Profitability caution flag (MATERIAL): TTM net loss of -$14.1M on $967M revenue (negative 1.5% net margin) indicates either restructuring headwinds, margin compression from materials/labor cost, or one-time charges. Path to 10–15% net margin (typical for qualified defense suppliers) is unclear. If permanent, valuation is vulnerable at 7.2x revenue.
  • Insider selling signal (NEW — Fintel Jun 11 sweep): Heavy insider selling ($152M / 15 sales vs 0 buys); 24.1% insider float = significant concentration. May indicate management concern re: profitability timeline or execution uncertainty.
  • CEO transition execution risk: New CEO (2024) still optimizing cost structure; organizational stability during transition may affect margin recovery path.
  • Transcript gap: No EX-99.1 earnings release in last 180 days — unusual for a $967M public company. May signal delayed earnings or unusual filing. Open question: why no earnings announcement?
  • Defense budget risk: Continuing Resolution or DoD budget sequestration would delay C-UAS order ramp and stretch backlog conversion timeline.
  • GAAP net income is still negative (-$2.9M in Q3) — the "adjusted" beats mask SBC, amortization, and restructuring charges.
  • Q4 pull-forward: management pulled ~$25M revenue and ~$15M adjusted EBITDA from Q4 into Q3, so the Aug 18 Q4 print will likely look softer sequentially — the real test is FY27 guidance, not the Q4 headline.
  • Prime insourcing risk is structural (RTX and L3Harris both maintain in-house mission-compute divisions).
  • Jun 11 Fintel sweep flagged insider selling ($152M / 15 sales / 0 buys); the Jul 29/31 13G/A filings show institutional accumulation, which partially offsets but does not erase the insider signal.
  • Customer concentration in ~5 defense primes creates dependency and renegotiation risk.

10-K competition language is generic (component/board vs subsystem; some larger, some lower-cost; prime insourcing named as a risk). Named merchant peers from prior research remain Curtiss-Wright, AMETEK Abaco, and the primes’ in-house mission-compute shops (RTX, L3Harris). No hyperscaler product replicates DMEA-trusted / ITAR mission compute. MOSA/SOSA is a double-edged sword: it lowers the software switching cost while raising the qualification/trust switching cost — the scarce asset is the accredited factory + program-of-record slot, not the board architecture.

  • GAAP still unprofitable at the net line. FY26 NI -$29.7M. Q4 GAAP NI $0.8M vs $16.4M in Q4 FY25 — the “adjusted” beat is still carrying SBC ($57.1M), amortization ($38.9M), and litigation ($13.5M).
  • FCF degraded. $68.1M vs $119.0M. FY27 conversion guided ~35% vs 50% target because of inventory + Phoenix automation. Cash dropped $94.8M YoY, mostly the $150M revolver paydown.
  • International execution. International operations 2% of revenue (from 5%); Q4 call: international revenue -15% on Cicor manufacturing transition (Geneva → other Swiss / UK sites in FY27). EMEA is a delivery risk, not a demand risk (international backlog “remains strong” per call).
  • Customer concentration rising. RTX 15% (from 13%), top-3 36%. Five-customer receivables 54% (from 48%). A single-program slip at RTX is now a 15-point revenue event.
  • CPA is not a clean win. 10-K (compensation discussion) cites “technical and production challenges relating to our common processing architecture.” The product that is supposed to be the volume engine still has yield/execution risk.
  • Starboard overlay. Five Starboard funds (~14% of the class) opted out of the securities-class settlement (Apr 2026) and filed a separate Massachusetts action (Jun 2026). Not thesis-breaking; it is a cash/attention tax.
  • Auto-stub on this note is wrong. The vault footer labeled “Earnings — FY2026 Q3” with EPS $0.37 / miss vs $0.38 is a mis-tagged Q4 adjusted EPS print. Do not use that stub as a thesis signal.
  • 2026-08-18: FY26 10-K + 8-K Item 2.02 (EX-99.1 earnings release). Record Q4 bookings $660M, backlog ~$1.9B, FY27 outlook raised.
  • 2026-08-18 call: largest-ever CPA bookings; production awards in effectors / airborne / space / missile defense; FY28 reference points (low-double-digit organic, adj. EBITDA at the low end of low-to-mid-20s, FCF conversion back toward 50%).
  • Cicor 5-year EMS (agreement 15 Apr 2025, close 30 Apr 2025) now in the FY27 transition window — the live operational risk.
  • Palantir Tradewind / RTB 1,000-unit order remain 08-16 facts; not re-verified this pass beyond the 10-K BuiltSECURE language.

The Aug 18 print was the binary the 08-16 note was waiting on. Demand is no longer the question (B2B 2.28, backlog 1.93×, NTM covers 90% of FY27). The remaining constraint is trusted-fab throughput + mix-shift into CPA production, which is exactly the QUALIFICATION_BARRIER the thesis claimed. GAAP net income and FCF conversion are the honest residual bears — they keep economic_capture at 6, not 7–8.

  • GAAP net income still -$2.9M in Q3 FY26 (adjusted beats mask SBC + amortization + restructuring).
  • Q4 FY26 has a ~$25M revenue / ~$15M adj-EBITDA pull-forward into Q3 → softer sequential print expected Aug 18.
  • Defense prime insourcing (RTX, L3Harris) is a structural bypass risk.
  • Jun 11 insider-selling sweep ($152M / 15 sales / 0 buys).
  • FY27 guidance < +7% revenue growth, GM < 29%, or book-to-bill < 1.0 at the Aug 18 print.
  • A major prime insourcing a program of record (bypass test drops to 1).
  • Continuing Resolution delaying DoD program starts and stretching backlog conversion.

The bullish deep-dive thesis would be wrong if any of the following appears in primary filings or verified data:

  1. Book-to-bill remains below 1.0 for consecutive quarters.

If bookings are persistently below revenue, backlog runs off and future revenue falls. This is the most direct kill shot for the sticky-backlog thesis.

  1. Gross margin fails to recover after restructuring.

If Mercury’s gross margin stays in the low-20s or falls further, the pricing-power and switching-cost argument is weaker than the fixed-price execution problem.

  1. Loss of a major defense program or key prime socket.

If a primary customer disqualifies Mercury hardware and opts for a competitor or in-house design, it would contradict the switching-cost moat.

  1. A large fixed-price program overrun is disclosed with no recovery path.

If the 8-K/10-Q shows significant EAC charges, margin erosion, and no path to retirement of the troubled program, the economics deteriorate faster than incumbency helps.

  1. Competitor filings show steady share gains while Mercury shrinks.

If Curtiss-Wright, AMETEK/Abaco, or L3Harris report sustained growth in the same defense-electronics categories where Mercury reports revenue declines, Mercury’s moat may not be as strong as assumed.

  1. Customer concentration worsens materially.

If one customer or one program becomes an outsized share of revenue, the company becomes a leveraged bet on a single platform decision, not a diversified defense-electronics franchise.

  1. Strategic process results in a value-destructive outcome.

Mercury has gone through a strategic-review process, activist pressure, executive turnover, and restructuring. If the result is further margin pressure, loss of key engineering talent, or a sale at a discount, the long-term business value is impaired.

  1. Defense budget reallocation away from electronics-heavy platforms.

If DoD funding shifts from EW, radar, C4I, and sensor processing toward manpower, infrastructure, or platforms where Mercury content is lower, revenue can decline even if total defense spending rises.

The following would disprove or seriously weaken a bullish MRCY thesis:

  1. Continued fixed-price program overruns. If 10-K/8-K disclosures show rising cost estimates on fixed-price development programs, margin recovery is unlikely.
  1. Sustained book-to-bill below 1.0. If orders do not replace revenue, the backlog will shrink and future revenue will decline.
  1. Customer concentration loss. If a large prime program is re-bid, delayed, or canceled, MRCY’s revenue could drop sharply.
  1. Competitor share gains. If Curtiss-Wright or other competitors report stronger defense-electronics growth and margins, MRCY’s problems may be structural rather than cyclical.
  1. Failed strategic review or fire-sale outcome. If MRCY cannot achieve a premium sale or strategic separation, the activist-driven re-rating thesis weakens.
  1. Defense budget rotation away from sensor/electronic-warfare programs. MRCY’s revenue depends on DoD procurement and RDT&E priorities. If funding shifts away from its product categories, demand falls.
  1. Persistent inventory and receivables build. If 10-Q data show inventory growth without revenue growth, demand may be weaker than reported backlog suggests.

None of these are asserted as current facts; they are falsification tests to apply to the actual filings.

Open questions
  • What is MRCY's FY26 revenue growth rate and program backlog?
  • What C-UAS programs is MRCY specifically embedded in?
  • Why is company at break-even / slight loss? (Restructuring, margin compression, or one-time charges?)
  • What is FY26 Q3 revenue growth rate? (CAGR and trajectory)
  • What is backlog-to-revenue ratio? (Strong order book depth)
  • Which specific C-UAS programs embed MRCY modules, and what is the order value?
  • Why did TTM net income remain negative (-$14.1M) despite stable revenue? Restructuring charges, material cost spikes, or structural margin compression?
  • What is MRCY's Q3 FY26 backlog-to-revenue ratio? (Strong backlog would support eventual profitability return.)
  • Which specific C-UAS programs embed MRCY modules, and what is the multi-year order depth?
  • Why no earnings announcement in last 6 months? Corporate action, delayed filing, or extraordinary items?
  • Has new CEO provided a profitability recovery timeline / target net margin? (Management guidance would answer execution concern.)
  • What is CPA’s share of FY26 / FY27 revenue (10-K does not segment it)?
  • Does the Phoenix +50k sq ft come online before the NTM $996M has to convert, or does Cicor/EMEA slippage push revenue right?
  • Can adj. EBITDA actually approach $200M if Q4 FY26 was $48.5M and Q1 is the low quarter?
  • Starboard separate action: cash or distraction?
Research verdict

INTACT

INTACT (profitability caution flag)

The core thesis — ruggedized embedded computing is a bottleneck for defense autonomy — remains intact. MRCY's position as a multi-prime supplier into programs of record is defensible and benefits directly from C-UAS procurement acceleration. However, near-term execution uncertainty (CEO transition, path to profitability) warrants monitoring. Next validation: confirm revenue growth in Q3 FY26 and see path to profitability in guidance.

WEAKENED — with caveat

Core thesis (ruggedized compute is a bottleneck for defense autonomy) remains INTACT. However, near-term execution risk (profitability timeline, insider selling, missing earnings signal) has risen. The name is NOT broken — defense procurement tailwinds are real — but path to valuation re-rating is now conditional on management demonstrating profitability recovery. Recommendation: Move to WATCH pending Q3 FY26 earnings (expected Aug 2026) and any management guidance on profitability / backlog. Re-enter at conviction=3/INTACT only if earnings show margin recovery trajectory.

Primary and supporting material

Sources

17 sources preserved from the latest qualified research update.

  1. sec.govMercury Systems SEC EDGAR filingsOpen source ↗
  2. sec.govQ3 FY2026 Form 10 QOpen source ↗
  3. mrcy.comsourceOpen source ↗
  4. sec.govsec.govOpen source ↗
  5. sec.govsec.govOpen source ↗
  6. ir.mrcy.comir.mrcy.comOpen source ↗
  7. sec.govsec.govOpen source ↗
  8. sec.govsec.govOpen source ↗
  9. sec.govsec.govOpen source ↗
  10. ir.mrcy.comir.mrcy.comOpen source ↗
  11. sec.govsec.govOpen source ↗
  12. mrcy.commrcy.comOpen source ↗
  13. ir.mrcy.comir.mrcy.comOpen source ↗
  14. sec.govsec.govOpen source ↗
  15. sec.govsec.govOpen source ↗
  16. comptroller.defense.govcomptroller.defense.govOpen source ↗
  17. congress.govcongress.govOpen source ↗
Historical long-form synthesis

MRCY: Mercury Systems Trusted Defense Compute Thesis

1,056 words · Research as of 8 Sept 2026

Preserved research context: this long-form synthesis reflects the evidence and valuation snapshot available on 8 Sept 2026. Use the current snapshot above for the latest signal, conviction, target and market-cap values.

Investment Thesis

Mercury Systems is a merchant supplier of ruggedized, ITAR-controlled, DMEA-trusted embedded computing — Common Processing Architecture and OpenVPX boards, BuiltSECURE and BuiltSAFE mission processors, RF modules, and secure microelectronics. It sells almost entirely as a subcontractor to U.S. defense primes. The product is the mission-compute brain inside radar, electronic-warfare, counter-UAS, missile-defense, space, and effector programs — not a commercial server and not a prime platform.

Demand is no longer the open question. After the fiscal 2026 Form 10-K and the August 18, 2026 8-K EX-99.1, FY26 net revenues were $983.622 million versus $912.020 million in FY25 (+7.85% on a 53-week year; +5.82% extra-week-adjusted). Bookings were $1.5 billion (book-to-bill 1.57); fourth-quarter bookings were $660 million (book-to-bill 2.28). Total backlog is about $1.9 billion. Next-twelve-month backlog of $996.0 million covers about 90.5% of the FY27 outlook of approaching $1.1 billion. The binding constraint has shifted to factory conversion of accredited trusted compute at Phoenix.

Machine state is mixed. Thesis status is STRENGTHENED. Differentiated scores from the September 5, 2026 vault writeback are technical_scarcity 7, economic_capture 6, and time_to_monetize 7. Toll-road remains 2 / 2 / 3, composite 7, STRONG PROXY. Current action is TRIM, stage WATCH, crowding YELLOW. Latest price is $82.42 versus a $106.81 first-flag close, down 23.3% on the month. GAAP net income is still a $29.673 million loss for the year. This is a qualified bottleneck with improving bookings, not a clean compounder.

Physical AI / Value-Chain Relevance

Mercury sits in Physical AI as a component supplier into Autonomy Software, Fleet Platforms & End Markets. The SKU is edge and embedded compute; the compounding exposure is defense autonomy. Customer classes are Defense C-UAS Integrators and Government Program Buyers. Value-chain role is picks-and-shovels, not an end-market OEM.

The bottleneck is clearance-gated domestic trusted compute, not the commodity silicon inside the board. The FY26 10-K describes Phoenix as an IPC1791-certified and DMEA-certified trusted manufacturing facility, with 50,000 square feet of additional space planned over the next 18 months. A prime cannot swap a Mercury CPA or BuiltSECURE module for a commercial or foreign board without a 12-to-24-month platform re-qualification. Defense and government sales were 97% of FY26 net revenues. RTX, Lockheed Martin, and Northrop Grumman accounted for 15%, 11%, and 10%. Five customers represented 54% of receivables, up from 48%. Named merchant peers remain Curtiss-Wright, AMETEK Abaco, and the primes’ in-house shops. No hyperscaler product replicates DMEA-trusted, ITAR mission compute. Swiss manufacturing moved to Cicor under a five-year exclusive EMS agreement after the Plan-les-Ouates sale closed April 30, 2025; international operations fell to 2% of FY26 net revenues from 5%.

Catalysts

The August 18 FY26 print was the binary the August 16 note was waiting on. Three of four falsification tests cleared: Q4 revenue $289.782 million versus a $235 million fail line; book-to-bill 2.28 versus 1.0; FY27 outlook approaching $1.1 billion versus a plus-7% fail line. Gross margin was partial: Q4 30.57% cleared 29%, full-year 28.58% nicked it. Q4 sequential revenue rose 22.9% versus Q3 $235.8 million, which falsifies the earlier pull-forward warning of a soft print.

Near-term conversion catalysts are the Phoenix expansion, mix-shift into Common Processing Architecture — Q4 included the company’s largest-ever CPA bookings, plus production awards in effectors, airborne, space, and missile defense — and the FY27 adjusted EBITDA path toward about $200 million with free-cash-flow conversion guided around 35%. Palantir Tradewind and the June 2026 RTB BuiltSECURE order of more than 1,000 units remain prior-note facts and were not re-verified on the September 5 pass beyond 10-K language. Cicor’s EMS transition is now in the FY27 window and is a delivery risk, not a demand risk.

Positioning / What the Market May Be Missing

The tape is pricing execution and profitability, not demand. Trailing GAAP P/E is not meaningful at -482.88. Forward P/E is 83.58. Market cap is about $6.96 billion. Institutional ownership is 103.79%. Price $82.42 sits near the $79.35 target and below the original $100–110 entry range — a TRIM and WATCH posture after a broken entry, not a fresh accumulate.

What may be under-weighted is conversion math. About 90% of the FY27 revenue outlook is already in next-twelve-month backlog. FY26 free cash flow was $68.087 million. One year of R&D, $59.736 million or 6.07% of revenue, defends roughly 16 times that spend in NTM backlog. Adjusted EBITDA rose 217 basis points to 15.27%. FY26 produced the first full-year GAAP operating profit, $0.280 million, after a $19.627 million operating loss in FY25. The residual bear is honest: FY26 GAAP net loss was still $29.673 million, Q4 adjusted EPS fell year over year ($0.37 versus $0.47), and free cash flow halved versus $119.0 million. A June 11 Fintel sweep flagged $152 million of insider selling across 15 sales and zero buys. The packet’s thesis_chain still carries a stale DEMOTION CANDIDATE / WEAKENED line that conflicts with the STRENGTHENED writeback; the 10-K numbers are the source of truth.

Risks and What Invalidates the Thesis

Prime insourcing at RTX and L3Harris is a structural bypass. Customer concentration is rising: the top three are 36% of revenue, and a slip at RTX is a 15-point revenue event. The 10-K cites technical and production challenges on common processing architecture. International revenue was down 15% on the Cicor transition. FY27 free-cash-flow conversion is guided around 35% versus a 50% target. Cash dropped $94.8 million year over year, mostly a $150 million revolver paydown; net debt is $227.2 million. A continuing resolution that delays DoD program starts would still stretch backlog conversion.

What to Watch Next

Watch whether Phoenix’s extra 50,000 square feet comes online before the $996 million NTM backlog has to convert, and whether Cicor or EMEA slippage pushes revenue to the right. CPA’s share of FY26 and FY27 revenue is not segmented in the 10-K. Test whether adjusted EBITDA can approach $200 million if Q4 was $48.518 million and Q1 is guided as the low quarter. Re-check insider Form 4s against institutional 13G/A. Do not treat TRIM as a completed exit until GAAP net income and free-cash-flow conversion show that record bookings are becoming owner earnings.

Continue company research

Related companies

View public companies
SPIR

Spire Global Inc.

Autonomy Software, Fleet Platforms & End MarketsPOOL · ●●●○○ISRG

Intuitive Surgical

Autonomy Software, Fleet Platforms & End MarketsWATCH · ●●○○RDW

Redwire Corporation

Autonomy Software, Fleet Platforms & End MarketsHOLD · ●●○○RTX

RTX Corp (Raytheon Technologies)

Autonomy Software, Fleet Platforms & End MarketsWATCH · ●●○○
The weekly brief

Get a weekly digest of what’s changing.

Research updates, thesis changes and company developments. One email a week.