What the end of ROS 1 support means for your robot, and how we will help you get there
From April 1st, 2026, official support for PAL Robotics robots will move exclusively to ROS 2. If you are currently operating a PAL Robotics robot on ROS 1 Noetic, this change affects your software support coverage, this page contains everything you need to understand what it means and what to do next.
This change reflects the broader shift in the robotics ecosystem, and what it means for the support and reliability your robot receives. This migration is designed to ensure long-term reliability, security, and performance for research and professional applications.
End of support for ROS 1
ROS 1 (including ROS Noetic on Ubuntu 20.04) reached its official end of life in May 2025. As the robotics ecosystem evolves, continuing to build meaningful, secure support on top of an unsupported software foundation would ultimately put your robot’s reliability and security at risk. Moving to ROS 2 is the responsible path forward for your work as much as ours.
For this reason, systems running on ROS 1 will no longer be covered by Official Support from PAL Robotics after March 31st, 2026.
What is changing and when?
- What changes: official ROS 1 support ends
- When: March 31st, 2026
- Who is affected: users currently operating on ROS 1
- Who is not affected: users already on ROS 2
What this means for you
If you are still on ROS 1, you still have time to plan your migration before the April 1st deadline. Here is what we recommend:
- Review your current robot configuration and ROS version
- Get in touch with our team — we will review your setup, identify any compatibility considerations, and define a migration path that fits your timeline
- We will support you through the process to minimise disruption to your ongoing work
Migration complexity varies depending on your setup. Our goal is to make this as straightforward as possible – We don’t leave working robots behind.
Migrating to ROS 2 entails several benefits for the future of your work. Robots operating on ROS 2 will continue to benefit from:
- Official technical support from PAL Robotics
- Active maintenance within the global ROS community
- Alignment with the current robotics software standard
- Access to new packages, performance improvements and future capabilities
- A software architecture designed for long-term scalability
This transition ensures that PAL Robotics platforms remain compatible with the latest tools, frameworks and integrations developed within the broader robotics ecosystem.
Why ROS 2?
ROS 1 has had a remarkable run. For over a decade it was the backbone of robotics research and development worldwide, and it powered some genuinely groundbreaking work, including a lot of what our community has achieved with ARI, TIAGo, and our other platforms.
ROS 2 is not simply a newer version of the same thing. It was built from the ground up to address the demands of modern robotics, ROS 2 introduces significant architectural improvements such as:
- Real-time communication capabilities
- Enhanced reliability and distributed system performance
- Built-in security features
- Improved support for multi-robot systems
- Long-term ecosystem sustainability
These foundations are essential for advanced mobile manipulation, autonomous navigation, human-robot interaction and industrial deployments. Consolidating our software stack around ROS 2, means your robot stays compatible with the tools, frameworks, and integrations the broader robotics community is actively developing now and into the future.
Planning your migration
If your robot is still running on ROS 1, we want to help you plan your migration. Our team will work with you to review your current configuration, identify compatibility considerations specific to your setup, and define a migration with a timeline. Our goal is to make the transition as smooth as possible while minimizing disruption to ongoing work.
If you would like guidance or want to discuss your specific case, please contact our team.
ROS 1 EoL FAQs
We don’t leave any robot behind. Find the answers to the frequently asked questions about ROS 1 End of Life and what it means for you.
What does “Official Support” include? Will I still get hardware maintenance on my robot?
Yes, hardware maintenance for all PAL Robotics robots continues as normal and is not affected by this change.
What is changing is software support for ROS 1 specifically. From April 1st, 2026, we will no longer be adding fixes or new features to the ROS 1 stack. All software development, bug fixes, security updates, and new features will be delivered exclusively through ROS 2 from that point onwards.
What happens to my contract or SLA?
Your contract and SLA remain in place and are not affected by this change. If your contract was signed within the last three years, a software upgrade to ROS 2 is already included in your service agreement. If you are unsure what your contract covers, please get in touch and we will walk you through it.
Can I still open tickets and request customer support?
Yes, absolutely. Our support team remains available to you through our regular support channel. Please visit our support page to open a support ticket.
What does “running on ROS 2” mean, and which ROS 2 baselines are supported?
Running on ROS 2 means your robot’s software stack is built on the ROS 2 middleware, which is the current standard for robotics development. The supported baseline for PAL Robotics robots is ROS 2 Humble on Ubuntu 22.04, which will be available from the March 2026 release (version 26.03) onwards.
What if I keep my robot in ROS 1?
Your robot will continue to function as it does today. Keeping it on ROS 1 does not affect the robot hardware or your ability to use it.
However, from April 1st, 2026, we will no longer be able to make any changes to the ROS 1 software stack, at either the middleware level or in PAL’s proprietary tools. This means no new features, no bug fixes, and no security updates will be delivered for ROS In practice, issues that arise on ROS 1 after that date will be solved by migrating to ROS 2.
Does PAL Robotics support ROS 1 to ROS 2 bridging?
Bridging between ROS 1 and ROS 2 without a full migration is technically possible, but this option falls outside the scope of PAL Robotics Official Support coverage. We recommend a full migration to ROS 2 to ensure continued support and the best long-term outcome for your work.
What will happen to the software packages or hardware I got with the robot in ROS 1?
The migration to ROS 2 involved a thorough revision of the software architecture. Most of the functionalities available in ROS 1 have been maintained in ROS 2, but some premium software packages do not have a direct equivalent in the new stack.
Hardware compatibility may be affected in cases where third-party drivers are not yet available for ROS 2. If you are unsure whether a specific package or hardware component is supported in ROS 2, please get in touch and we will give you a clear answer for your specific setup.
What do I need for a successful porting to ROS 2? How long will the process take?
The migration is carried out by installing a new ISO provided by PAL Robotics, which gives you a fully operational robot running on ROS 2. To get started, contact our team and we will provide you with the ISO and the necessary installation guidance.
Migration time will vary depending on your setup and how much custom development has been done on top of the base system. We recommend getting in touch as soon as possible so we can give you a realistic picture for your specific case.
How will PAL Robotics support the process?
We provide a dedicated ISO that enables a full transition to ROS 2, giving you a fully operational robot on the new stack. Our support team is available to help you get set up and answer questions about the installation process.
Development work and the migration of custom code or third-party integrations falls outside the scope of our support offering. If you have specific questions about what is and is not covered, we are happy to discuss your case directly.
Can I get a support extension while I complete my migration?
We understand that migrations take time, and we will try to honor all support requests. However, we are not able to introduce fixes or new features into the ROS 1 stack beyond the March 31st, 2026 deadline, regardless of migration status. The best way to protect your continuity of support is to begin planning your migration as soon as possible. If you are concerned about your timeline, please reach out and we will do what we can to help you move forward.