Skip to content
Test page This is a test landing page. It is not indexed and submitted data may be deleted.
Hopover / ROS 1 to ROS 2 migration audit
In development · Early access

Know what your ROS 2 migration will take.

Hopover scans your catkin workspace locally — packages, dependencies, custom messages, launch files, build files and API usage — and returns a per-package effort report and a phased migration plan for ROS 2 Humble or Jazzy.

Join the waitlist Pre-order — €490
Free to join No spam €490 one-time at launch

Problem01 / 07

Why it hurts today

  1. P-01

    Noetic reached end of life on 31 May 2025. Upstream no longer ships bug fixes, security updates or new binaries, so every month on ROS 1 is a month on an unmaintained stack — or a paid extended-support subscription.

  2. P-02

    Nobody can say how big the job is. The official guide is clear that every dependency must exist in ROS 2 before a package can move, but finding out which ones do means walking dozens of package.xml files by hand.

  3. P-03

    Estimates come late and expensive. Consultancies scope migrations project by project, and the scoping itself takes senior engineering time before anyone writes a line of rclcpp.

Solution02 / 07

What Hopover does

  • Dependency map, per package

    Every dependency checked against the target ROS 2 distribution: released, renamed, replaced or missing — so blockers show up before the first sprint, not in the middle of it.

    B-01

  • Effort report you can defend

    Counts of what actually has to change in each package — roscpp/rospy calls, parameters, launch files, custom .msg/.srv, catkin build logic — rolled up into an effort estimate with the assumptions written out.

    B-02

  • A plan in the right order

    A phased migration order that follows your dependency graph, flags what can run behind ros1_bridge in the meantime, and separates mechanical work from redesign.

    B-03

Process03 / 07

How it works

  1. Step 1: Run the CLI

    Point it at your catkin workspace. It parses manifests, CMakeLists, launch files, interfaces and source locally.

  2. Step 2: Review the manifest

    It writes a readable manifest of names, dependencies and counts. You inspect it before anything leaves your machine.

  3. Step 3: Upload the manifest

    Choose ROS 2 Humble or Jazzy as the target. The manifest is matched against that distribution's released packages.

  4. Step 4: Get the report

    A per-package effort report and a phased migration plan, as PDF and Markdown, ready to put in your backlog.

Audience04 / 07

Who it's for

  • Robotics companies with a product or fleet still running ROS 1 Noetic or Melodic
  • Engineering leads who need a migration estimate and budget before committing a team
  • University and research labs with years of catkin packages and a few students to port them
  • Integrators and consultancies scoping ROS 2 migrations for their clients

Pricing05 / 07

Simple, early-customer pricing

Hopover is in development. Join the waitlist for free and we’ll email you when it’s ready.

Want to lock in the founding price? Pre-order today. If we don’t launch, you get a full refund. See the pre-order terms.

Founding migration audit

Early access

€490 one-time

One workspace, one report. Founding price for the first teams on the waitlist. Pre-orders are charged upfront and fully refunded if Hopover doesn't launch.

  • One catkin workspace, any number of packages
  • Dependency status against ROS 2 Humble or Jazzy
  • Per-package effort report with stated assumptions
  • Phased migration plan following your dependency graph
  • Custom message, launch file and build-system inventory
  • One re-run after you've fixed the first blockers
  • A call with the engineers building it to walk through the plan
Pre-order — €490 · €490 Join the waitlist instead

Secure checkout by Stripe. Full refund if Hopover doesn’t launch. Terms.

FAQ06 / 07

Questions, answered

Q01 Does my source code leave my machine?

No — that's the design we're building. The CLI runs locally and writes a manifest: package names, dependency lists, file counts and counts of API calls per package. No source code, no file contents. You can open the manifest and read it before you choose to upload it. This is planned behaviour for a product in development; we will publish exactly what the manifest contains before anyone runs it.

Q02 Does Hopover port the code for me?

No. It tells you what has to change, where, and in what order, and estimates the effort. The porting is done by your team (or whoever you hire). Tools that rewrite code exist, but they get you part of the way at best; the hard decisions — redesigning nodes, replacing missing packages, QoS — still need an engineer.

Q03 How accurate is the effort estimate?

It's an estimate, not a quote. It's built from what we can count in your workspace and assumptions we write out in the report, so you can adjust them to your team. Things we can't see — hardware drivers you don't have the source for, test coverage, how well the team knows ROS 2 — are listed as open risks rather than guessed.

Q04 Which ROS versions are supported?

Source: ROS 1 catkin workspaces, starting with Noetic, then Melodic. Target: the ROS 2 long-term-support releases Humble (supported to May 2027) and Jazzy (supported to May 2029). Other targets on request.

Q05 Why not just buy extended support for Noetic?

That's a valid option, and for some fleets it's the right one. Paid extended security maintenance buys time; it doesn't move you to ROS 2. Many teams will do both: keep deployed robots covered while they plan the migration. Hopover helps with the second part.

Q06 Are you affiliated with Open Robotics or the ROS project?

No. Hopover is an independent tool built for ROS users. ROS is a trademark of Open Robotics; we use the name only to describe what the tool works with. We are not endorsed by Open Robotics, the Open Source Robotics Alliance or the ROS project.

Q07 When will it be available?

Hopover is in development. We'll run the first audits with a small group of teams from the waitlist, then open it up. Join the waitlist and we'll email you when a slot opens.

Q08 Can I pre-order, and can I get my money back?

Yes. A pre-order charges the founding price (€490) upfront. If Hopover doesn't launch, you get a full refund, and you can ask for a full refund at any time before delivery, for any reason; we process refunds within 14 days.

Access07 / 07

Get an early audit

We're running the first audits with a small group of teams. Leave your work email and we'll contact you when a slot opens.

Questions? hello@holtrane.com

No spam. One email when there is something to show. Unsubscribe any time.