// SlashBack · Company operations & ship management · Enterprise
The office, the fleet and every ship. One secure system.
Company operations and ship management on a single database — from the board's dashboard to the form a Third Officer signs at sea tonight. A screen for every person, compliance that schedules itself, a ship that works offline and syncs by itself, and security built on Apple's Claris platform.
| Vessel · position | State | ROB VLSFO | Next due |
|---|---|---|---|
| AEGEAN STARSuez → Piraeus | At sea | 486,20 t | SIRE 14/09/2026 |
| IONIAN SPIRITConstanta, berth 42 | In port | 1.204,50 t | DD 03/09/2026 |
| ADRIATIC DAWN34°12'N 025°48'E | At sea | 742,80 t | Class 22/11/2026 |
| CORAL BAYAlexandria, anchorage | In port | 318,40 t | PSC deficiency open |
| AMBER SEAGibraltar → Rotterdam | At sea | 963,10 t | ISM audit 08/10/2026 |
| NORTHERN LIGHTTuzla yard, dock 3 | Off hire | 112,00 t | Redelivery 29/08/2026 |
| PACIFIC ROSEColombo → Jebel Ali | At sea | 1.571,60 t | Crew change 11/09/2026 |
Figures in Greek format, dates DD/MM/YYYY — as the bridge writes them.
Why this is different — the whole site in six lines.
Six points, each linked to the leg of this site that proves it. The rest — every user's own screen, the regulators' registers, the chartering desk, the move from your old system — we show in the demo. If you have forty-five minutes, book one and see it on your own ships.
It runs the company, not just the ships
Tasks, approvals, meetings, leave, HR, the general ledger — the work of the office lives here, with full ship-management depth underneath. Nothing lives in a mailbox. see ↓
One database. One interface. No middleware between our modules
184 modules read and write the same records. A certificate, a seafarer, a purchase order is one record everywhere it appears — there is nothing to reconcile. all modules →
The ship runs the same system, offline, and signs by PIN
Each vessel carries her own copy, opens on what she owes today by rank, syncs by herself, and every form is signed by a named crew member. see ↓
Every SMS form interactive, every risk assessed before the work
Your Word and Excel forms become interactive forms that file one receipt into one ledger; the risk assessment is attached to the permit before it is issued, with the gaps listed. see ↓
Rules you edit, not release — and it shows its working
Approval chains, event tasks and checklists come from tables you can open; documents read into records and tasks are proposed by rule. A person confirms; nothing writes on its own. see ↓
Secure on Apple's Claris platform
TLS in transit, AES-256 at rest, scheduled backups, a named account for everyone, an audit log on every commit, every ship holding only her own slice. see ↓
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.
The live demo wants a desktop screen. Email yourself the link →
// Live demo · five modules, one frame
Try:
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.
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.
01 Today, by rank
Every periodic SMS form carries its cadence and its responsible role. After a PIN sign-in the ship sees only the forms still owed for that rank.
02 A PIN per person
One account per ship, a four-digit PIN per crew member. Every form, drill sheet and acknowledgement is signed by a named person, with rank and time snapshotted at signing.
03 Ship ↔ office lane
Circulars the office waits for the ship to acknowledge; requisitions and reports the ship waits on the office for; a chat thread with the office on the same screen.
04 Kiosk mode, anonymous reporting
The bridge PC boots to a lock screen with the crew list and a keypad. A near miss can be raised from it without signing in — open reporting the paper form never delivered.
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.
01 Only the ship's own slice
A vessel's copy holds her crew, her jobs, her forms. If a laptop walks off the gangway, it carries one ship's records, not a company's.
02 Outbound only, paired identity
The ship talks to the office server; nothing connects into the ship. Each ship file is paired to one vessel with its own account — a login on the wrong PC cannot cross-write another vessel.
03 Nothing waits for the link
Work on board is saved on board. When the link is there the changes travel; when it is not, nobody notices until it is back. A conflict is kept for a person to see, never lost.
04 One board for thirty ships
Every vessel's last contact, what is waiting and how much has travelled this month, on one office screen, with the problems that need a person on top. Updates reach the ships the same way.
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.
The register
Every controlled form, faceted by chapter, category, department, event, rank and ship — with Open in the module, or Form, on each card
Schedule
The same register by when it falls due: daily, weekly, monthly, quarterly, annual, ad-hoc
Compliance
Expected occurrences against what the ledger holds — one cell per ship, per period
Coverage
Which forms have a module, a definition, or still only paper — the map is a setting per client, not a build
The manual
The section tree read in place, with the company's own name filled into the text
Master reviews
One section a month, fleet-wide. Masters comment, the office replies, nothing is verbal
Form builder
Your Word and Excel forms imported into interactive definitions — your codes, your wording, your flags
Doc control
Draft, diff, publish. An amendment bumps the revision and asks for acknowledgement; an editorial change does not
Permits & RA
The permit to work, and the assessment it stands on — attached to the job, the event or the entry
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.
Working aloft — fall from height
Untick a control and watch the residual move. Controls mostly reduce LIKELIHOOD; only a few touch severity, because preparing for a fall or an oxygen-deficient space does not make the consequence smaller. That is why severity has a floor and never reaches 1. Until the controls are done, the first number is the one that counts — and the screen says so.
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.
Five more rules — approvals, appraisals, garbage, PSC, MLC — we walk through in the demo.
The superintendent's visit, from the plan to the close-out.
A visit is planned in one place, lived in another, reported in a third and paid for in a fourth. Here it is one record from the schedule to the expense claim: the trip, the days on board, the jobs with their checklists, the crew who were there, the findings and their corrective actions, the report and the costs — and the internal inspection follows the same road to its close-out.
01 Planned, per ship and per type
Superintendent visits, ISM and MLC internal audits, navigational, mooring and manning-agent audits, planned per vessel. A plan row turns green only when a real visit or audit fulfilled it.
02 Jobs with a checklist behind each
Every visit carries its jobs by reason code, and each reason knows the form or checklist it must produce. A job is not done until that document exists. The crew on board is read from the sea-service records for those dates.
03 Findings to corrective actions
Question-by-question internal audits: a failed answer opens a finding, the finding gets a corrective action with an owner and a deadline, and the CAPA queue shows who owes what until the close-out is evidenced.
04 The report, and the expenses
The coded report per reason, filed and reviewed; and every cost of the trip on the visit record with its receipts, linked to the expense claim and to the vessel's cost book.
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.
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.
01 Encrypted in transit and at rest
Every connection — office client, browser, iPad, vessel agent — over SSL/TLS with your own certificate. The database file encrypted with AES-256, so a copied file is an unreadable file. Backups inherit the encryption.
02 Backed up on a schedule
Full and progressive backups on the server, verified, retained by policy and copied off-site. Restoring a file is a rehearsed procedure, not an emergency.
03 A named account for everyone
No shared logins ashore. Sign in with your Microsoft or Google identity so your own password and multi-factor policy apply; privilege sets decide what an account may open, read and change.
04 Every commit logged
Who changed what, and when, on the tables you choose to audit — per record and per person. Deletions are counted, not hidden. The trail an ISM auditor asks for is a screen.
05 Off-site backups that cannot be altered
Every backup is copied automatically to off-site object storage in the EU with object lock — write once, read many. For its retention period it cannot be changed or deleted by anyone, an administrator or a ransomware included. Restoring from it is a rehearsed procedure, not an emergency.
06 Files and AI behind the server
Documents in object storage are reached through short-lived signed links minted by the server; the model key never leaves it; the reader writes nothing until a person confirms. Every list exports to Excel — the data is yours.
Security is a property of the whole, not a feature. Ask us for the technical annex; it is written for your IT.
// Next
See it running on your own fleet.
A page can show you screens. It cannot show you your ships on them. The demo can — forty-five minutes with your vessels' names, your ranks and your SMS forms index loaded, online or at your office. Then a pilot on one department, a fixed-scope onboarding, and a decision after thirty days of real use. Legacy ERP or Excel? Nothing gets retyped — the migration is part of the pilot.
SlashBack · 4 Paschalias Street · 15452 Palaio Psychico · Athens, Greece · Claris Partner · runs on Mac, Windows, iPhone, iPad and the web · support after go-live: support@slashback.gr