country_code

What Is Federated Learning?

Federated learning is a way to develop and validate AI models from diverse data sources while mitigating the risk of compromising data security or privacy, as the data never leaves individual sites.
by
AI healthcare

Editor’s note: On April 16, 2024, we updated our original post on federated learning, which was first published October 13, 2019. 

The key to becoming a medical specialist, in any discipline, is experience.

Knowing how to interpret symptoms, which move to make next in critical situations, and which treatment to provide — it all comes down to the training you’ve had and the opportunities you’ve had to apply it.

For AI algorithms, experience comes in the form of large, varied, high-quality datasets. But such datasets have traditionally proved hard to come by, especially in the area of healthcare.

Federated learning is a way to develop and validate accurate, generalizable AI models from diverse data sources while mitigating the risk of compromising data security or privacy. It enables AI models to be built with a consortium of data providers without the data ever leaving individual sites.

Medical institutions have had to rely on their own data sources, which can be biased by, for example, patient demographics, the instruments used or clinical specializations. Or they’ve needed to pool data from other institutions to gather all of the information they need, which requires managing regulatory issues.

Federated learning makes it possible for AI algorithms to gain experience from a vast range of data located at different sites.

The approach enables several organizations to collaborate on the development of models, but without needing to directly share sensitive clinical data with each other.

Over the course of several training iterations the shared models get exposed to a significantly wider range of data than what any single organization possesses in-house.

Federated learning is gaining traction beyond healthcare, moving into financial services, cybersecurity, transportation, high performance computing, energy, drug discovery and other fields.

Frameworks such as NVIDIA FLARE (NVFlare) have enabled enterprises to collaborate by contributing data through federated learning for model improvements.

NVFlare, an open-source federated learning framework that’s widely adopted across various applications, offers a diverse range of examples of machine learning and deep learning algorithms. It includes robust security features, advanced privacy protection techniques and a flexible system architecture — building trust among users.

How Federated Learning Works 

The main concept of federated learning is to train models locally without sharing data, only the model parameters.

The aggregator starts with an initial global model and broadcasts the model parameters to all clients. The client node receives the global model parameters and starts training the received model on local data. Then, the newly trained local model is sent back to the aggregator node. Only model parameters, no private data, are shared with the aggregator.

The aggregator node will perform aggregation, such as weighted average, to produce a new global model. That new global model will be broadcast again by repeating the first step until convergence, or until it’s reached the max number of rounds.

AI algorithms deployed in medical scenarios ultimately need to reach clinical-grade accuracy. Largely speaking, this means that they meet, or exceed, the gold standard for the application to which they’re applied.

To be considered an expert in a particular medical field, you generally need to have clocked 15 years on the job. Such an expert has probably read around 15,000 cases in a year, which adds up to around 225,000 over their career.

When you consider rare diseases, which affect around one in 2,000 people, even an expert with three decades’ experience will have only seen roughly 100 cases of a particular condition.

To train models that meet the same grade as medical experts, the AI algorithms need to be fed a large number of cases. And these examples need to sufficiently represent the clinical environment in which they’ll be used.

But currently the largest open dataset contains 100,000 cases.

And it’s not only the amount of data that counts. It also needs to be very diverse and incorporate samples from patients of different genders, ages, demographics and environmental exposures.

Individual healthcare institutes may have archives containing hundreds of thousands of records and images, but these data sources are typically kept siloed. This is largely because health data is private and cannot be used without the necessary patient consent and ethical approval.

Federated learning decentralizes deep learning by removing the need to pool data into a single location. Instead, the model is trained in multiple iterations at different sites.

For example, say three hospitals decide to team up and build a model to help automatically analyze brain tumor images.

If they chose to work with a client-server federated approach, a centralized server would maintain the global deep neural network and each participating hospital would be given a copy to train on their own dataset.

Once the model had been trained locally for a couple of iterations, the participants would send their updated version of the model back to the centralized server and keep their dataset within their own secure infrastructure.

The central server would then aggregate the contributions from all of the participants. The updated parameters would then be shared with the participating institutes, so that they could continue local training.

A centralized-server approach to federated learning.

If one of the hospitals decided it wanted to leave the training team, this would not halt the training of the model, as it’s not reliant on any specific data. Similarly, a new hospital could choose to join the initiative at any time.

This is just one of many approaches to federated learning. The common thread through all approaches is that every participant gains global knowledge from local data — everybody wins.

Why Federated Learning?

Federated learning still requires careful implementation to ensure that patient data is kept secure. But it has the potential to tackle some of the challenges faced by approaches that require the pooling of sensitive clinical data.

For federated learning, clinical data doesn’t need to be taken outside an institution’s own security measures. Every participant keeps control of its own clinical data.

As this makes it harder to extract sensitive patient information, federated learning opens up the possibility for teams to build larger, more diverse datasets for training their AI algorithms.

Implementing a federated learning approach also encourages different hospitals, healthcare institutions and research centers to collaborate on building a model that could benefit them all.

How Federated Learning Can Transform Industries

Federated learning could revolutionize how AI models are trained, with the benefits also filtering out into the wider healthcare ecosystem.

Larger hospital networks would be able to work better together and benefit from access to secure, cross-institutional data. While smaller community and rural hospitals would enjoy access to expert-level AI algorithms.

It could bring AI to the point of care, enabling large volumes of diverse data from across different organizations to be included in model development, while complying with local governance of the clinical data.

Clinicians would have access to more robust AI algorithms, based on data that represents a wider demographic of patients for a particular clinical area or from rare cases that they would not have come across locally. They’d also be able to contribute back to the continued training of these algorithms whenever they disagreed with the outputs.

Healthcare startups could bring cutting-edge innovations to market faster, thanks to a secure approach to learning from more diverse algorithms.

Meanwhile, research institutions would be able to direct their work toward actual clinical needs, based on a wide variety of real-world data, rather than the limited supply of open datasets.

Large-scale federated learning projects are now starting, hoping to improve drug discovery and bring AI benefits to the point of care.

MELLODDY, a drug-discovery consortium based in the U.K., aims to demonstrate how federated learning techniques could give pharmaceutical partners the best of both worlds: the ability to leverage the world’s largest collaborative drug compound dataset for AI training without sacrificing data privacy.

King’s College London is hoping that its work with federated learning, as part of its London Medical Imaging and Artificial Intelligence Centre for Value-Based Healthcare project, could lead to breakthroughs in classifying stroke and neurological impairments, determining the underlying causes of cancers, and recommending the best treatment for patients.

In the context of financial services, federated learning can be applied to train a model using data from several banks to estimate individual transaction risk scores while keeping personal information locally at the banks.

Fraud detection is an important federated learning use case for banking and insurance. Institutions can harness data from user accounts and fraud cases to create better fraud-detection models without sacrificing user data privacy.

This can be challenging without federated learning, considering data privacy protection laws such as the EU’s GRPR, China’s PIPL and the recent EU AI Act, which prohibits cross-border data sharing. With federated learning, financial institutions can comply with these laws and regulations while using rich, private datasets for better, safer outcomes.

NVFlare can be used with XGBoost and Kaggle’s Credit Card Fraud Detection dataset for securing credit card transactions and with graph neural networks (GNNs) for financial transaction classification.

Federated learning is also applicable in use cases such as federated data analytics on edge medical devices, cross-board data training with autonomous vehicle models and drug discovery. Driven by data privacy regulations, the need to build better models with more private data, as well as the generative AI boom, the adoption of federal learning is accelerating.

Learn more about NVFlare. Explore more about federated learning on related NVIDIA technical blogs. And discover the science behind the approach, in this paper.

 

Why Deploying Physical AI at Scale Demands Safety at Every Layer

As autonomous vehicles, robots and other AI-driven machines take on more complex tasks in the physical world, safety must extend across every layer of the system.
by

Physical AI is moving rapidly from research to large-scale deployment. By 2035, ABI Research projects an installed base of 49 million level 3-5 autonomous vehicles (AVs), while Omdia estimates that roughly 60 million industrial robots will be deployed between 2026 and 2035. As these machines enter roads, factories, warehouses and other environments shared with people, safety must scale with them.

Physical AI safety means proving that AI-driven machines — AVs, humanoid robots, industrial robots and more — behave safely when their decisions turn into physical action. That requires safety across the hardware, software, AI, operating environment and deployment lifecycle — not a one-time check before deployment.

Why Is Safety the Key to Scaling Physical AI?

After years of testing and benchmarking, AVs continue to expand commercially. That progress has required developers to demonstrate how automated systems address potential hardware and software failures, limitations in intended functionality and AI-specific risks.

Robotics is approaching a similar inflection point as autonomous machines move into factories, warehouses and other environments shared with people.

Across physical AI, manufacturers, regulators, insurers and workplace safety teams need evidence that hardware, software, AI behavior and operating environments can work together safely without human intervention.

Why Does Physical AI Need a New Safety Model?

Four shifts define new safety standards:

  • Dynamic environments require context-aware safety. Roads, factories and warehouses cannot be fully controlled through static zones or physical barriers. Autonomous systems must perceive changing conditions, adapt their behavior and reach a safe state when something unexpected occurs.
  • AI behavior requires its own assurance. Testing must assess AI software alongside traditional functional safety, using design-time, runtime and validation-time guardrails. Emerging standards such as ISO/IEC TS 22440 are beginning to address these AI-specific risks.
  • Deployment is ongoing. AVs and robots evolve through software and model updates, new tasks and changing operating conditions. Material changes may require additional safety testing.
  • Validation at scale requires simulation and synthetic data. The number and complexity of potential scenarios requires real-world testing to be combined with simulation, synthetic data generation and scenario reconstruction.

Together, these shifts require safety to be operationalized across design, deployment and validation, from the underlying hardware to AI behavior and the operating environment. 

What Safety Foundation Has NVIDIA Built for Physical AI?

Physical AI safety requires specialized engineering, data, processes and validation that few companies can reproduce alone. NVIDIA’s safety foundation draws on more than a decade of development in AV safety, building expertise in functional safety, sensor fusion, AI behavior assurance, vision AI, simulation and real-world validation.

NVIDIA Halos is the first and only full-stack safety system for physical AI, helping developers engineer safety across every layer of design, validation and deployment. The principles are shared across AVs and robotics, while the platforms, standards and evidence remain specific to each domain.

For AV development, Halos spans:

  • Hardware: NVIDIA DRIVE AGX Thor provides safety-engineered accelerated compute, while NVIDIA Hyperion provides the full-stack vehicle platform and reference architecture for level 4 AVs.
  • Operating system and middleware: Halos OS provides a unified software foundation built on ASIL-D certified DriveOS. Halos Core and Halos Middleware support system isolation, monitoring and deterministic communication.
  • End-to-end model: NVIDIA Alpamayo offers open reasoning vision language action models that bring explainability to long-tail scenarios.
  • Simulation and validation: The NVIDIA Halos Safety Evaluation Framework provides tools and guidelines for generating evidence to support AV safety cases across different levels of automation.

Together, these elements connect cloud-based AI development and simulation with in-vehicle deployment so safety evidence can remain traceable across the vehicle lifecycle.

For robotics, Halos spans:

  • Hardware: NVIDIA IGX Thor is an industrial-grade module that combines accelerated computing and functional safety on one platform with a dedicated Functional Safety Island. It’s designed to support systems developed for standards including IEC 61508 and ISO 13849.
  • Software: Halos Core for IGX provides the software foundation for safety-related operating functions, including fault detection,  monitoring and reporting, along with the communication and processing capabilities that connects sensors, actuators and other safety components 
  • Real-time sensing: NVIDIA Holoscan Sensor Bridge connects sensor data with AI and safety-related processing, helping systems identify invalid information and execute defined safety responses.
  • Simulation and validation: NVIDIA Isaac Lab and NVIDIA Omniverse libraries let developers test robot behavior across relevant conditions and edge cases, complementing real-world validation.
  • Outside-in safety: The open source NVIDIA Halos Outside-In Safety Blueprint uses external cameras and vision AI agents to extend awareness beyond onboard sensors and support facility-level monitoring and functional safety use cases.

Across both AV and robotics, the NVIDIA Halos AI Systems Inspection Lab turns safety, cybersecurity and AI safety requirements into repeatable inspections and helps prepare Halos integrations for final system-level certification by third-party agencies.

Who Is Building With the NVIDIA Halos Safety Ecosystem?

NVIDIA Halos connects the companies that build, integrate, assess and deploy physical AI solutions, including product developers, software and embedded-system providers, sensor and silicon companies, safety solution developers and certification bodies.

In autonomous vehicles, Geely, Isuzu, Nissan (powered by Wayve software) and Einride are building level 4-ready vehicles on NVIDIA Hyperion, supported by Halos OS.

Uber, Grab, Lyft and other mobility providers are also using Hyperion to scale robotaxi development and deployment. Members of the NVIDIA Halos AI Systems Inspection Lab include AUMOVIO, Bosch, Gatik, Hesai, Lucid, MIRA, onsemi, PlusAI, Sony, Valeo and Wayve, spanning autonomous-driving development, ADAS, sensors, silicon, systems integration, validation and safety assurance.

In robotics, acontis and QNX provide the embedded software needed to run safety functions predictably, while Advantech and NexCOBOT build safety-designed NVIDIA IGX systems. Infineon, NXP, STMicroelectronics and Texas Instruments contribute sensor, safety-microcontroller and other semiconductor technologies. KION Group is developing functional safety agents for autonomous forklifts. Agility is integrating NVIDIA IGX Thor and Halos Core into the safety system for its Digit 5 humanoid.

How Is NVIDIA Halos Independently Assessed?

For AVs, TÜV SÜD certified NVIDIA’s Automotive Product Lifecycle software process and DriveOS 6.0 to ISO 26262 ASIL D, as well as NVIDIA’s automotive engineering processes to ISO/SAE 21434. TÜV Rheinland also performed an independent UNECE safety assessment of NVIDIA DRIVE AV.

For robotics, TÜV Rheinland is inspecting NVIDIA IGX Thor, Halos OS and Holoscan Sensor Bridge for functional-safety certification readiness, building on TÜV SÜD’s inspection of the Thor SoC and Halos Core for ISO 26262.

Across physical AI, ANAB has accredited the NVIDIA Halos AI Systems Inspection Lab as an ISO/IEC 17020 inspection body. The lab inspects scoped Halos integrations and helps companies prepare for final certification by independent third-party bodies.

The companies that scale physical AI will not simply build the most capable systems. They will build systems that can be assessed, certified, deployed and trusted in the real world. Designing functional safety from the start is what separates a prototype from a scalable solution.

Learn more about NVIDIA Halos for AVs and robotics, and explore the full-stack safety architecture for physical AI.

NVIDIA Alpamayo 2 Super, the Frontier Open Model for Robotaxis and Autonomous Vehicles, Now Available for Commercial Use

Open commercial licensing, benchmark‑leading reasoning and inspectable decisions bring autonomous vehicles, including robotaxis, closer to production and widescale deployment.
by

For robotaxis and other autonomous vehicles (AVs), the hardest problems aren’t the everyday scenarios. They’re the rare, complex situations that are difficult to anticipate and train for.

Handling these long‑tail events takes more than just object detection and motion prediction. AVs must understand the situation, reason about cause and effect, choose the right action and turn that decision into a safe, comfortable path — all in real time and in a way developers can inspect, validate and trust.

NVIDIA Alpamayo 2 Super, available now for commercial use, is part of the Alpamayo family, the most-adopted open reasoning models for autonomous driving on Hugging Face, supporting a wide range of AV-relevant capabilities within a single foundation model. 

Built on NVIDIA Cosmos 3 Super Reasoner and post‑trained with reinforcement learning, the model advances the AV ecosystem on two fronts: open commercial licensing and leading multitask capabilities for autonomous driving. 

Alpamayo 2 Super is part of NVIDIA’s growing collection of open models, datasets and tools for autonomous driving, expanding access, strengthening competition, giving developers greater control and supporting safer, more transparent AV deployment. 

Open Licensing for Production AVs

Alpamayo 2 Super is available on Hugging Face under OpenMDW‑1.1, the Linux Foundation’s permissive license for open AI model distributions. The license covers fine‑tuning, derivative models and commercial redistribution, allowing AV developers, automakers, truckmakers and suppliers to adapt Alpamayo to their own data, driving policies and deployment strategies. 

This openness lets AV researchers and companies keep control of their own data and infrastructure, as well as own the value they create through specialized models and accumulated know‑how. Such control is essential for workflows involving proprietary fleets and safety. 

Earlier Alpamayo releases were initially introduced for R&D. The OpenMDW license is now being  applied across the entire Alpamayo model family so developers can deploy any of the models commercially without requiring additional permissions. This creates a direct path from adaptation to deployment.

Open weights make that path economically viable. Teams can build on advanced reasoning without re‑training every foundation capability from scratch or paying frontier‑model costs for every task, matching the right model to the right job at the right cost. 

Alpamayo 2 Super enables frontier-scale reasoning in cloud-based development workflows, where developers can generate high-quality reasoning traces, synthetic training data and teacher outputs for model distillation. Within the Alpamayo model family, Alpamayo 2 Super delivers the highest reasoning and driving performance for multimodal autonomous driving development, while Alpamayo 1.5 and Alpamayo 1 provide more cost-efficient options for cloud-based development and model distillation.

The resulting distilled models can then be optimized for efficient, real-time inference in production vehicles. Together, the Alpamayo model family provides a cloud-to-car workflow that combines frontier-scale reasoning with scalable deployment across commercial AV fleets.

For AV programs, that means frontier‑scale reasoning in the cloud and efficient, specialized models in the vehicle — a more sustainable way to scale safe autonomy into commercial fleets.

Benchmark-Leading Reasoning at Frontier Scale

Alpamayo 2 Super ranks first on LingoQA, an autonomous driving reasoning benchmark, among nearly 40 models evaluated. In NVIDIA testing using the Lingo‑Judge metric, it outperformed Qwen2.5‑VL 72B by 17.0 points, Gemini 2.5 Pro by 15.1 points and GPT‑4o by 23.2 points, demonstrating state‑of‑the‑art reasoning for driving‑centric scenarios. Alpamayo 2 Super also ranks first across all autonomous driving benchmarks evaluated by NVIDIA, underscoring its leading performance across a broad range of AV capabilities. 

Alpamayo 2 Super offers 3x the scale of the 10‑billion‑parameter NVIDIA Alpamayo 1.5 and Alpamayo 1 models. The added capacity helps the model better generalize reasoning from sparse examples — a critical capability for the rare, multi‑agent interactions where conventional systems often struggle. 

The model reasons over full‑surround camera coverage, fusing views from the vehicle’s front, sides and rear. This 360‑degree context enables richer understanding of lane changes, merges, unprotected turns and complex intersections, where risks commonly arise.

A Multitask Foundation Model for Robotaxis and Autonomous Driving

For each driving situation, Alpamayo 2 Super can produce five tightly coupled outputs:

  • A trajectory describing the vehicle’s planned path.

  • A chain‑of‑causation (CoC) trace that explains the reasoning behind the decision.

  • A meta‑action (e.g., yield, lane changes, stops) that captures the model’s intent.

  • Reasoning auto-labels that generate CoC annotations for training and validation data.

  • Visual question answering responses with 2D visual grounding that link the model’s answers to specific regions in camera images.

Together, these outputs offer insight into the model’s decision-making process. Developers can tie what the model observed to the action it selected, making decisions easier to understand, critique and validate. 

CoC traces integrate with NVIDIA Halos safety‑validation workflows and support AI safety aligned with ISO/PAS 8800 requirements, providing a stronger foundation for AV safety engineering. 

Alpamayo 2 Super can also be deployed as an autolabeler to generate CoC labels and perform visual question answering with 2D grounding on proprietary fleet data. By linking its reasoning to specific regions in camera images, the model can transform raw driving clips into richer training data, compressing annotation cycles from months to days.

Beyond planning and auto-labeling, Alpamayo 2 Super supports scene understanding, model critiquing and knowledge distillation. These multitask capabilities enable developers to use a single foundation model across more of the development stack, simplifying tooling and accelerating iteration.

An Open Ecosystem for Reasoning‑Based AVs

Alpamayo 2 Super is part of a broader family of open models, frameworks and datasets for AV development. 

Other tools in the family include: 

  • NVIDIA AlpaSim, which provides closed‑loop simulation.

  • NVIDIA AlpaGym, which enables high‑throughput reinforcement learning.

  • NVIDIA Physical AI Open Datasets, which supply data for training and testing.

  • Open training recipes and an autolabeling pipeline to accelerate model development, training and validation.

Alpamayo has already surpassed 500,000 downloads on Hugging Face, reinforcing its position as the most-adopted open reasoning model family for autonomous driving on the platform.

Download NVIDIA Alpamayo 2 Super on Hugging Face to explore the model, evaluate its reasoning capabilities and start building the next generation of robotaxis and autonomous vehicles.

For Robotaxis, Safety Must Be Built In, Not Bolted On

by

Editor’s note: The name of NVIDIA DRIVE Hyperion was changed to NVIDIA Hyperion in September 2026. All references to the name have been updated in this blog.

A car pulls up to the curb. The app says, “Your ride is here.” No one’s in the driver’s seat. For people who live in one of the dozens of cities now hosting robotaxi services, this is already a reality.

The robotaxi industry has moved from prototype milestones to commercial operations, with an expanding ecosystem accelerating the pace of deployment. New collaborations announced at NVIDIA GTC Taipei reflect robotaxi programs spinning up around the world:

  • Uber and Autobrains are launching a robotaxi program in Munich on the NVIDIA Hyperion platform, using Autobrains’ agentic AI to support scalable operations. 
  • Foxconn is expanding its collaboration with NVIDIA to deploy robotaxi fleets, combining its services with NVIDIA Hyperion for rapid integration and scaling in Taiwan.
  • VinFast is working with Autobrains to bring level 4 vehicles built on Hyperion to the Southeast Asia market.
  • HUMAIN is working to bring Hyperion-powered robotaxis to Saudi Arabia, expanding the platform’s global footprint into the Middle East.

Building a Safe Software Foundation

As the robotaxi industry scales, safety is paramount.

Regulators, certification bodies and developers are scrutinizing what safe deployment at scale requires. 

Industry discussion on level 4 autonomy often centers on what the vehicle can perceive and decide. 

That discussion is well-founded. Accurate perception, sound decision-making and handling the unexpected are difficult problems, and real progress toward solving them is being made.

But perception and decisions alone are not the whole story. Regulators require something more: proof that the overall system behaves reliably, isolates faults before they escalate and never operates outside the boundaries it was designed for. 

Robotaxi safety requires solving four distinct challenges simultaneously:

  • A safety-certifiable operating system
  • Safe, standardized hardware and software interfaces
  • AI that operates within verifiable guardrails
  • Validation at scale before vehicles touch public roads

To help solve these challenges, the recently introduced Halos Operating System (OS) — a component of the NVIDIA Halos full-stack, comprehensive safety system — offers a unified, production-ready safety foundation for AI-driven vehicles, built on NVIDIA Hyperion. It comprises: 

Halos Core: A Certified OS Foundation

At the foundation of NVIDIA Halos OS is Halos Core, which is the next generation of NVIDIA DriveOS and certified to automotive safety standards. It’s audited, documented and proven to behave predictably under fault conditions, with a hypervisor — a specialized software layer — that isolates safety-critical functions so failures can’t reach vehicle controls. 

Halos Core is compliant with ISO 26262 ASIL D, includes safety-certified support for NVIDIA CUDA and TensorRT, and provides the TensorRT Edge-LLM open source framework for high-performance large language model inference.

Halos SDK: Standardized and Safe Interfaces

A robotaxi integrates cameras, radar, lidar and other sensors, each streaming data in a different format at a different rate. Without a standardized middleware layer, every hardware change forces teams to manually rebuild those integrations. 

Halos SDK removes that burden. Its sensor abstraction layer decouples the autonomous driving stack from individual sensor drivers, so adding or swapping a sensor no longer causes ripples through application code, while a vehicle abstraction layer connects the autonomous driving stack to the rest of the vehicle through a single, consistent interface. 

On top, Halos SDK provides the runtime building blocks that safety-critical software demands: a deterministic application-level scheduler for predictable timing, zero-copy inter-process communication that moves data without added latency, a comprehensive system error-handling framework and a robust scenario data recorder — delivering the foundation for highly reliable and low-latency automotive applications.      

Halos Applications: Safety Guardrails for AI

AI models can match human driving behavior, but regulators require more than performance. 

The Halos Applications layer provides safety guardrails for AI through deterministic, rule-based functions, analyzed and designed to behave within defined bounds. It includes world model perception and the top-rated NVIDIA DRIVE active safety stack featuring automatic emergency braking, lane departure warning, blind spot monitoring, collision warning and more. 

In addition, in Halos Applications, Halos OS can be combined with end-to-end AI models for which explainability and transparency are essential. This includes the NVIDIA Alpamayo family of open models for autonomous vehicle development, which enables chain-of-thought reasoning, continuously evaluating the road, planning next steps and adapting to changing conditions.

The Halos Safety Evaluation Framework

Halos Infra is the cloud-side development infrastructure that enables autonomous vehicle training, simulation and validation at scale. It’s the foundation for the recently released NVIDIA Halos Safety Evaluation Framework (SEF).

SEF provides the tools and guidelines needed to build a credible safety case, from L2 driver assistance to L4 robotaxis. It draws on more than 330 research papers and 1,000 patents developed within NVIDIA Halos OS.

Halos Infra runs on NVIDIA’s three-computer autonomous driving solution: 

Halos OS spans the full development lifecycle — from training and simulation in Halos Infra to inference in the vehicle itself.

Learn more about NVIDIA Halos.