BASSnet is in the middle of the biggest architectural change in its history, and that is the single most important fact for anyone evaluating it in 2026. BASS Software of Oslo has been building maritime fleet management systems since 1997, the suite spans roughly 19 modules on a single database covering maintenance, procurement, dry-docking, HSEQ, audits, inspections, risk, documents, certificates, crewing, payroll and finance, and the installed base has been reported at around 2,000 vessels. In January 2025 BASS launched BASSnet Web 3.0, moving the Foundation and HSEQ modules first onto a cloud-native architecture hosted in Microsoft Azure. In September 2025 the platform was rebranded BASSnet Neo from release 3.0.1, and the latest Neo version was launched at the European Customer Forum in Athens in 2026. That is a genuine modernisation, backed by ISO/IEC 27001:2022 certification, ISAE 3402 Type II attestation and NIST2 alignment. It also means the answer to "is BASSnet cloud-native?" depends entirely on which modules your fleet runs and where those modules sit on the release track. This guide sets out how to establish your own position, which alternatives are worth evaluating, and what the switching maths actually looks like. Start a free trial of Marine Inspection and test a modern cloud PMS against your own equipment register before the transition plan is written for you.
Maritime Fleet Software, 2026
A Platform Mid-Transition Is a Different Buying Decision
When a suite is migrating architecture module by module, your evaluation is not "which product is better" — it is "where does my specific module set sit today, and what does the rest of the sequence cost me."
1997
BASS Software founded in Oslo
19
Modules on a single shared database
Jan 2025
Web 3.0 launch, Foundation and HSEQ first
Sept 2025
Rebranded BASSnet Neo from release 3.0.1
Where Your Fleet Sits on the Release Track
The cloud transition is sequential, not simultaneous. Foundation and HSEQ moved first, further modules follow across subsequent releases, and the Neo name is being applied across web and mobile applications progressively. Establishing your own position on this track is the first task of any evaluation, because it determines whether you are comparing a cloud-native platform or a partially migrated one. Book a Marine Inspection demo to see what a platform built cloud-native from the start looks like as a reference point.
01
January 2025
Web 3.0 Launch
Foundation and HSEQ modules transition to a scalable cloud-based web architecture on Microsoft Azure, using containerised technology with high availability and disaster recovery design.
02
September 2025
Neo Rebrand at 3.0.1
The Neo name is introduced from release 3.0.1 and applied across web and mobile applications progressively, positioned as a fully native cloud suite with AI and analytics rather than a version increment.
03
2026
Athens Forum Release
The latest Neo version launches at the European Customer Forum with innovations across Maintenance, Procurement, Projects and Dry-Docking, HSEQ, Crew Management, automation and integrations, alongside ISO 27001 and NIST2 work.
04
Your Fleet
Position Unknown Until Asked
Get it in writing, module by module: which of your licensed modules are Neo-native today, which are scheduled, which release carries each one, and what the migration costs your fleet in services and downtime.
The Nineteen-Module Question
A single-platform strategy on one shared database is a real engineering advantage: data is entered once and reused across processes, and duplication largely disappears. It is also how a licence quietly grows past the operation it serves. Group your holdings below and count what genuinely gets opened in a normal month. Sign up for Marine Inspection and see what the maintenance and inspection cluster looks like priced on its own.
Technical and Asset
Maintenance and Materials
Procurement
Projects and Dry-Docking
Machinery Library
The core of most fleets' actual daily use. High-level planning, scheduling and execution of a maintenance regime against individual vessels or the entire fleet, with maintenance cost forecasting against jobs, material and resource.
Compliance and Risk
HSEQ
Risk Management
Audits
Inspections
Vetting
Environmental Management
Where regulatory pressure is heaviest and where fleets most often find they are running two systems in parallel, because vetting and inspection workflows drifted into spreadsheets while the module sat licensed but underused.
People and Documents
Crew Management
Payroll
Work and Rest Hours
Electronic Training Record Book
Document Manager
Certificates and Operations
Genuinely valuable where you run crewing and payroll in-house. Largely redundant where a manning agent handles the crew pool and payroll externally, which describes a substantial share of mid-sized commercial operators.
Operations and Platform
Ports Management
Finance
Business Intelligence
Gateway
Ports Management carries port forms with auto-population from other modules and a worldwide port guide updated by replication. Gateway handles third-party file exchange with suppliers, forwarders and external systems, and is the module to interrogate hardest on integration questions.
The Honest Count
If your fleet genuinely operates one cluster out of four, you are running a maintenance and inspection workload on a full maritime ERP. That is a fit question rather than a quality question, and it is the strongest single signal that the wider market deserves an evaluation cycle.
Capability Comparison: Maritime ERP Against Modern Cloud PMS
Both categories claim every feature, so compare where architecture forces a real difference. The final column is the test that settles each line inside a demo rather than a datasheet. Schedule a walkthrough and run these against your own vessel data rather than a vendor sandbox.
Table 1: Maritime ERP Suite Compared With Modern Cloud PMS
| Line | Maritime ERP Suite Pattern | Modern Cloud PMS Pattern | Test in the Demo |
|---|---|---|---|
| Functional scope | Roughly 19 modules across technical, compliance, crewing, finance and operations on one shared database | Maintenance, inspection, defect management, spares and compliance evidence only | Price only the modules you would genuinely operate in year one |
| Architecture status | Mid-transition, with modules moving to cloud-native across sequential releases | Cloud-native since inception, with no legacy client and no migration sequence to track | Get a written module-by-module statement of what is Neo-native today |
| Crew working model | Mobile applications available, with replication between vessel and shore across modules | Full create, edit and submit offline on phone or tablet, syncing on reconnection | Airplane mode, close a job with photos, reconnect and watch the sync resolve |
| Hosting and security | Microsoft Azure with containerisation, zero-trust security, ISO/IEC 27001:2022, ISAE 3402 Type II and NIST2 alignment | Multi-tenant cloud; certification varies sharply by vendor and must be treated as a hard requirement | Request current certificates and the most recent penetration test summary |
| Time to first value | Commonly 6 to 15 months across configuration, database building, migration, integration and training | Roughly 6 to 12 weeks, and 6 to 10 weeks for five to eight vessels with usable records | Request a phased plan with named milestones, not an average timeline |
| Commercial model | Custom quotation by fleet, module and user; multi-year terms typical; services quoted separately | Published per-vessel or per-user subscription with the module set fixed at signature | Ask for year-one and year-three totals in writing, services included |
| Integration | Dedicated gateway module handling file exchange with suppliers, forwarders and third-party systems | Documented API access, typically inside the subscription | Name your finance and telematics systems and ask for a working reference |
| Class and ISM evidence | Class-neutral, with maintenance regime execution and cost tracking against jobs, material and resource | Class-neutral, with certificate windows, survey due dates and audit trails native | Generate the ISM Element 10 evidence pack live from your own data |
| Migration services | Vendor teams offer extraction, conversion and standardisation of PMS data from third-party systems including historical job data | Standard extract, cleanse, map and validate cycle, usually inside onboarding | Ask for a completed migration reference off your specific incumbent |
2026 EVALUATION REALITY
The regulatory floor is platform-independent. ISM Code Element 10 requires every company holding a Document of Compliance to run a documented maintenance system, and SOLAS Chapter IX makes ISM mandatory for SOLAS-certified ships, so passenger ships, cargo ships of 500 GT and above and mobile offshore drilling units are all in scope whichever software they run. IACS formalised PMS requirements in 2001, and Bureau Veritas, DNV, Lloyd's Register and ABS approve owners' systems and conduct the initial survey. Neither BASSnet nor a modern cloud PMS carries a class affiliation, so unlike some competing suites there is no society-specific advantage to weigh on either side of this particular comparison. Roadmaps move faster than buyer guides. Release positions cited here are from public announcements; confirm current module availability and version support horizons directly with the vendor before planning around any of it.
Compare Against a Platform With No Migration Sequence to Track
Equipment registers, interval and running-hour triggers, defect-to-work-order closure, spares, certificate windows and class survey dates — cloud-native from the first release, with true offline capture on any device and fleet-wide visibility from one dashboard.
Total Cost Across a Transition Year
A platform mid-transition has one cost line the others do not: the migration itself, which lands whether you stay or leave. Market analysis puts unlisted items at 20 to 40 percent of first-year total cost of ownership when they are not surfaced before signature, and professional services alone commonly add 20 to 30 percent in the enterprise tier. Start a free trial to see per-vessel pricing applied to your fleet without a custom-quote cycle.
Table 2: Cost Lines, Typical Patterns and the Question That Surfaces Each
| Cost Line | Maritime ERP Pattern | Cloud Subscription Pattern | Put This in Writing |
|---|---|---|---|
| Architecture migration | A cloud transition is a project regardless of vendor loyalty, with services, testing and training per module wave | None, because there is no legacy architecture to leave behind | Total transition cost per module across the full sequence |
| Module accumulation | Each module licensed separately; capability you assumed included may sit in a module you do not hold | Defined module set at a published price point | Itemised price per module, and the renewal cost of dropping one |
| Database building | Consultation, implementation, database building and training offered as a professional service | Bundled or a fixed onboarding fee | Fixed-fee ceiling for go-live across the whole fleet |
| Integration builds | Gateway-based exchange with third-party systems, typically scoped per connector | Documented API access, usually inside the subscription | Is API or gateway access included at our tier, or behind an upgrade? |
| Crew turnover | Per-user training repeated as crews rotate every few months, and again after each module wave | Role-based onboarding and in-product guidance for new joiners | Retraining cost for a full crew change on a single vessel |
| Parallel running | Old and new architectures maintained together during transition windows | Single environment throughout | How many months of dual licensing does the sequence require? |
| Contract exposure | Multi-year terms with uplift at renegotiation and early termination provisions | Annual or monthly terms at published rates | Contractual cap on annual increases |
Migration Risk Register
Whether you migrate within the vendor or away from it, the risks are the same ones. BASS's own guidance on maritime PMS data migration cites Gartner and Bloor Group findings that 80 to 83 percent of migration projects either fail or exceed budget and schedule, and maritime migrations are harder than most because every vessel carries its own operational history. Plan against the register rather than the optimism. Book a walkthrough and pressure-test each mitigation against a real vendor.
Historical job data lost or degraded in transfer
Scope years of history in the contract, not the proposal. Legacy formats rarely align with modern structures, so require extraction, cleansing, standardisation and a validation review with a superintendent and a chief engineer before go-live.
Equipment naming inconsistent across vessels
Standardise component naming during the audit phase rather than after. Carrying a decade of inconsistent records into a new platform reproduces the same problem at a new price. A shared machinery library across the fleet is the structural fix.
Crew adoption stalls after cutover
Train during cutover, not after. Training crews who are already behind on work orders produces workarounds. Set a firm read-only date on the legacy environment, because a writable old system keeps part of the crew on it indefinitely.
Integration to finance or telematics breaks
Review gateway or API documentation before contract, then pilot one live integration before fleet rollout. Name your specific finance and telematics systems and require a working reference rather than a roadmap commitment.
Module wave sequence slips against your plan
Where a suite migrates architecture module by module, the modules you depend on may not be first in the queue. Get the sequence and target releases in writing, and build contingency for at least one wave arriving later than announced.
Vetting or charter position weakens during transition
Maintain both environments through the transition window so inspection and certificate evidence is never unavailable to a vetting inspector or PSC officer. Confirm contractual data portability and open-format export before signature.
Frequently Asked Questions
Is BASSnet cloud-native or on-premise?
Both, depending on release and module. BASS launched BASSnet Web 3.0 in January 2025, transitioning the Foundation and HSEQ modules to a cloud-based web architecture hosted in Microsoft Azure with containerised technology. In September 2025 the platform was rebranded BASSnet Neo from release 3.0.1, with the name applied progressively across web and mobile applications. Further module innovations were announced at the 2026 European Customer Forum. The practical answer for your fleet depends on which modules you license and which release you sit on, so request a written module-by-module statement rather than relying on a general positioning claim.
What are the main alternatives to BASSnet in 2026?
Alternatives group into tiers rather than a ranked list. Full maritime ERP suites integrate technical, commercial, crewing and financial management on one data model. Established maritime PMS specialists offer comparable maintenance depth with per-vessel licensing and shorter implementations. Modern cloud PMS platforms including Marine Inspection are mobile-first with offline vessel working, published pricing and deployment measured in weeks. Generic industrial CMMS products suit shore facilities and shipyards but typically lack Continuous Machinery Survey logic and ship-to-shore offline sync. Identify the tier that matches your fleet size and operating pain before comparing individual products inside it.
Should we migrate to Neo or evaluate the market first?
Do both, in that order. A transition is the one moment when the cost of staying and the cost of leaving are roughly equal, which makes it the cheapest time to run a genuine comparison. Ask for the Neo migration plan, sequence and total cost in writing, then run a parallel evaluation of one modern cloud PMS on a single vessel. If you operate three or four module clusters daily, the suite will almost certainly win on integration. If you operate one, the comparison will tell you something useful that a renewal conversation never will.
Can BASSnet data be migrated to another platform?
Yes. Maritime PMS migration between systems is established practice, and vendors on both sides of this market publish experience migrating and converting PMS data from third-party systems including historical job data with cleaning and standardisation. Establish in the contract how many years of history are included, who owns the cleansing work, and what the export path looks like if you leave the new platform later. Treat data lock-in as a commercial negotiation rather than a technical barrier, and require contractual data portability with open-format exports regardless of which direction you move.
How long does a move to a cloud PMS take?
For five to eight vessels with reasonably complete records, roughly six to ten weeks covering data audit, extraction and cleansing, single-vessel pilot, crew training and phased rollout. Enterprise implementations more commonly run 6 to 15 months including database building, integration and training. Data quality moves the timeline far more than software does. Run one vessel in parallel for a full cycle before committing the fleet, train crews during cutover rather than after it, and retire the legacy environment on a firm date once evidence continuity is confirmed.
Run the Comparison While the Switching Cost Is Symmetrical
A transition year is the cheapest moment to test whether a full maritime ERP still fits your operation. Marine Inspection gives chief engineers and superintendents a complete digital PMS with equipment registers, interval and running-hour triggers, spares, certificate windows and offline mobile capture — deployed in weeks, priced per vessel, with no module sequence to wait on.
