> For the complete documentation index, see [llms.txt](https://docs.zama.org/homepage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/homepage/readme.md). # Welcome to Zama's documentation Zama is an open source cryptography company that builds state-of-the-art Fully Homomorphic Encryption (FHE) solutions for blockchain and AI. ## Zama Confidential Blockchain Protocol *** A suite of tools and libraries for building confidential smart contracts and dApps on any chains.


Quick Start	Build your first contract step by step.	gradient2-2.png	https://docs.zama.ai/protocol/solidity-guides/getting-started/quick-start-tutorial
Solidity Guides	Write contracts to compute on encrypted data.	gradient3-2.png	https://docs.zama.ai/protocol/solidity-guides
Zama SDK	TypeScript SDK for Zama Protocol.	Vector-4.png	Stable
Protocol Apps	Explore the official Zama Protocol web apps.	Layer_1.png	https://docs.zama.org/protocol/protocol-guides
Code Examples	Review code examples for developers.	gradient2-2.png	Examples
Zama Protocol Litepaper	Read the Litepaper for protocol details.	gradient3-2.png	Zama Confidential Blockchain Protocol Litepaper

## Libraries *** Open-source libraries that support FHE computations.


TFHE-rs	Rust implementation of TFHE.	Bracket (1).png	https://docs.zama.ai/tfhe-rs
Concrete	TFHE Compiler in Python.	SDK (1).png	https://docs.zama.ai/concrete
Concrete ML	Machine learning models in FHE.	Example (1).png	https://docs.zama.ai/concrete-ml

## Supports *** * [Community forum](https://community.zama.ai/) * [Discord channel](https://discord.com/invite/zama) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zama.org/homepage/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.