labs@atheron:~/industries/ports-marine/cloud$ deploy --managed --monitored

Port systems, kept running

Hosting, monitoring and backups for the systems your port relies on.

A berth plan or a gate system that goes down at the wrong moment holds up vessels and trucks. We host and run the systems we build, or the ones you already have, in your cloud account or ours, with monitoring, tested backups and updates planned around your operations.

Start a project See the example projects

// what matters here

What is different in this industry.

In your account if you prefer

Servers, data and bills can stay in your own cloud account. We work inside it, or host it for you.

Backups that are tested

Databases are backed up on a schedule and restored to a test server, so you know they work before you need them.

Updates around your calls

Planned updates are scheduled for quiet hours that your operations team agrees, never in the middle of a vessel call.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb app

Vessel calls and berth planning

Hypothetical. Not a client, not a result.

// The problem

A terminal plans berths on a whiteboard from agents' emails, so arrival changes reach the planner late and crane and labour bookings are redone by phone.

// What we would build

A web system where agents submit and update vessel calls, the planner drags calls onto a berth timeline that shows estimated arrivals from an AIS data provider, and cranes, labour and services are booked against each call. Hosted and run for you on AWS, with monitoring and backups. Vessel positions are for planning only, never for navigation.

// What is in it

An agent portal for vessel call requests, updates and documents
A berth timeline with drag-to-plan and clash warnings
Estimated arrivals from an AIS data provider, shown beside the agent's own times
Cranes, labour, pilots and services booked against each call
A link to your terminal operating system for confirmed calls
Hosting, monitoring and backups run for you

// Stack

Next.js
PostgreSQL
AIS data provider API
Terminal system API
AWS Canada

// estimate

Build: ≈ US$105,000 to US$160,000, delivered within 23 weeksCAD 149,400 to 228,500
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 5.9 to 9.9 weeks
Core features: 2.9 to 4.9 weeks
Full build: 1.9 to 3.4 weeks
Testing and fixes: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

AIS data provider account: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 29,880 to 45,700
Discovery 7.7%: CAD 11,503.80 to 17,594.50
Design approved 7.7%: CAD 11,503.80 to 17,594.50
Core features 23.3%: CAD 34,810.20 to 53,240.50
Full build 15.5%: CAD 23,157.00 to 35,417.50
Testing and fixes 7.7%: CAD 11,503.80 to 17,594.50
Launch 8.1%: CAD 12,101.40 to 18,508.50
Holdback, 30 days after launch (10%): CAD 14,940 to 22,850

Start from this example

Example projectWeb app

Port activity dashboard

Hypothetical. Not a client, not a result.

// The problem

A port authority pulls vessel movements, berth use and cargo figures from several systems and AIS feeds into spreadsheets for every monthly report.

// What we would build

A data warehouse that takes AIS feeds, the terminal system and berth records on a schedule, checks them for gaps and duplicates, and shows calls, dwell times, berth use and cargo on dashboards, with the monthly report filled in automatically. For planning and reporting, never for navigation.

// What is in it

AIS feeds from two providers, joined and checked for gaps
Calls, dwell times and berth use by terminal and by month
Cargo figures from the terminal system, with one written definition each
The monthly report filled in automatically
A map of vessel positions for planning, clearly marked not for navigation

// Stack

PostgreSQL
dbt
Metabase or a custom dashboard
AIS data provider APIs
DigitalOcean

// estimate

Build: ≈ US$78,000 to US$119,000, delivered within 17 weeksCAD 111,100 to 169,800
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 4.4 weeks
Core features: 2.4 to 4.4 weeks
Full build: 1.9 to 2.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

AIS data provider accounts: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 22,220 to 33,960
Discovery 7.7%: CAD 8,554.70 to 13,074.60
Design approved 7.7%: CAD 8,554.70 to 13,074.60
Core features 23.3%: CAD 25,886.30 to 39,563.40
Full build 15.5%: CAD 17,220.50 to 26,319.00
Testing and fixes 7.7%: CAD 8,554.70 to 13,074.60
Launch 8.1%: CAD 8,999.10 to 13,753.80
Holdback, 30 days after launch (10%): CAD 11,110 to 16,980

Start from this example

// questions

Questions we get about this.

Can you take over hosting of an existing port system?

Often, yes. We start with a review of how it runs today, then move it or run it where it is.

Where is our port data kept?

In the region you choose. For Canadian ports that is usually a Canadian region of AWS or DigitalOcean.

Who watches the terminal systems overnight?

Monitoring alerts our team when something fails. What we cover and when is written into your support plan before we start.

Back to the industry: Ports, shipping and marine About the service: Cloud, DevOps and operations

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call