No formal Aleph Cloud whitepaper or litepaper was located during this pass.
The most useful first-party material is the current product site, the docs set, and the project’s own repositories for cloud docs, VM orchestration, and message formats.
Aleph Cloud appears most analytically interesting as a bundled control plane across storage, indexing, compute, and confidential execution rather than as a single-purpose decentralized storage network.
Official landing page describing Aleph Cloud as a censorship-resistant decentralized cloud with storage, VPS, GPU cloud, confidential VMs, and cross-chain interoperability.
Useful source for the operational surface of standard instances, including console/CLI creation, IPv4 exposure paths, and backup/restore controls with operator-determined expiration.
Most important source reviewed for network architecture: CRNs, CCNs, workload distribution, hardware requirements, microVM isolation, and ALEPH-token incentives for operators.
Useful source for the message specification and item_hash semantics shared by client and node software.
Key takeaways captured for corpus
Aleph Cloud is not just a decentralized storage network; it is a broader cloud stack that combines storage, indexing, execution, and confidential-compute claims.
The CRN/CCN relationship is a core control surface because CCNs distribute workloads to connected CRNs, shaping where routing and coordination authority can sit.
The trust model blends crypto-native addressing and token incentives with highly specific hardware, virtualization, and operator requirements.
Practical authority also appears in user-facing control planes: hosted console flows, backup retention policy, port-forwarding/domain exposure, and whichever nodes satisfy hardware and attestation requirements.
Aleph Cloud belongs in comparisons not only with storage systems like Filecoin/IPFS/Irys but also with decentralized cloud and offchain-execution stacks that bundle orchestration above raw resource markets.