Skip to main content

Aleph Cloud

Aleph Cloud (aleph.im) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Aleph Cloud — decentralized cloud services (storage/compute/indexing), targeting AI/ML workloads among others; token: ALEPH.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a decentralized “cloud provider” (virtual machines/functions/storage/indexing) for applications.
  • Who it’s for: dApp developers and teams that need backend/compute without a single center.
  • Why onchain/token: the ALEPH token is claimed as the currency for paying for services and as the staking mechanism for nodes.

How it works (very briefly)

  1. The user does: chooses a service (VPS/GPU/Functions/Storage) and launches a workload.
  2. The system does: allocates resources in the Aleph Cloud node network and provides access via UI/SDK/API.
  3. The user gets: compute/storage/indexing as a service.
  4. Where the blockchain is: onchain staking mechanics and support for PAYG payments on some networks are described for the network.
  5. Token role (if any): ALEPH is used for paying for services and for staking/node operation.

Quick links: AI thesis fit

Project passport

Field Value
Project name Aleph Cloud
Also known as (aliases) aleph.im; $ALEPH
Logo (logo) ../assets/145_aleph-im_logo.jpg
Token symbol (ticker) ALEPH
Category AI/Compute
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x27702a26126e0b3702af63ee09ac4d1a084ef628
Token model (token_type) utility (payments + staking)
Max supply 500,000,000 ALEPH (Max Total Supply on Etherscan)
Issuance —
Tokenomics (tokenomics, brief) The token is used to pay for cloud services and for node staking (Tier‑1).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) GPU/compute for AI/ML workloads
Use‑case (use_case) run AI/ML workloads on a decentralized cloud
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

Aleph Cloud is a set of decentralized cloud services: compute (serverless/VM), storage and indexing. On its website the project is positioned as an “AI Supercloud” and separately highlights AI/ML scenarios (GPU cloud, confidential AI/ML pipelines), but the protocol itself is not a provider of AI models — it provides the infrastructure for running them.

Features/modules

  • Decentralized Storage (including IPFS integration).
  • Decentralized Computing: serverless functions and persistent virtual machines.
  • Blockchain indexing: indexing and querying of blockchain data.
  • Staking / CCN: staking on Core Channel Nodes (Tier‑1).

Typical scenarios

  • Scenario 1: a developer hosts a backend (functions/VM) → gets API/compute without a centralized cloud.
  • Scenario 2: a team rents GPU resources → trains/runs AI/ML workloads.
  • Scenario 3: a project uses indexing → gets fast queries to onchain data.

Getting started (wallet/network)

  • What you need: a wallet and an Aleph Cloud account; a choice of service (VPS/GPU/Functions/Storage).
  • Network/chain: the ALEPH token exists on several networks; the base contract is ERC‑20 on Ethereum.
  • Fees: network fees + payments for resources/staking (depending on the scenario).

Architecture/tech (non‑AI)

  • Components: network nodes (including CCN), compute/storage/indexing services, SDK/tools.
  • Onchain interaction: the docs describe staking mechanics and support for PAYG payments (token streaming) on some of the supported networks.

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): the official token page describes the use of ALEPH for paying for Aleph Cloud services and for participating in the network via staking and node operations.
  • Staking (Tier‑1): the staking guide describes a minimum stake of 10,000 ALEPH and an activation threshold of 500,000 ALEPH on a CCN to receive rewards.
  • Max supply/issuance parameters: not recorded in the Tier‑1 sources used (see Evidence).

Governance

  • Governance: the governance model of Aleph Cloud is not described in the Tier‑1 sources used.

Security and incidents

  • Audits / bug bounty / incidents: Tier‑1 links are not listed in this card.
  • Risks: exploitation of node/VM vulnerabilities, supply‑chain risks (containers/images), risks of node operator centralization.

Project status and timeline

  • Current status: an active product (docs + app).
  • Roadmap: a roadmap post (Medium) is listed in this card.

Ecosystem/integrations

  • Integrations: SDK/tools, multi‑chain support (see the docs “Supported Chains”).
  • Where it is used: decentralized applications that need backend/compute (specific cases require a separate list).

AI component of the project

  • What is real AI here? This is infrastructure for AI/ML workloads (GPU cloud, confidential AI/ML pipelines), not a protocol with its own models.
  • What is truly onchain? Staking on CCN and part of the PAYG/balance mechanics are described as the network’s interaction with blockchains.
  • Why is a token needed? ALEPH is used for paying for cloud services, staking and node operation (Tier‑1).
  • Red flags (based on the information found): AI‑washing — medium (do not confuse “compute for AI” with an “AI protocol”); onchain‑washing — medium (it is necessary to explicitly identify which settlements/payments go onchain vs offchain); token‑washing — medium (check where exactly the token is mandatory for payment/staking and whether there are alternatives).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity medium 2
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): — (there is AI_1: an AI‑oriented use case of the infrastructure is described)
  • Evidence: Tier‑1 — https://aleph.cloud/whitepaper
  • Why sufficient / why not (one line): AI_0 applies only if AI_1..AI_4 = 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the network provides compute (including GPU) for running and deploying AI/ML workloads.
  • Evidence: Tier‑1 — https://aleph.cloud/whitepaper
  • Why sufficient / why not (one line): The Tier‑1 product description includes GPU Cloud and mentions AI/ML pipelines as a target scenario.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo of AI/ML workloads is recorded in this card.
  • Evidence: Tier‑1 — — ; Tier‑2/3 — —
  • Why sufficient / why not (one line): There is positioning and a service, but no specific reproducible example for AI.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The Tier‑1 sources contain no quality/performance benchmarks for AI.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): AI architecture/model versions are not applicable (the project is infrastructure, not a model provider).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): For compute infrastructure, resource characteristics are more relevant than a “model architecture”.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ALEPH (ERC‑20): 0x27702a26126e0b3702af63ee09ac4d1a084ef628
  • Evidence: Tier‑1 — https://etherscan.io/token/0x27702a26126e0b3702af63ee09ac4d1a084ef628
  • Why sufficient / why not (one line): There is an onchain identifier of the token in the block explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the docs describe onchain mechanics: PAYG token streaming (for some networks), balances and staking on Core Channel Nodes.
  • Evidence: Tier‑1 — https://docs.aleph.cloud/about/network/supported-blockchains/ ; https://docs.aleph.im/nodes/staking
  • Why sufficient / why not (one line): The Tier‑1 sources describe the operation of the network via onchain interactions, not only the existence of a token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the criticality of the blockchain is not proven in Tier‑1 (similar clouds are possible in a centralized way).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There are onchain mechanics, but the lack of alternatives under the “replace the blockchain” test is not shown.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ALEPH.
  • Evidence: Tier‑1 — https://www.aleph.cloud/aleph-token
  • Why sufficient / why not (one line): The official token page describes its roles and contracts on the networks.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): ALEPH is used to pay for Aleph Cloud services (functions/instances/confidential VMs/web hosting).
  • Evidence: Tier‑1 — https://www.aleph.cloud/aleph-token
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the payment scenario.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): ALEPH staking is used to secure the network and distribute rewards.
  • Evidence: Tier‑1 — https://docs.aleph.im/nodes/staking
  • Why sufficient / why not (one line): The staking guide describes staking and rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of governance mechanics via the token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The sources describe payments/staking, but not governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token has not been assessed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): An analysis of payment/staking alternatives is needed.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://aleph.cloud/whitepaper Positioning and the AI/ML use case: “AI Supercloud”, GPU cloud, confidential AI/ML pipelines.
Tier‑1 https://docs.aleph.cloud/about/network/supported-blockchains/ Description of PAYG/balances/staking as the network’s interaction with blockchains.
Tier‑1 https://www.aleph.cloud/aleph-token Token utility (payment for services, staking, node operations) and the list of contracts.
Tier‑1 https://etherscan.io/token/0x27702a26126e0b3702af63ee09ac4d1a084ef628 Max Total Supply 500,000,000 ALEPH (supply parameters).

No comments to display

Back to top