We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Demurrage isn't a billing problem — it's a preventable readiness failure. We help bulk operators prevent demurrage before laytime is consumed.
The signals exist days or weeks in advance. What's missing is a system that acts on them.
You learn about delay when the vessel is already waiting. By then, options are gone.
Root causes are spread across emails, counterparties, and ports. No single source of truth.
The same ports, lanes, and counterparties generate repeat demurrage. But lessons aren't learned.
Your team spends time reconciling and disputing delay, not preventing it in the first place.
Beyond invoices: lost voyage opportunities, tied-up capital, operational distraction, broken relationships.
Everyone agrees it was "unavoidable" — until the invoice arrives. No operational ownership of prevention.
The result? A system optimized to argue about delay, not prevent it.
A real-time, contract-aware demurrage prevention system designed specifically for bulk shipping.
Track vessels, ports, cargo, documentation, and third-party dependencies in real time. No blind spots.
Not just delay — risk relative to laycan, NOR, and laytime exposure. Know before waiting begins.
Alerts, escalation, and recommended actions while outcomes can still change. Time is leverage.
Clear visibility into what failed, when, and why — before invoices and disputes.
"The difference is not insight — it's timing."
A concrete example of how Valnar prevents demurrage before it happens.
AIS and port data show anchorage congestion building. Contract rules indicate laytime exposure begins 12 hours after NOR. Cargo documents are still unverified.
Risk is flagged days in advance. The specific missing dependencies are identified. The system quantifies exposure if nothing changes.
Escalation happens while alternative actions are still available. You stay in control. The vessel arrives to a ready berth.
Most teams discover the problem when the vessel anchors.
With Valnar, you act while outcomes can still change.
Every feature designed to prevent delay, not just report on it.
Understands laycan, NOR rules, and laytime triggers. Risk is measured against your contracts.
Continuous visibility across vessels, ports, and dependencies. No more blind spots.
Learn from prior delays to predict and prevent future ones on the same lanes and ports.
Threshold-based triggers when risk crosses the point where action is still possible.
We ingest data you already have. No workflow changes required to get value.
Know which party caused readiness failure before the invoice phase.
In 90 days, you'll know whether demurrage is truly unavoidable — or simply unmanaged.
Pilot fee is often less than the demurrage from a single delayed voyage.
By the end of the pilot
Clear insight into where demurrage risk actually originates
Proof of which delays are actually preventable
Measured prevention value based on your data
Prioritized list of chronic issues (ports, lanes, counterparties)
Demurrage exists as a contract concept — but its current scale is not inevitable. Most demurrage events are caused by known readiness failures that surface before arrival. When the same ports, lanes, and counterparties generate repeat demurrage, that's not fate — that's a system failure.
Fuel inefficiency used to be "part of the business" too — until operators instrumented it.
Tracking is not prevention. Most teams can answer "Where is the vessel?" and "What's the ETA?" — but very few can answer "Is this voyage contractually safe right now?" or "Which dependency will cause delay if nothing changes?"
A speedometer doesn't prevent accidents. Brakes do.
You're right — you don't control ports. But you do control when you escalate, which alternatives you explore, how early counterparties are pressured, and whether readiness gaps are exposed before arrival. Time is leverage. Early signal creates optionality. By the time a vessel is anchored, you have none.
You don't control the weather either — but you still reroute before the storm.
Demurrage pays cash, but it destroys utilization. A delayed vessel misses follow-on voyages, breaks schedules, increases ballast risk, and creates downstream knock-on delays. The highest-performing owners optimize for voyages per year, not demurrage per voyage.
Airlines don't profit from delay fees — they profit from planes in the air.
This is intentionally designed to be low-friction. No rip-and-replace. No workflow overhaul. No behavior change required to get value. We ingest data you already have and surface risk you currently don't see. The output is fewer surprises — not more work.
Complexity already exists. We reduce it.
We don't need perfect interpretation to create value. We focus on laycan, NOR rules, and laytime triggers. Even partial contract awareness dramatically improves early risk detection. Perfection is not required to prevent delay.
Autopilot doesn't fly the plane — it reduces pilot workload.
Not a cost of business.
You're already paying for demurrage. The only question is whether you want to keep paying for the same preventable delays next year.