














































Gruppo IB, founded in 1983 in Rapallo near Genoa, built asset management software for industry and shipping. Its maritime business came under Arribatec in 2020 as Arribatec Marine, and in March 2025 STAR Information Systems acquired it, so the product is now sold as Infoship under the STAR brand. Infoship is a web-based fleet technical management suite that ship managers use for planned maintenance, defect tracking, spare parts across ships and warehouses, purchase requisitions and QHSE. IB's industrial EAM, InfoPMS, is a separate product. A predictive maintenance product reads vessel equipment and open work orders through Makini's Unified API, where the connection exposes them, so an alert on a main engine or pump refers to the component record the technical team uses. Where the connection permits writes, it can raise a work order in Infoship instead of sending an email. Inventory optimization tools compare spare-part stock across vessels and warehouses with open purchase orders, and OEM suppliers can review the equipment they supplied to plan parts and service. The customer signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. Infoship can run on a central cloud database or on ship-to-shore synchronization, and in the second case shore data may lag behind onboard records. First confirm which IB product and deployment the customer runs.
Have any questions? We’re here to help You
Some editions of Gruppo IB expose an API, but it is often limited, legacy, or inconsistent between versions, and many on-prem deployments have no usable API at all. Makini gives you one modern REST API for Gruppo IB that lets you read and write Gruppo IB data, even for legacy or on-prem instances. You build against Makini once instead of integrating with Gruppo IB directly.
You integrate Gruppo IB through Makini's Unified API. Authenticate once and Makini normalizes Gruppo IB data into a single consistent schema you can read from and write to inside your product. The same connection reaches Gruppo IB plus 2,000+ other ERP, WMS and CMMS systems, so you build one integration instead of one per system.
Through Makini you can read and write Gruppo IB's core records as normalized, standardized resources, in both directions: pull data out of Gruppo IB and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across Gruppo IB and every other connected system.
Days, not quarters. Because Makini already builds and maintains the Gruppo IB connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing Gruppo IB data through the Unified API, typically within a few days. A Gruppo IB integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to Gruppo IB over encrypted connections on SOC 2 Type II certified infrastructure, and handles Gruppo IB credentials for you so they are never exposed to your app. You authenticate once, and access runs through Makini's managed, auditable layer. The same security model applies across Gruppo IB and every other connected system.
Makini owns the maintenance. When Gruppo IB changes its API, versions, or endpoints, Makini updates the connector, and your integration keeps working with no changes on your side. You get a stable Unified API with webhooks, and Gruppo IB upkeep stays off your roadmap.
