Carus Ab Ltd.
Finland · owned by Independent (Finland) · carus.com · 12 vendors
Carus Ab Ltd. is a global supplier of IT solutions for the ferry and cruise industry, offering software for reservation, ticketing, port automation, onboard sales, and business intelligence. Their flagship product, CarRes, is a mission-critical integrated system serving passenger vessel operators across 18 countries on 4 continents. The company processes over 33 million passengers and 5 million vehicles annually through 35 shipping, ferry, and cruise operator clients.
Resilience scores
- Digital Sovereignty: 8
- Digital Resilience: 8
Disruption prediction
Carus Ab Ltd. has an estimated 10% probability of disruption in the next 6 months.
7 of Carus Ab Ltd.'s 12 vendors monitored for disruptions.
Technology vendors
- Google LLC — Technology — United States
- The Apache Software Foundation — Technology — United States
- Zendesk, Inc. — Technology — United States
- and 9 more
Services catalogue
3 services in catalogue across 3 categories; runs on 12 sub-vendors.
- Business intelligence
- Port automation
- Reservation system
Insights
Last updated 2026-08-10 · revision 1
12 direct vendors, 180 subvendors
Direct vendors by controlling owner country (sample)
- Germany: 1
- United States: 8
- Australia: 1
Subvendors by controlling owner country (sample)
- France: 6
- Norway: 1
- United States: 133
Migration Readiness: 5/10
Assessed by AI based on technology stack characteristics (cloud-native vs legacy, containerization, microservices), regulatory environment, data residency requirements, financial stability, and vendor lock-in risks. The score ranges from 0-10, where higher scores indicate better readiness for technology migration.
Carus Ab Ltd.'s migration readiness is assessed as medium, largely influenced by critical unknowns and significant regulatory/data residency constraints. The most significant positive factor, if interpreted literally, is "Total Vendors: 0", which would mean no external vendor lock-in. This absence of vendor dependencies would greatly simplify migration planning and execution, offering maximum flexibility. However, this contradicts other vendor-related information provided. The primary challenge to migration readiness is the complete lack of data on the internal tech stack (e.g., cloud-native adoption, containerization, microservices). Without this information, it's impossible to determine the architectural complexity and effort required for migration, which could range from straightforward to highly challenging if legacy systems are in place. Additionally, the company faces strict data residency requirements, with servers primarily in the European Union and potential transfers outside the EEA. This necessitates careful planning for cloud region selection and compliance, potentially limiting cloud provider options and increasing migration complexity. The applicability of NIS2 also adds a layer of regulatory scrutiny, requiring robust security and resilience measures to be maintained or enhanced during any migration, further complicating the process. The absence of financial stability data also means the ability to fund a potentially large migration project is unknown.
Financials
Signed-in users can see whether their own company is exposed to this vendor's disruption, plus the full sub-vendor list and country breakdowns, every in-scope compliance framework plus gaps and next steps, and alerts when any of it changes.