> For the complete documentation index, see [llms.txt](https://docs.ethernity.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethernity.cloud/developer-guide/introduction.md).

# Introduction

Ethernity Cloud runs your code inside sealed hardware enclaves (Intel SGX) on a decentralized network — nobody, not even the node operator, can see your code's data while it runs, and every execution is proven on-chain. A **confidential dApp** is exactly that: backend functions that execute in an enclave, callable from any client, with results (and optionally persistent state) you can trust.

This guide is a build journey:

1. [How it works](https://docs.ethernity.cloud/developer-guide/the-ec-protocol) — the enclaves, the task lifecycle, and what "sealed" buys you (enough to make the rest make sense).
2. [Set up your environment](https://docs.ethernity.cloud/developer-guide/the-guide/environment-prerequisites) — the toolchain: Python or Node, Docker, a wallet, testnet tokens.
3. [Build & publish your first dApp](https://docs.ethernity.cloud/developer-guide/the-guide/build-and-publish-your-first-dapp) — scaffold, write a function, bake it into an enclave, register it on-chain.
4. [Run it](https://docs.ethernity.cloud/developer-guide/the-guide/running-your-dapp) — locally for free with `ecld-test`, then on the network with `ecld-run`.
5. [Add persistent state](https://docs.ethernity.cloud/developer-guide/the-guide/managing-dapp-state-esr) — encrypted, on-chain-anchored state with ownership and permissions.
6. [Inspect and troubleshoot](https://docs.ethernity.cloud/developer-guide/the-guide/inspecting-your-dapp) — free, read-only diagnostics with `ecld-info`, plus the [reference](https://docs.ethernity.cloud/developer-guide/the-guide/reference-and-troubleshooting) of commands and status codes.

You will build and publish a working confidential dApp in the next few pages — no prior blockchain experience required.