Blue Robotics sells subsea components, BlueROV2 vehicles and BlueBoat surface platforms, with open software and a partner ecosystem that extends their commercial uses.
Blue Robotics supplies the building blocks of marine robotics as well as complete platforms. Its range includes thrusters, underwater electronics and sensors, the BlueROV2 remotely operated underwater vehicle, and the BlueBoat uncrewed surface vessel. Open software, documented interfaces and third-party products are important parts of the commercial proposition alongside the hardware.
The company is relevant to defense industry readers even when a particular product is being used for civilian research or inspection. A marine technology supplier can encounter Blue Robotics as a component source, a platform on which to develop a specialised product, or equipment used by a service provider. Understanding those positions is more useful than assuming the company sells only one finished underwater vehicle.
Blue Robotics identifies itself as a privately held company headquartered in Torrance, California. Its public company profile dates its founding to 2014. The reviewed sources do not disclose an ownership table, current exact headcount or absolute annual revenue.
A June 2016 announcement identifies founder Rustom “Rusty” Jehangir and describes the launch of BlueROV2. It explains how the vehicle brought together products the company had already developed, including underwater thrusters, pressure enclosures, sensors and lights. That history is important: the complete vehicle grew from a component business, rather than replacing it.
The launch also positioned the vehicle for universities, research organisations, smaller businesses and first responders. Those were stated target users, not a list of confirmed purchases. The contemporary product range continues to show the same combination of individual components and systems that customers can build upon.
Blue Robotics should be distinguished from Bluefin Robotics, a different underwater robotics business, and from similarly named industrial automation companies. Matching the legal and commercial identity matters when comparing contracts, employee records or ownership information.
BlueROV2 has retained its product name through successive changes. In a September 2021 update, Blue Robotics described the R3 revision and earlier improvements to components and accessories. The significance for a commercial user is continuity of a product family alongside evolving hardware.
A long-running name can simplify recognition, but it does not mean every installed unit is identical. An inspection provider considering upgrades or a supplier developing an accessory needs to establish the relevant revision and support arrangements. That is a product-management issue rather than a reason to treat older equipment as interchangeable with a current configuration.
The company’s component catalogue also means customers can buy a subset of its technology without purchasing BlueROV2. For other manufacturers, the opportunity can be incorporation into a separate product. For service businesses, the opportunity is using an available vehicle as the basis for a more specialised inspection or survey offering.
The BlueBoat product page presents a surface platform for hydrographic surveys, scientific work and robotics development. Its purchase configuration separates the base package from options such as a control station, controller, communications accessories and sonars. That makes the difference between a base platform and a complete application package visible.
A buyer comparing prices therefore needs to compare the selected equipment and intended output. A surface vessel without a survey sensor is not economically equivalent to a ready-to-use survey package. Nor does purchasing the platform automatically provide the specialist processing or reporting that a survey customer may require.
This distinction helps explain where partners can add value. They can combine the base vessel with a particular sensor, application software and customer support. Blue Robotics supplies part of that system, while the integrator may be responsible for making the whole purchase useful to a specific customer.
BDI’s Exail civil autonomy adoption analysis provides a comparison with a different marine platform and customer relationship. The useful comparison concerns procurement scope and repeat use, rather than the headline price of unlike vehicles.
Blue Robotics’ open-source portfolio identifies BlueOS, the Cockpit interface and contributions to ArduPilot. It describes BlueOS as an open-source, browser-based operating system with an extensions mechanism, and Cockpit as a configurable control interface. The company also identifies itself as lead maintainer of ArduSub.
For an integrator, those software choices can make adaptation and participation easier to assess. A product developer can examine the public software ecosystem and determine which functions belong to the underlying platform and which would need additional work. The existence of open software does not eliminate the need for engineering, maintenance or responsibility for a customer’s final system.
Commercially, this supports a market in additions around the core products. An accessory manufacturer or software provider can build a proposition that complements the vehicle. The customer then needs a clear support relationship across the original equipment, the added product and any integration performed locally.
The Reef is Blue Robotics’ curated collection of other companies’ products. The page lists examples including Cerulean sonar, an Outland Technology power supply and Water Linked equipment. Blue Robotics describes evaluating and integrating products before offering them through the collection.
This is a concrete route to market for complementary technology. A supplier is reaching an audience already considering marine robotics equipment and can be presented in the context of compatible systems. Blue Robotics, in turn, can address applications requiring products it does not manufacture itself.
The arrangement does not establish that every third-party item is suitable for every customer or operating environment. Its commercial value lies in reducing the distance between a component catalogue and a usable package, while retaining distinct responsibilities for the underlying products.
The wider subsea supply chain includes companies with different levels of integration. The Kraken Robotics profile offers context on sensors, equipment and services at another point in that market.
Blue Robotics’ distributor page describes authorised partners providing regional sales guidance and support. Some develop accessories and additions around BlueROV2 and BlueBoat. The company’s partner categories separately recognise distributors, marine service providers, research users and operational partners.
That separation is commercially helpful. A distributor sells equipment and may help configure it. A service provider uses equipment to deliver an inspection or survey. A research collaborator can contribute to a future product without becoming a reseller. These relationships generate different forms of demand for Blue Robotics and different responsibilities towards the final customer.
Its custom-development pathway is also bounded: the company describes adapting existing products or collaborating on new products, rather than accepting every request for a wholly bespoke system. That gives prospective partners a clearer indication of where their project might fit.
Ocean Discovery League’s DORIS project provides a specific collaboration beyond the existing vehicle catalogue. The organisation identifies Blue Robotics as a development partner for a lower-cost deep-ocean imaging system, supported in part by NOAA funding. The project combines instrument development with the ambition to widen access to ocean research.
An April 2026 workshop in Hawaii brought the system into a documented training setting. Ocean Discovery League names Blue Robotics engineers among the facilitators and describes participants becoming eligible to apply for system loans. That is evidence of user engagement and an early deployment pathway, rather than proof of commercial volume sales.
The project page identifies 2027–2028 as a target for scaling a second-generation product and gives a target base price, both of which remain forward plans. Its importance to Blue Robotics’ profile is the role its engineering and supply chain can play in turning research equipment into a repeatable offering.
Blue Robotics’ market position rests on that broader pattern: components become vehicles, vehicles support complementary products, and partners turn those products into useful services or new research tools. Future milestones are most informative when they identify which part of that ecosystem is expanding and what customers actually receive.
Public company product, software and partner pages and Ocean Discovery League project records were readable. Ownership status comes from the public company-authored profile. DORIS pricing and 2027–2028 commercialisation are targets. No current exact employee total or annual revenue verified; LinkedIn bands and third-party historical sales figures were not converted into company metrics.
Suggest a correction