Home / For IT and security
For IT and security
Stated as controls your team can test, with what we do not claim written alongside.
In our managed cloud, with records held in the European Union (Finland); on a dedicated instance we run in the region you need; on your own servers under licence; or fully air-gapped. Self-hosted, it is a small set of containers beside a PostgreSQL database, delivered as a signed release bundle that your team verifies before loading. A failed upgrade rolls back to the previous version.
No. Once running, a self-hosted or air-gapped deployment makes no outbound connection: not for licensing, not for telemetry, not to us. The licence verifies offline.
How we hold that line: the build fails if our source gains an outbound call, and a test plants one to prove the check catches it. That check covers our own code, not every library beneath it, which is why this is a property your team should confirm at the network boundary rather than take from us.
Every record carries the organisation it belongs to, and that boundary is enforced by the database itself rather than by application code remembering to filter. A query that forgets to scope returns nothing, not another customer's records. On a dedicated or self-hosted deployment, the database is yours alone.
Accounts belong to your organisation and are administered by you. Second-factor sign-in works by authenticator app or passkey, and your policy can require it for everyone. Passkeys work with no internet connection. Scanners and machines get their own credentials, per facility or per unit, and a revoked one stops working immediately.
A documented HTTP API, with keys that carry only the scopes your administrator chose and can be revoked. Data from your ERP comes in from the export it already produces; Cargovate deliberately never writes back into it.
No, and we do not claim either. If your programme needs evidence against a specific control set, send it to us and you will get a straight answer about what is in place today and what would be work. The architecture document has a section on exactly what we do not claim.
Start from the architecture document, then put the rest to us in writing.
