Saidul Islam BhuiyanScalable Enterprise Software Engineering Book a call

Maritime, transport and logistics

Software for maritime, transport and logistics operations

Apps and platforms for crews, fleets and field teams who can’t count on a connection.

Book a call See all work

In short

We build software for people who work on ships, on buses and in the field, and for the teams managing them from shore or the depot. That includes a Bluetooth smartwatch app that keeps syncing with no internet at sea for Ovue ANCORE, and Android POS ticketing across BRTC’s national bus fleet. Maritime and public transport are delivered work. Logistics and aviation ground operations are where the same skills apply next, and we’re upfront about that difference.

Delivered in
Maritime, public transport
Applies to
Logistics, fleet, aviation ground ops
Devices
BLE wearables, Sunmi POS
Design goal
Keeps working with no connection
Starts with
1–2 week sprint, $1k–$2k

Delivered work

Built for ships, buses and field teams

Maritime · Crew wellbeing

Ovue ANCORE

Senior Engineer in a small team

Crew wearables and AI that keep working with no internet at sea

A Kotlin Bluetooth module, an offline upload queue over slow ship links, confidential safety reporting and a shore portal for crewing and QHSE teams.

Business resultCrew health data keeps flowing with no internet at sea, and both crew modules shipped for the ANCORE pilot.

KotlinBluetooth LEReact NativeGemini
Read the full case study →

Public transport · Bangladesh

BRTC

Full-stack Lead

Android POS ticketing for the national bus operator

Cash tickets replaced by Sunmi terminals across the fleet, batch ticket sync, and a multi-tenant admin for fleet, route and staff management.

Business resultFares recorded digitally instead of in cash, with each depot seeing its own numbers.

Android POSNestJSReactMongoDB
Read the full case study →

Field workforce · United Kingdom

Everhome

Lead Developer

Onboarding, scheduling and payroll for carers out on visits

Not a transport product, but the same shape of problem: ID and right-to-work checks, rota planning for people on the move, and completed visits that flow into payroll and invoicing.

Business resultCarer onboarding checks take about 3 minutes, down from hours of paperwork.

Node.jsAzureSQL ServerStripe

Common ground

The hard parts we design for

  • No reliable connectionData is stored on the device first and sent in small batches when a link appears, so work carries on at sea or out of coverage.
  • Devices in the fieldSmartwatches over Bluetooth LE and Android POS terminals, with reconnects and background sync handled properly.
  • Consistency across a fleetBatch sync keeps records consistent across every device and route, so the back office can trust the numbers.
  • Many depots, vessels or customersMulti-tenant access gives each depot only its own data, while shore teams manage vessels, crew and certificates in one portal.
  • Crew documents and onboardingMedical certificates read by AI and confirmed by the seafarer, and identity and right-to-work checks in one guided flow.
  • AI with a human checkInsights pass a safety check before crew see them, and coordinators approve what AI drafts.

Where this applies

What we’ve delivered, and where it carries over

We’d rather tell you this now than have you find out on a call.

  • DeliveredMaritimeCrew apps, wearables, certificate tracking, confidential safety reporting and shore portals.
  • DeliveredPublic transportTicketing, POS terminals, depot admin, and fleet, route and staff management.
  • Carries overLogistics and fleetDriver and field apps, proof of delivery, partner integrations and fleet dashboards. We haven’t shipped a logistics platform yet, but the offline, device and multi-tenant problems are the ones we’ve already solved.
  • Carries overAviation ground operationsCrew, ground handling and maintenance apps with offline use and document tracking. This would be a new sector for us, so we’d start with a discovery sprint.

When to call us

Signs this is the right time

  • Crew or drivers lose work when the connection drops
  • Paper, spreadsheets or cash still run part of your operation
  • Field devices or wearables keep disconnecting
  • Each depot, vessel or customer needs its own view of the data
  • Your prototype works in the office but not on a ship or in a vehicle
Ovue maritime case study →BRTC transport case study →IoT and Bluetooth →

Questions

Common questions

Anything else is easier to answer on a short call.

Do you build apps that work offline on ships and vehicles?

Yes. Data is stored on the device first and uploaded in small batches when a connection appears. On Ovue ANCORE, smartwatch data syncs to the phone with no internet, and small daily snapshots go ashore whenever the ship gets a connection.

Have you built maritime software before?

Yes. Working in a small team on Ovue ANCORE, we built the Android Bluetooth layer for crew smartwatches, AI health insights, medical certificate reading, confidential incident reporting and the BioVue shore portal. The crew modules were delivered for the ANCORE pilot in September 2026.

Have you built logistics or fleet software?

We haven’t shipped a dedicated logistics platform yet. The closest delivered work is BRTC, which includes fleet, route and staff management, POS terminals and batch sync across a national bus fleet. We’d start with a discovery sprint to check the fit honestly.

Do you work with aviation companies?

Aviation would be a new sector for us. Our closest experience is Wego’s travel platform, where we built hotel search next to its flight search, and our crew and offline work on ships. It suits ground operations, crew and maintenance apps better than certified flight systems.

Which devices have you integrated?

Smartwatches through a vendor Bluetooth LE SDK, and Sunmi V2 and V3 Android POS terminals.

Can you connect to the systems we already use?

Usually, if they offer an API or data export. Integration is a large part of our work, including 40+ supplier feeds brought into one model at Wego. The discovery sprint maps your systems and flags anything risky early.

How does a project start?

With a 1–2 week discovery and architecture sprint, priced at $1,000 to $2,000. You get a scope, a technical plan and a clear view of whether we’re the right fit.

Tell us what you need to build or scale.

Engagements start with a 1–2 week discovery sprint, $1,000 to $2,000. Email

Book a call LinkedIn ↗