EigenCloud

• Name: EigenCloud
• URL: https://docs.eigencloud.xyz/
• Category: verifiable cloud stack / TEE-backed offchain compute / agent deployment platform
• Tags: ethereum-ecosystem
• Summary: EigenCloud packages TEE-backed offchain compute into a developer cloud stack. The useful part is not the verifiable AI gloss; it is the exposed trust stack: enclave hardware, cloud attestation, coordinator-managed deployment, KMS-gated key release, onchain deployment records, and higher-level agent templates on top. Because the current coordinator and KMS path is still explicitly Eigen Labs-operated, this product note now works best alongside the separate company-layer companion eigen-labs.
• What it does:
  • Packages EigenLayer-adjacent services such as EigenDA, EigenCompute, and AgentKit into one developer-facing stack
  • Lets developers deploy Dockerized apps or agents into Intel TDX trusted execution environments tied to specific container digests
  • Gives each deployed app its own cryptographic identity and wallet so it can sign, hold funds, and operate as a persistent service
  • Uses a coordinator plus KMS flow to verify attestation and release keys only to approved workloads matching recorded deployments
  • Adds verification surfaces such as onchain deployment records, dashboards, and roadmap items around stronger trust guarantees
  • Ships AgentKit as the opinionated top layer, with templates, policy files, and prepaid compute / inference billing on top of EigenCompute
• Key claims:
  • EigenCloud is more useful as a control-surface note than as a finished decentralization story. The docs make the trust decomposition unusually legible instead of hiding it behind generic verifiability language.
  • EigenCompute is the core mechanism page. It binds code identity, enclave attestation, wallet identity, and secret release into one stack.
  • The present system is explicitly transitional. The docs say mainnet alpha still depends on Intel TDX, Google Confidential Space attestation, and a single EigenLabs-operated KMS.
  • That makes the current trust model closer to hardened hosted infrastructure than to an open compute market. The roadmap promises threshold KMS, stronger liveness guarantees, forced inclusion, and better verification, but those are still promises.
  • AgentKit matters because it shows how quickly low-level compute turns into an opinionated agent-control product once templates, constitutions, connectors, and billing are layered on top.
  • The durable analytical takeaway is simple: verifiable offchain compute is not one thing. In EigenCloud it splits across deployment publication, attestation, orchestration, key custody, verification UX, and product packaging.
• Whitepaper: A dedicated EigenCloud_Whitepaper.pdf exists in the official docs repository, but this entry is grounded primarily in the reviewed official docs pages collected in ../whitepapers/eigencloud-primary-sources-2026-05-15.md.
• Sources:
  • https://docs.eigencloud.xyz/
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/docs/eigencloud/eigencloud-overview.md
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/docs/eigencompute/get-started/eigencompute-overview.md
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/docs/eigencompute/concepts/eigencompute-architecture.md
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/docs/eigencompute/concepts/security-trust-model.md
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/docs/eigencompute/concepts/trust-guarantees.md
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/docs/agentkit/get-started/agentkit-overview.mdx
  • https://raw.githubusercontent.com/Layr-Labs/eigencloud-docs/main/static/pdf/EigenCloud_Whitepaper.pdf

Internal linkages

• Company-layer companion: eigen-labs.
• Strongest verifiable-compute comparison points: cartesi, bacalhau, and opengradient.

Protocol / company boundary

• Keep this note on the product and architecture surface: TEE-backed execution, attestation, deployment publication, key-release flow, and the higher-level AgentKit packaging that turns EigenCompute into a developer-facing cloud stack.

• Use eigen-labs when the sharper question is who runs the coordinator, who currently operates the single mainnet-alpha KMS, who controls the hosted signup / billing / docs / legal shell, and where builders inherit an explicitly company-run trust boundary rather than only a protocol or product mechanism.

• That split matters because the current trust story is not only Intel TDX + attestation + onchain deployment records; the docs also name Eigen Labs directly as the present operator at the coordinator and KMS layers.

• Last reviewed: 2026-08-08 UTC