Custom software development
Applications built for a specific operational process — berth planning, dispatch, case handling, inspection records — where off-the-shelf tools stop short of the real workflow.
Ghent — handover session, overcast
A Belgian software house with a maritime focus
Bluehaven Maritime Services BV is a software and IT services company registered in Belgium, working with clients across the country and the wider Benelux region.
Who we are
We build and modernise the systems that ports, shipping companies, forwarders, and industrial manufacturers depend on.
The company exists because maritime and industrial operations need software partners who understand the constraints of the environment, not only the technology stack. A berth window does not extend because a release slipped. A customs format changes on a Tuesday and the filing has to go out on Wednesday. Equipment was installed by a vendor who no longer answers email. Those conditions shape what we agree to build and how we staff it.
We are one of Belgium's specialist software companies rather than a general consultancy. The work is custom software development, cloud, data and BI, system integration, enterprise application modernisation, and cybersecurity — and a single project often touches three of them at once.
What the company does
Six trades, assembled around the problem
In practice these are not separate departments. The team is assembled around the problem rather than around an org chart, and most engagements begin with a short discovery phase.
Cloud migration
Moving long-running systems off ageing hardware without stopping the operation, including the cutover plan, the rollback path and the training that goes with it.
Data and BI
Reporting that traces back to the source system, so an operational figure can be explained rather than argued about in a Monday meeting.
System integration
Connecting terminals, carriers, customs systems and ERP platforms that were never designed to speak to each other, with monitoring so a broken link is visible before a customer calls.
Enterprise application modernisation
Replacing or wrapping software that still works but can no longer be changed safely — one module at a time, with the old path kept running until the new one is trusted.
Cybersecurity
Access review, patching and logging for systems that sit on a shared port network, where a misconfiguration is an operational problem, not only an IT one.
Most engagements begin with a short discovery phase and grow from there — or stop there, if that is the right answer. We would rather spend two weeks proving the shape of a problem than two quarters discovering it during delivery.
Why maritime and industry
A narrower field, better questions
It would be easier to sell general software development to anyone who asks. We chose a narrower field because the constraints are real and they reward experience.
- Berth windows They do not move. A release date that misses the vessel is a cost the operator pays, not a note in a retrospective.
- Customs formats They change. Filing interfaces are updated by authorities on their own schedule, and integrations have to absorb that without a project restart each time.
- Legacy equipment Installed by vendors who no longer answer email, still running, still load-bearing, and still part of the new architecture.
- Two or three languages On the same shift. Screens, labels and error messages are a design decision here, not a translation ticket at the end.
A team that has met those constraints before asks better questions in the first workshop — and better questions are most of what separates a project that works from one that gets renegotiated.
How the team is organised
Small squads, engineer-led
Delivery runs in small squads, typically three to six people, led by an engineer rather than a layer of management. Clients meet the people who will do the work before the engagement starts.
- Squad size3–6
- 1
- 2
- 3
- 4
Delivery lead
Every squad has a named delivery lead who is the client's single point of contact. Not a shared inbox, not an account manager relaying messages — the person who can answer whether the migration will be ready on the night you need it.
Specialists join for the phase
Data, cloud and security engineers join for the phases that need them and leave when the phase closes, so a small integration project does not carry a standing security team on the invoice.
Whoever is free does not exist
We do not staff a project with whoever is free that month. If the person with the right background is committed elsewhere, we say so and propose a start date that is honest rather than a start date that is convenient.
When someone leaves
If a person leaves the project, we say so and plan the transition openly — handover sessions, paired working for the incoming engineer, and a written record of what they owned. The announcement is not saved for a monthly report.
Where we work
One hour from Antwerp
Belgium is a small country with a distributed technology market. Brussels holds the largest concentration of firms. Antwerp is where maritime and logistics demand sits — terminals, forwarders, barge operators and the customs traffic between them. Ghent has built genuine regional delivery capacity, and Zaventem hosts several established IT-services companies close to the airport.
We work on client sites when a process needs watching — a quay office on a night shift, a wire room during a cutover — and remotely for the rest. We travel within the Benelux without treating it as an exception. For a maritime project, being an hour from Antwerp matters more than a prestigious address.
Brussels
Registered office
Antwerp
Maritime demand
Ghent
Regional delivery
Liège
Industrial clients
The principles we work by
Three things that shape what we take on
Decline rather than under-staff
We would rather decline a project than take one we cannot staff properly.
Documentation written during the work
Reconstructed documentation is fiction, and everyone reading it knows it.
Say when something cheaper exists
Even when it means a smaller engagement. That has cost us work and it has kept clients.
Telling someone their problem is smaller than they think is worth more than the invoice it costs us. It is a fair trade.
How we fit into the Belgian market
One of the specialists
Belgium's technology sector is layered. Large consulting groups such as EY Belgium and Cognizant Belgium, global integrators, telecom-led providers such as Orange Business Belgium, and a deep bench of specialist boutiques — TECHI Solutions, Sigli, DNA Solutions in Zaventem, and newer entrants such as EACHSTAPP — all compete for custom development work.
We are one of the specialists, and we are clear about what that means.
| Area | What we offer | What sits outside |
|---|---|---|
| Software delivery | Custom development and enterprise application modernisation, delivered in small engineer-led squads. | Enterprise-wide strategy programmes that end in a slide deck rather than a running system. |
| Integration | Terminal, customs, carrier and ERP integration with monitoring that shows a broken link early. | Network infrastructure builds, cabling and hardware procurement. |
| Data and reporting | Operational reporting that traces back to a named source field, so a figure can be explained. | Regulatory interpretation — we build to a rule your legal and customs advisers define. |
| Cybersecurity | Access review, patching and logging for systems that sit on a shared port network. | Managed SOC services with round-the-clock staffing. |
What clients can expect from us
The shape of an engagement
Commercial terms are stated before work starts, with invoicing against milestones or monthly by bank transfer. Nothing in this list is a surprise later.
- A short discovery phase
- With a written output you can take to a board, a vendor or a second opinion.
- A named team
- The people you met at the start are the people doing the work.
- Demos every two weeks
- Working software, not status reports. If a fortnight has nothing to show, the plan was wrong.
- Honest answers, early
- When something is harder than expected, you hear it in week three rather than at the deadline.
- A real handover
- Documentation, paired sessions and access, so your team can run what we built.
- Stated commercial terms
- Scope, milestones and invoicing agreed in writing before the first sprint begins.
Where to start
A system that no longer fits
If you have a system that no longer fits, an integration that keeps failing, or a plan that needs a technical second opinion, the first step is a short conversation. We will ask what the current process looks like, who uses it, and what a good outcome would mean. If it sounds like something we should do, we will propose a discovery phase. If it does not, we will say that too.