UpArate

AI for Tanker Chartering

The AI engine for tanker chartering operations.

Drafts the emails. Files the documents. Tracks the deadlines. Your operators approve — they don't type.

What UpArate Does

One engine. Every email genre an operator handles.

Operators spend most of their day relaying email between charterers and owners, filling indemnities and stowage plans, and chasing deadlines. UpArate handles all three.

Drafts every email

Recaps, voyage orders, freight invoices, heating and COW instructions, STS clearance. Engine classifies the inbound, extracts the fields, and writes the reply for the operator to approve.

Fills every document

LOI templates auto-completed from the charter party, the recap, and the voyage context. Green for confidently filled, amber for fields the operator must confirm. No blank-template back-and-forth with the P&I Club.

Tracks every deadline

Laycan narrowing, B/L chase after sailing, post-voyage Master silence, EDP suppression. UpArate schedules the alerts and clears them when the confirming inbound arrives.

How It Works

From inbound to relay, in seconds.

UpArate connects to the operator's mailbox via Microsoft Graph. Every new message runs through the engine before the operator opens it.

  1. 01

    Inbound arrives

    A recap, voyage orders, an LOI template, or an SOF lands in the operator's Outlook inbox.

  2. 02

    Engine drafts

    UpArate classifies the message, extracts the fields, fills any templates, and writes the reply.

  3. 03

    Operator approves

    The draft appears in the operator's dashboard. Approve as-is, edit, or reject. Edits teach the engine for next time.

  4. 04

    Sent & tracked

    UpArate sends from the operator's mailbox, files the documents, and schedules any follow-up alerts.

Built with an operator

Designed by a 20-year tanker chartering operator.

UpArate is built alongside a senior tanker operator with two decades on the desk. The engine knows the difference between COSP and BOSP, when EDP suppresses a B/L chase, and why an STS clearance needs both sides' docs in the same thread. It's designed around the email rhythm of a real tanker desk — not a theoretical workflow drawn on a whiteboard.

Every guardrail, every alert, every template variant comes from a real incident on a real voyage. We don't ship features the operator wouldn't recognize.

See UpArate on a real tanker voyage.

Five-minute walkthrough of the engine handling a recap, an LOI template, and a Statement of Facts end-to-end.