On-premise or cloud: how to choose between Trustiaboot and Trustinstance
Both blocks can host a server. The question isn't which is better, it's which data is allowed to leave your premises.
A question comes up often during audits: "why can two different blocks host a server?" Trustiaboot and Trustinstance aren't redundant — they answer a different constraint: where is the data allowed to live.
Trustinstance: the default case
For the vast majority of uses, a managed server off your premises — hardened, supervised 24/7, with automated backups — is the most economical and reliable solution. It's the default choice, the one we recommend unless there's a specific constraint.
Trustiaboot server: the justified exception
Some data structurally must not leave your premises: a client's contractual requirement, sector regulation, or simply an internal sovereignty policy. In that case, we deploy and harden a physical server on your site, with the same level of rigor as a hosted instance — but without the convenience of shared infrastructure.
The real trade-off
On-premise structurally costs more (hardware is on you, no pooling, physical intervention needed for any failure) — it's never a default choice, it's an answer to a specific constraint identified during the audit. Combining both is common: an on-premise server for sensitive data, a Trustinstance instance for the rest.
A question about your situation?
Request a free audit, we'll look at your specific case.