Runs where your data is allowed to be.

Some organizations cannot put freight data in a shared cloud — for contractual, jurisdictional or security reasons. That is a deployment decision, not a reason to lose the deal, and all four options run the same platform.

Cloud, on-premises or air-gapped: choosing how to run Cargovate. 2:15 · Watch with chapters and transcriptDemo tenant — the companies and data shown are fictional.

Option 01

Managed cloud

We run it. Fastest to start, nothing to operate on your side, updates applied centrally. The right default unless you have a specific reason to need otherwise.

You provide: Nothing beyond your data
Suits: Most operators, and every pilot

Option 02

Dedicated instance

We still run it, but for you alone: your own stack, database, backups and upgrade window, in the region your data must be held. Nothing to operate on your side.

You provide: Nothing beyond your data, and the region it must stay in
Suits: Clients with a residency requirement who do not want to run servers

Option 03

On-premise

Runs inside your own estate under license, against your own database, with your own backup and retention policy. Your data is held on infrastructure you control and goes out only through connections you switch on, such as carrier tracking or your own mail server, which is frequently the difference between a procurement approval and a refusal.

You provide: A host and a database; we provide the install and the license
Suits: Regulated operators, and clients with data residency obligations

Option 04

Air-gapped

Installed with no outbound network path from the server. It is the same signed bundle as self-hosted, with the features that need to reach outside (carrier tracking feeds and email notification) switched off. Once running it has no network path out, and needs none: the license verifies offline, and our source makes no outbound calls except to destinations an operator configures, enforced at build time. That check covers our own code, not the open-source libraries beneath it; the isolation of your network is what guarantees the rest.

The browser reaches nothing outside the site either, once the installation is set to offline (CARGOVATE_OFFLINE=1): fonts are part of the bundle, and maps draw a world outline served by the installation itself, or your own tile server if you run one. The outline shows countries and coastlines, not streets.

You provide: An isolated host; transfer is by controlled media
Suits: Regulated supply chains, such as aerospace and pharmaceutical manufacturing, and environments where outbound network access is prohibited outright

Data ownership

Your record leaves with you.

A client's operational record — consignments, checkpoints, custody — is attributed to that client from the first row written, in every deployment option. If you stop using Cargovate, you leave with a complete history rather than an export that omits the parts that were inconvenient to model.

This is enforced structurally in how records are stored, rather than promised in a contract clause.

Which deployment fits your obligations?

Usually answerable in one conversation, and worth having before a procurement review rather than during one.

Pricing and a quotation Request a demo Deployment Architecture (PDF)