Home / Deployment
Deployment
Some organisations 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 three options run the same platform.
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.
Runs inside your own estate under licence, against your own database, with your own backup and retention policy. Your data never leaves infrastructure you control, which is frequently the difference between a procurement approval and a refusal.
Installed with no outbound network path at all. Features that would require egress are disabled by the install rather than left switched on and merely unused — the distinction matters when the environment is audited.
This is a genuinely different install profile, not a configuration flag on the cloud product.
Data ownership
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.
Usually answerable in one conversation, and worth having before a procurement review rather than during one.
