Zama

• Name: Zama
• URL: https://www.zama.org/
• Category: confidential-compute infrastructure company / FHE tooling operator / FHEVM commercialization and licensing entity
• Tags: ethereum-ecosystem
• Summary: Zama belongs as an entity note. fhevm is the framework note. Zama is the company controlling the docs, repos, product packaging, and commercial licensing around that stack, plus the broader TFHE / Concrete tooling line. The useful question here is who steers and monetizes the confidential-compute bundle, not whether one more privacy protocol exists.
• What it does:
  • Publishes the broader Zama Confidential Blockchain Protocol surface while maintaining FHEVM as the clearest lower-layer confidential-EVM framework note
  • Maintains the public repos, docs, examples, relayer and app surfaces, and surrounding developer workflow for encrypted smart-contract development
  • Ships broader FHE tooling beyond blockchain, including TFHE-rs, Concrete, and Concrete ML, which makes the company bigger than one protocol wrapper
  • Operates the commercialization boundary through its licensing posture, with open development access but separate patent licensing for commercial use
• Key claims:
  • The official docs describe the Zama Confidential Blockchain Protocol as a suite of tools and libraries for building confidential smart contracts and dApps, which is broader than a single deployed chain or app
  • The public FHEVM repo, docs corpus, and protocol-app materials show Zama controlling a full product surface: framework code, gateway and coprocessor components, developer guides, and user-facing apps
  • Zama’s open-source licensing post matters because it makes the company boundary explicit: development and experimentation are broadly open, while commercial users need a separate patent license
  • That licensing and repo-control posture is why this note belongs under companies. FHEVM is the cleaner protocol/framework read; Zama is the operator and commercialization layer around it
• Whitepaper: Official FHEVM whitepaper saved locally as ../whitepapers/zama-fhevm-whitepaper.pdf. For the entity note, the clearest source of truth remains Zama’s docs, repos, and licensing materials; see ../whitepapers/zama-primary-sources-2026-04-27.md.
• Sources:
  • https://www.zama.org/
  • https://docs.zama.org/homepage/readme.md
  • https://docs.zama.org/protocol/solidity-guides/getting-started/quick-start-tutorial
  • https://docs.zama.org/protocol/solidity-guides.md?ask=What%20capabilities%20do%20the%20Solidity%20guides%20and%20library%20offer%20for%20encrypted%20smart-contract%20development%3F
  • https://docs.zama.org/protocol/protocol-guides.md?ask=Summarize%20the%20official%20Zama%20Protocol%20applications%20and%20what%20roles%20they%20play%20for%20developers%20or%20users.
  • https://github.com/zama-ai
  • https://github.com/zama-ai/fhevm
  • https://raw.githubusercontent.com/zama-ai/fhevm/main/fhevm-whitepaper.pdf
  • https://www.zama.org/post/open-source

Internal linkages

• Alias / prior project-layer entry: zama.
• Canonical lower-layer framework note: fhevm.
• Useful confidential-EVM comparison once the company boundary is clear: fhenix.

Protocol / company boundary

• There is no especially useful standalone Zama protocol boundary doing separate analytical work here.
• The cleaner split is [[../projects/fhevm]] for the lower-layer framework and [[../companies/zama]] for the repo, docs, licensing, and commercialization boundary around the broader confidential-compute stack.
• Keep zama only as an alias so legacy links keep resolving without pretending Zama itself is a deployed protocol peer.

Control surface

• Authority sits in repo stewardship, release cadence, protocol and app packaging, documentation, licensing and patent terms, and which parts of the confidential-compute stack get productized versus left as libraries.

• Keep the split clean: Zama is the entity and commercialization boundary; FHEVM is the lower-layer framework note.

• Last reviewed: 2026-08-10 UTC