Instead of running your server-side logic on a conventional server or cloud instance that sits on a normal operating system, put the backend on the Internet Computer.
How this works on ICP
• On ICP, backend logic runs in canisters — self-contained units of code (usually WebAssembly) plus persistent state.
• The network replicates and executes the code through consensus. Cryptography and the protocol guarantee that the code runs exactly as written (tamperproof).
• You don’t manage servers, virtual machines, or operating systems. The network handles replication, availability, and execution — this is what “serverless” means here.
• Because there is no traditional OS layer that an attacker can target in the same way as a normal cloud server or personal computer, the usual class of OS-level vulnerabilities is removed from the attack surface of the application itself.
ICP’s own materials describe this as a “sovereign cloud” where apps are built from network-native, tamperproof code with no OS, cloud infrastructure, or database dependencies to breach in the conventional sense.