The office, the fleet and every ship. One secure system.

Why this is different — the whole site in ten lines.

This page is long because the platform is. If you have five minutes, these ten points are the argument; each links to the part that proves it. If you have forty-five, the bottom of the page tells you how to see it running on your own ships.

Software people open because they want to. Try it.

Fleet software has a reputation: grey, modal, three clicks from anything. This is the other kind — keyboard first, nothing reloads, and what you need next is already on the screen you are on. The one below is not a picture. Click a defect, open its dock, search, change the ships in scope.

// Live demo · five modules, one frame

Try: search record dock chat notifications reset

Sample data, real behaviour — the scope chip, the facets, the palette and the dock all work. Drawn in the browser, and it repaints with the accents below. The real screens are further down the page. On a phone, swipe the frame sideways.

What people actually see.

The demo above is drawn. These are the screens themselves, captured from the platform on a demo fleet — one modern interface on Mac, Windows, iPad, iPhone and the web, the same board, filters, search and export on each.

Every user is different. So is their screen.

A crewing manager, a technical superintendent and a managing director do not want the same first screen, the same colours or the same type size. Here the dashboard is built per department and per person, and the look of the whole platform is each user's own setting: light, dark or system; seven accents; four type sizes. Change the accent here and watch this page move.

One system, because three systems never agree.

Most fleets run crewing in one place, maintenance in another and purchasing in a third, then spend the week reconciling them. SlashPrime keeps one record per ship, per person, per order — and every module reads it.

The ship runs the same system — and it knows what it owes today.

Most "vessel modules" are a form the office asks the ship to fill in. This is the ship's own screen: it opens on what is due today for the rank at the keyboard, what is late, what is coming in the next fortnight, and what the office is waiting for. Every tile on it is the same module the office uses, scoped to this ship.

Every ship carries its own copy, and it syncs itself.

Satellite links drop and VSAT is metered, so every ship runs her own copy of the system, holding only her own slice of the data, and keeps herself in step with the office by herself. Nobody on board exports anything; nobody ashore imports anything. No third-party sync licence.

The safety management system stops being a folder.

On most ships the SMS is a shelf of manuals, a tray of printed forms and a spreadsheet that says which ones came back. Here every controlled form of your SMS — imported from your Word and Excel originals — is an interactive form on screen, filled and signed where the work happens. Filled as a form or done inside a module, it files one receipt into one ledger, and the register knows.

Risk assessed before the work, not filed after it. Ask for the job, not the form number.

Every inspector now asks the same question: show me the risk assessment for this job — and show me the jobs that should have had one. Here the library by department, the assessments carried out and the jobs, permits and drills that still need one are three tabs of one module. Nobody on deck thinks in form codes; pick the job and the picker hands over the permit, the risk assessment and the checklist that belong to it, attached to the work order.

Compliance that schedules itself. Rules you edit, not release.

Every workflow below is driven by a table you can open, not by code someone has to release. Change who approves above fifty thousand, add a step to the new-joiner checklist, teach the system what a mooring incident should trigger — all of it is a row, live, this afternoon.

Enter it once, and it lands everywhere it belongs.

The question every buyer asks is "how do the modules talk to each other?" — because on most fleets they do not, and the rest hours, the drills and the safety meetings are three spreadsheets that disagree. Here they are views over one file. There is no integration layer, because there is nothing to integrate.

What the others still don't do.

Not a feature race. These are the differences your crews and your office feel on a Tuesday.

13 departments, 178 modules. The same file underneath.

Each one is a full working module, not a tab that opens a PDF. They share the register, the people, the companies and the audit trail.

Then there is everything else.

The domains above are the headline. Underneath them the platform already carries the screens a ship manager actually opens in a week — and the ones nobody asks for in a tender and nobody gives back — every one sharing the same register, the same people, the same companies and the same audit trail.

178 modules in one build, and the list is still growing. The full module index, with a line on each →

One day, as the file records it.

Nothing below is a screen someone opened on purpose. It is what happens when the work itself is the data entry.

Built around how ships actually report.

The details that decide whether a system gets used or quietly worked around.

Secure by design, on Apple's Claris platform.

SlashPrime runs on Claris FileMaker, the database platform developed by Claris, an Apple subsidiary, in production worldwide for over three decades. What we built on it is a system in which every person is named, every connection is encrypted, every change is logged, and every ship carries only what is hers.

Security is a property of the whole, not a feature. Ask us for the technical annex; it is written for your IT.

Legacy ERP or Excel? Nothing gets retyped.

The reason fleets stay on a system they dislike is the move, not the software: years of certificates, running hours, crew histories and supplier lists somebody would have to type again. They do not. Whatever you run today — an older maritime ERP, spreadsheets, Word forms, or all three — we take the exports, load them, check them, and you are working in weeks, not seasons.