NVIDIA Jetson Module Lifecycle Guide
A production decision is not just “Which Jetson is fastest?” It is whether the exact module, software branch, carrier design, security process, and service plan can stay supportable for as long as your customer contract requires.
Align four clocks before freezing a Jetson module.
Plan the production-module supply window, the JetPack/Jetson Linux maintenance path, the carrier and peripheral lifecycle, and your own production plus field-service obligation. The earliest unsupported clock controls the real risk.
“Available through” covers only one part of the decision.
A long hardware availability date can coexist with an aging software branch, an obsolete camera, or a customer service obligation that extends years past last shipment.
Module supply
Exact production SKU, forecast, PCN flow, last-time forecast, order deadline, last shipment, and approved source.
Software branch
JetPack/L4T compatibility, kernel, CUDA, TensorRT, drivers, containers, upstream packages, security fixes, and OTA path.
Product hardware
Carrier, PMIC, storage, cameras, networking, connectors, thermal solution, enclosure, manufacturing test, and compliance.
Customer obligation
Start and end of production, warranty, repair demand, spares, update policy, cybersecurity response, and end-of-service date.
Start with the program stage, not the module name.
Choose the situation that best matches your project. The output is a review agenda, not a substitute for NVIDIA notices or engineering validation.
Prove the workload, but keep the production path visible.
A developer kit can speed software discovery. Before architecture freeze, move the design onto the exact production module and a production-quality carrier.
- Record the intended production module SKU, not only the kit name.
- Benchmark the real camera, storage, thermal and power envelope.
- Select a JetPack branch that supports the production module and update strategy.
- Budget carrier bring-up, factory flashing, regulatory testing and recovery.
Production-module availability as of August 28, 2026
NVIDIA’s live lifecycle page is the date authority used here. These dates are planning horizons—not a promise of channel stock, stable price, unlimited allocation, or an order window that remains open until the same month.
| Module group | Production modules | Available through | Lifecycle action |
|---|---|---|---|
| Jetson Thor | T4000 | January 2036 | Longest published horizon in the current table; still qualify the Thor carrier, power, cooling, JetPack 7 and complete system. |
| Jetson Thor | T5000 | August 2035 | Use the exact module and regional SKU; do not confuse it with an AGX Thor developer kit. |
| Commercial Orin | AGX Orin 64GB/32GB; Orin NX 16GB/8GB; Orin Nano 8GB/4GB | January 2032 | Viable for many current designs if production fits the horizon and service is covered by spares or a funded successor plan. |
| Industrial Orin | AGX Orin Industrial | July 2033 | Confirm the industrial SKU, environmental need and full lifecycle economics; “industrial” is not interchangeable with commercial AGX Orin. |
| Legacy Xavier / TX2 | AGX Xavier 32GB/Industrial; Xavier NX 16GB/8GB; TX2 NX; TX2i | July 2027 | Last-time forecast and PO deadline announced for July 15, 2026 has passed. Treat as active migration or confirmed-backlog work. |
| Jetson Nano | Jetson Nano production module | January 2027 | Not suitable for a fresh long-life design without a defensible finite-stock and software-maintenance plan. |
Source: NVIDIA Jetson Product Lifecycle. Accessed August 28, 2026.
A kit proves ideas; it does not create a production supply plan.
NVIDIA states that developer kits contain a non-production-specification module on a reference carrier and are not intended for production. Kits have no specified lifecycle on the lifecycle page. A production module ships without software and must be integrated with the carrier, image, security, and factory process for the sellable product.
- Freeze the production module’s complete part number and memory configuration.
- Move to the intended carrier early enough for pinmux, device tree, storage, camera, EMC, thermal and manufacturing validation.
- Keep kit procurement separate from production-module forecasts and contracts.
- Do not assume a developer-kit EOL date predicts the production module’s date—or the reverse.
Source: NVIDIA Jetson FAQ.
The commercial commitment point can arrive a year before last shipment.
NVIDIA’s May 2026 forum announcement said LPDDR4 supply constraints affected TX2 NX, TX2i, AGX Xavier 32GB/Industrial, and Xavier NX 8GB/16GB. Customers were asked to submit forecasts and noncancelable, nonreturnable purchase orders by July 15, 2026, with final shipments no later than July 15, 2027.
The lifecycle page’s “July 2027” date is a shipment horizon, not permission to wait until July 2027 to place a new factory order. By this article’s August 28, 2026 evidence date, the announced forecast/PO deadline had passed. Affected teams should confirm existing backlog or distributor-held strategic inventory and progress a migration; they should not present the lifecycle date as current order acceptance.
It also demonstrates why a roadmap screenshot is weak evidence. A product manager needs the live lifecycle table, the actual EOL/last-time-buy notice, the exact SKU, the approved order record, and a date-stamped internal decision.
Source: NVIDIA Developer Forums: Jetson Product EOL Updates.
Hardware availability does not guarantee your preferred JetPack branch.
The current archive shows different module coverage by release. “Jetson software compatible” still allows porting work when the JetPack generation, kernel, CUDA stack, boot chain, or device tree changes.
JetPack 7.2.1
Lists T4000, T5000, AGX Thor developer kit, and the Orin family with Jetson Linux 39.2.1.
JetPack 6
NVIDIA’s FAQ calls JetPack 6 sustaining; the 6.2.3 archive entry supports AGX Orin, Orin NX and Orin Nano.
JetPack 5
NVIDIA’s FAQ calls JetPack 5 sustaining and says it supports Orin and Xavier.
JetPack 4
The FAQ marks JetPack 4 EOL. It remains the legacy foundation for Nano, TX2 and some Xavier deployments.
On August 28, 2026, NVIDIA’s live lifecycle page showed July 2027 dates for affected Xavier/TX2 modules, while an older answer within the FAQ still displayed January 2028 and July 2031 dates for some Xavier products. The control is simple: use the dedicated lifecycle page for current hardware dates, and use the FAQ for product-policy and compatibility explanations. Save the access date and escalate conflicts rather than choosing the more convenient number.
Sources: NVIDIA JetPack Archive, Jetson Software Documentation, and NVIDIA Jetson FAQ.
Freeze the complete image, not the phrase “latest JetPack.”
A production record should identify the module, board configuration, Jetson Linux/L4T release, JetPack components, kernel, bootloader, CUDA, cuDNN, TensorRT, multimedia stack, camera and peripheral drivers, container runtime, root filesystem, application packages, model artifacts, and security configuration.
- Archive permitted packages, licenses, build scripts, containers, patches, device trees, pinmux and flashing configuration.
- Record image hashes, signing keys and key ownership, factory recovery media, and rollback rules.
- Test the supported update path from every deployed baseline—not only from the newest lab image.
- Validate application inference, camera timing, storage, network, boot, thermals, power, secure boot and recovery after every branch change.
Build
Generate the exact signed image or OTA payload from controlled inputs.
Qualify
Exercise upgrades, power interruption, A/B or rollback behavior, and recovery on production hardware.
Deploy
Stage by cohort, verify identity and compatibility, monitor health, and stop on defined thresholds.
Retire
Define the final supported image, residual risk, compensating controls, and migration or decommissioning path.
The same connector does not mean a drop-in replacement.
NVIDIA’s FAQ distinguishes pin-and-form-factor compatibility from form-factor-only relationships. Orin NX/Nano and Xavier NX-family modules can share mechanical concepts, but NVIDIA says they are not pin-compatible; a carrier can be designed around common I/O only when the design documents are followed.
- Compare pin functions, unavailable signals, UPHY use, voltage rails, sequencing, source current and power modes.
- Revalidate cameras and SerDes, PCIe/NVMe, networking, USB, display, GPIO, clocks and storage boot paths.
- Check heatsink contact, TTP limits, airflow, throttling, shock/vibration, keep-outs, assembly and enclosure fit.
- Re-run BSP bring-up, device-tree, flashing, manufacturing, EMC, safety and application regression.
A software-enabled power mode is also a hardware change. NVIDIA notes that Orin Super Mode can require more carrier-board power and thermal capability, including the correct HV rail for Orin NX.
Three lifecycle decisions—and the consequence of getting each wrong
The scenarios below are hypothetical composites for planning. They are not YURUNOX customer claims, shipment results, or first-hand test reports.
A prototype works on Jetson Nano
The application meets its lab goal, but the production module is listed only through January 2027 and JetPack 4 is EOL.
Decision consequence: freezing the prototype unchanged creates immediate supply and security-maintenance exposure. Re-baseline the workload on a current module before product qualification.
A Xavier NX fleet cannot be reflashed casually
The installed base uses custom camera drivers, encrypted storage, a factory recovery image, and a JetPack 4-era application stack.
Decision consequence: buying modules addresses only hardware supply. The owner must choose between maintaining the old branch, porting to JetPack 5 where appropriate, or migrating the complete hardware/software platform—with validation for every deployed baseline.
Orin NX is proposed as a “same-size” replacement
The mechanical outline seems familiar, but the old carrier, power budget, CSI design, pin use and cooling were optimized for Xavier NX.
Decision consequence: approving by connector appearance risks board damage or field instability. Treat it as a controlled migration with schematic comparison, bring-up and regression gates.
Turn a web date into an auditable production decision.
A trustworthy lifecycle file connects manufacturer evidence to the exact SKU, software baseline, purchasing terms, and approved engineering response.
Live lifecycle snapshot
Save the NVIDIA lifecycle page with access date and approved interpretation. Recheck on a defined cadence.
PCN / EOL / LTB notice
Record affected SKUs, last forecast, last order, NCNR terms, last shipment, and required engineering action.
Exact module identity
Capture full part number, capacity, industrial/commercial grade, origin requirements, revision, labels, date code and packing.
Software bill of materials
Keep JetPack/L4T, kernel, CUDA stack, containers, drivers, model, security settings, images and hashes together.
Carrier and validation record
Link schematic/BOM revision, design-guide assumptions, thermal results, compliance, factory tests and regression coverage.
Supply and service model
Connect forecasts, backlog, usable inventory, repair yield, storage controls, field demand, buffer assumptions and migration triggers.
Calculate the supply horizon before choosing the module.
Required supply horizon = start of production + production period + service/spares period + risk buffer. If the module date covers production but not service, the business must fund service inventory, qualify a successor, shorten the obligation, or redesign.
| Gate | Questions to answer | Evidence required |
|---|---|---|
| Architecture freeze | Does the exact module cover production? Is the software branch maintainable? Is migration technically credible? | Dated lifecycle snapshot, SKU, performance/thermal margin, branch decision, preliminary successor path. |
| Production release | Can factory, quality and security processes reproduce the approved product? | AVL, carrier qualification, signed image, key process, inspection criteria, functional test and supply forecast. |
| Annual / PCN review | Did dates, components, software status, forecast, field failures or customer commitments change? | Lifecycle diff, PCN disposition, regression results, inventory/backlog, SBOM and risk register. |
| Last-time buy | How much usable stock is needed, and what uncertainty remains? | Installed base, production tail, service demand, repair yield, scrap, qualification units, on-hand inventory, storage plan and NCNR approval. |
| Migration release | Has the complete replacement system—not just the module—passed? | Carrier and mechanical review, BSP/image, performance, I/O, thermal, EMC, security, OTA, manufacturing and customer approval. |
Do not apply an arbitrary “5% spares” rule. Use installed base by year, reliability and repair data, production tail, warranty terms, storage conditions, lead time, scrap, uncertainty scenarios and usable on-hand inventory.
Ask for evidence that matches the real lifecycle risk.
Identify the product and commitment
- Exact NVIDIA module part number and approved alternates
- Memory capacity and commercial/industrial grade
- Country-of-origin and date-code policy
- Forecast, firm quantity, schedule and destination
- Production and service horizon
- Cancellation, return and NCNR terms
Verify the offer and change process
- Written order acceptance, lead time and backlog basis
- Current lifecycle status, latest PCNs and EOL notices
- Authorized or independent source basis stated clearly
- Traceability, storage, inspection and counterfeit controls
- Firmware/BOM revision and packing evidence
- RMA route, split-delivery plan and notification flow
As an independent electronic-component sourcing partner, YURUNOX can align an offered Jetson module with the requested SKU, quantity, schedule, source basis, available evidence, commercial terms, and customer-defined inspection or traceability requirements. NVIDIA lifecycle commitments, software support, compatibility, and technical qualification remain governed by NVIDIA documentation and the customer’s engineering approval.
For broader sourcing controls, see YURUNOX’s NVIDIA product page, quality assurance process, purchasing experience, and global shipment workflow.
Jetson lifecycle questions from engineering and purchasing teams
How long are commercial Jetson Orin modules available?
NVIDIA’s lifecycle page listed AGX Orin 64GB/32GB, Orin NX 16GB/8GB, and Orin Nano 8GB/4GB through January 2032 when checked on August 28, 2026. AGX Orin Industrial was listed through July 2033. Recheck the live page before a contract or purchase decision.
How long are Jetson T4000 and T5000 available?
The current NVIDIA lifecycle page listed T4000 through January 2036 and T5000 through August 2035. These are production-module dates, not a lifecycle commitment for the AGX Thor developer kit.
Can a Jetson developer kit be used in a production product?
NVIDIA says developer kits are not for production use. They contain a non-production-specification module on a reference carrier and have no guaranteed availability lifecycle. Production requires the production module, carrier integration, software image, validation, manufacturing process and supply plan.
Does module availability guarantee JetPack support until the same date?
No. Hardware and software move on separate timelines. Check the JetPack archive, Jetson Linux release notes, security bulletins, module support, upstream dependencies and the supported update path for the exact deployed baseline.
What changed for Xavier and TX2-family modules in 2026?
NVIDIA announced that LPDDR4 supply affected TX2 NX, TX2i, AGX Xavier 32GB/Industrial, and Xavier NX 8GB/16GB. It requested last-time forecasts and POs by July 15, 2026, with final shipment no later than July 15, 2027. That order deadline had passed by this article’s evidence date.
Is Orin NX a drop-in replacement for Xavier NX?
No. NVIDIA describes the relationship as form-factor compatible, not pin-compatible. A carrier can support common I/O only when designed for both. Review pinout, power, UPHY, cameras, storage, thermal, BSP, mechanics, compliance and regression.
How often should a Jetson lifecycle plan be reviewed?
Quarterly is a practical baseline for an active production program, with immediate review after lifecycle changes, PCNs, EOL notices, security bulletins, JetPack releases, forecast changes, large orders or new service commitments. High-risk legacy programs may need monthly supply review.
Evidence used for this guide
Technical facts were checked against current NVIDIA primary sources. Image authors and reuse licenses are linked at the point of use.
- NVIDIA Jetson Product Lifecycle — current module availability, EOL modules, developer-kit policy, PCN statement, and minimum EOL-notice timing.
- NVIDIA Developer Forums: Jetson Product EOL Updates — May 2026 LPDDR4 impact, last-time forecast/PO deadline, NCNR basis, and last shipment.
- NVIDIA Jetson FAQ — developer kit versus production module, JetPack branch status, hardware compatibility, Super Mode, warranty, and operating-life policy.
- NVIDIA JetPack Archive — release-to-module compatibility for current and historical JetPack versions.
- NVIDIA Jetson Software Documentation — current and archived Jetson Linux developer guides and release notes.
- NVIDIA Jetson Linux Developer Guide: Software Packages and the Update Mechanism — image-based OTA, update-path constraints, payload security, OEM client and recovery responsibilities.
Checked August 28, 2026. Lifecycle dates, order windows, release status, PCNs, part numbers, distributor commitments and security guidance can change; verify the live source before approval.
Need to review a Jetson module requirement?
Send the exact module candidates, annual quantity, start of production, production and service years, carrier, power and thermal limits, JetPack/L4T baseline, destination, required evidence, and migration authority.