All analysis was generated autonomously, without human review. Scores are analytical opinions drawn from the cited public sources, without hands-on testing. They are not audits, certifications, investment reports, purchasing advice, or evaluations of quality.
Zama is an open-source cryptography company whose software computes on data it never decrypts. Its Zama Protocol hides amounts and balances inside smart contracts on public blockchains such as Ethereum. Deploying an application on that protocol is free and needs no extra license. Zama's documentation says all of its technologies are patented and that commercial use of the open-source code requires buying a patent license. Protocol fees are burned, and new tokens are minted to pay operators, Zama among them. Zama says Bron paid staff salaries on Ethereum with the amounts encrypted. Press reports on its 2025 round put total funding above $150 million at a valuation above $1 billion. The reviewed sources carry no revenue figure, so the record shows adoption without showing what Zama earns.
| Description | Zama builds fully homomorphic encryption software whose Zama Protocol runs on existing layer-1 and layer-2 chains and keeps amounts and balances encrypted at all times, including while they are being processed. | [f1] |
|---|---|---|
| Founded | 2019 | [f2] |
| HQ | Paris, France | [f3] |
| Subsidiaries | Zama Switzerland AG (Swiss entity of the Zama Group named in the website legal notice.) , TokenOps (Token lifecycle management platform Zama acquired in May 2026. The Block reported that it would continue under its own brand.) | |
| Latest funding | Series B, $57 million (announced June 2025) | [f4] |
| Product | What it does |
|---|---|
| Zama Protocol | Confidentiality layer for existing L1 and L2 chains that lets smart contracts compute on encrypted inputs and state, with fees paid in the $ZAMA token. |
| FHEVM | Open-source framework at the core of the Zama Protocol that brings encrypted computation to EVM-compatible chains so developers write confidential contracts without cryptography expertise. |
| TFHE-rs | Open-source Rust implementation of the TFHE encryption scheme, supporting boolean and integer arithmetic directly on encrypted data. |
| Concrete | Open-source compiler that turns Python programs into equivalents running under fully homomorphic encryption, built on TFHE and LLVM. |
| Concrete ML | Open-source machine-learning toolkit built on Concrete, with scikit-learn-style and PyTorch conversion paths for inference and training on encrypted data. |
Cyber Defense Matrix
| Identify | Protect | Detect | Respond | Recover | |
|---|---|---|---|---|---|
| Devices Workstations, servers, phones, tablets, storage, network devices, IoT infrastructure, and similar hardware. | |||||
| Applications Software, interactions, and application flows on the devices. | |||||
| Networks Connections and traffic flowing among devices and apps, plus communication paths. | |||||
| Data Content at rest, in transit, or in use across devices, apps, and networks. | |||||
| Users The people using the devices, apps, networks, and data. |
The Zama Protocol keeps transaction amounts and balances encrypted while smart contracts compute on them, and TFHE-rs, Concrete, and Concrete ML let developers run computation on encrypted data offchain. These capabilities are mapped to the Cyber Defense Matrix. [f1]
How well the company can compete in its security market, scored across eight dimensions against public evidence.
| Dimension | Score | Rationale |
|---|---|---|
| Problem Clarity How precisely the company defines its problem, with evidence the problem exists at the scale claimed. | 3/5 | Zama names one problem and one buyer plainly, that public blockchains expose every amount and balance, which its homepage says has made onchain finance a non-starter for institutions in regulated markets. The reviewed sources describe that pain in the vendor's own terms and carry no independent measurement of it. [s1, s12] |
| Capability Depth How specific the technical capabilities are, with evidence beyond marketing claims such as docs and third-party validation. | 4/5 | Zama publishes protocol documentation, Solidity guides, an SDK, and a litepaper setting out its key-management and coprocessor architecture, and it hosts the encryption engine itself as open source. Blockscout explorers now support the ERC-7984 confidential token standard built on that work, which is validation from a party outside Zama. [s4, s12, s13, s17] |
| Market Timing Whether the market is ready for this product, with evidence that buyers are actively seeking solutions. | 3/5 | Zama names speed, application range, and developer difficulty as what it had to solve, and its June 2025 announcement says that took five years. Demand signals followed in 2026, including the institutional token distribution The Block reported for KAIO's partners, but most other adoption evidence is vendor-published, so buyer-side demand stays indirect. [s5, s9, s1] |
| Team Credibility Demonstrated domain expertise with public signals such as prior exits, publications, and industry recognition. | 4/5 | The International Association for Cryptologic Research named chief technology officer Pascal Paillier a 2025 Fellow for essential contributions to homomorphic encryption, recognition from the field's own professional body rather than from Zama. Chief executive Rand Hindi co-founded and led Snips, the Paris voice-AI company Sonos acquired for about $37.5 million in a deal that closed in November 2019. [s11, s19, s15, s3] |
| GTM Proof Evidence of actual traction (customers, revenue signals, partnerships) beyond stated intentions. | 3/5 | Zama names deployments including a payroll run on Ethereum mainnet, a confidential over-the-counter trade by GSR, and a confidentiality role for the T-REX Ledger, and The Block separately reported encrypted token distribution deployed for KAIO's partners including BlackRock, Hamilton Lane, and Brevan Howard. Most of the remaining references are vendor-published, and no independent source sizes the deployment base. [s1, s9] |
| Funding Efficiency Whether funding matches go-to-market ambition, with signs of capital-efficient growth. | 2/5 | Press reports on its 2025 round put Zama's total raised above $150 million at a valuation above $1 billion, and the reviewed record discloses no revenue or margin figure. Under the published design the protocol burns every fee and mints new tokens to reward operators, and no source measures the commercial return on the capital raised. [s6, s7, s4] |
| Category Clarity Whether the company creates or fits a recognizable category that buyers can quickly place in their stack. | 3/5 | Independent coverage places Zama consistently as a fully homomorphic encryption company building confidentiality for public blockchains, so its technology class is legible to anyone reading about it. The category is young enough that a buyer has to decide for itself whether a confidentiality layer for public blockchains belongs to a security budget or an infrastructure one. [s6, s7, s12] |
| Incumbent Defensibility How vulnerable the core value proposition is to absorption as a feature by a platform vendor. | 3/5 | Zama says building this took five years, and its threshold key-management network runs across named operators including Ledger, Fireblocks, and Open Zeppelin. Zama publishes the encryption engine as open source, and its own documentation says commercial use of that code requires buying the company's patent license. [s5, s4, s13, s18] |
Every transaction on a public blockchain exposes amounts and balances to anyone, and Zama's homepage says that exposure has made onchain finance a non-starter for institutions operating in regulated markets. The Zama Protocol keeps those values encrypted while smart contracts compute on them, running on chains that already exist instead of on a new one.
The uses Zama names are payroll, over-the-counter trading, tokenized real-world assets, and token distribution, and the deployments it points to are in the same set.
Zama's documentation still describes the company as building encryption for blockchain and AI, and the same GitHub organization hosts machine-learning libraries alongside the blockchain code. Its 2025 announcement says it had licensed the technology to dozens of companies across both, and no machine-learning deployment is named in the reviewed sources, so the size of that side of the business stays undocumented. [s1, s2, s5, s13, s17, s18]
The Zama Protocol is a confidentiality layer on top of chains that already exist. Blockscout, whose explorers support confidential tokens built on it, describes it the same way Zama does, as something that works on top of Ethereum and other EVM networks rather than as a new chain of its own.
Three pieces do the work underneath. Fully homomorphic encryption keeps values encrypted while they are being computed on, a multi-party key network splits the decryption key across operators, and zero-knowledge proofs check that a user encrypted their inputs correctly. Zama's litepaper says the protocol runs under delegated proof-of-stake across 18 operators, initially 13 key-management nodes and 5 coprocessors.
Developers reach all of that through a Solidity library. Zama's announcement says they can build confidential applications with no knowledge of cryptography, and its homepage says the work needs no new language. The encryption engine is published on GitHub, where the same organization also hosts TFHE-rs, and Zama's documentation groups Concrete and Concrete ML alongside it as open-source libraries. Zama's own documentation says commercial use of that code requires buying the company's patent license. [s12, s4, s5, s1, s13, s17, s18]
Zama positions itself as infrastructure other people's confidential applications run on. Hinkal, which sells a confidential settlement product, publishes a comparison that describes Zama as an FHE infrastructure provider offering TFHE-rs, fhEVM, and Concrete ML to teams building their own encrypted computation, and says Zama powers Fhenix and Inco.
That position cuts both ways. Zama publishes the engine, and a rival can read the same code. Zama's own documentation says commercial use of that code requires buying the company's patent license, and its litepaper says using the technology outside the Zama Protocol requires a license too.
The same Hinkal comparison frames the buyer's choice as one between an application and a toolkit, positioning its own confidential settlements against what it calls developer infrastructure from Zama and Inco. That is a rival's characterization, and no other head-to-head framing appears in the reviewed sources. [s16, s4, s13, s18]
Zama reaches its market through the developers and protocols that build on it. Deploying an application is free and needs no extra license, and the protocol charges a fee in $ZAMA tokens for each gateway operation, whether that is verifying an encrypted input, decrypting a value, or bridging one between chains.
Named deployments exist. Zama's homepage describes a payroll run in which Bron's finance chief paid team salaries on Ethereum mainnet in confidential USDT, an over-the-counter trade GSR executed with the amounts encrypted, and a role as the confidentiality layer for the T-REX Ledger. The Block reported separately that KAIO deployed encrypted token distribution for partners including BlackRock, Hamilton Lane, and Brevan Howard. Zama acquired the token lifecycle platform TokenOps in May 2026, and The Block reported that TokenOps would continue under its own brand.
The record thins past those names. No contract value or revenue figure appears in the reviewed sources, and the litepaper says the protocol burns every fee and mints new tokens to pay operators. Zama's own 2025 announcement says it had been licensing its encryption technology to dozens of companies across blockchain and AI, and its litepaper adds hosted services and premium support beside that. Beyond the count of companies, the sources put no size on any of it. [s1, s5, s9, s4, s20]
Zama employs a cryptographer whose recognition comes from outside the company. The International Association for Cryptologic Research named chief technology officer Pascal Paillier a 2025 Fellow for essential contributions to homomorphic encryption and service to the cryptologic research community.
Chief executive Rand Hindi has built and sold a privacy company before. A Sonos filing with the Securities and Exchange Commission quotes him as co-founder and chief executive of Snips, a Paris voice-AI company built on keeping speech processing on the device, which Sonos acquired for about $37.5 million in a deal that closed in November 2019.
AWS's case study names Hindi and Paillier as Zama's founders and says Paillier led the research team that worked on making the encryption practical. Zama's legal notice names Hindi as chief executive and Jeremy Bradley as managing director and chief operating officer, and Bradley spoke for the company in Cointelegraph's reporting on the 2026 contract freeze. [s11, s19, s15, s3, s8]
Zama publishes a responsible disclosure policy and a bug bounty scope, and no certification or attestation appears on the probed surfaces. The security page sets out reporting channels, a safe harbour for researchers, and in-scope classes covering smart contract, key management, and consensus issues.
Zama also points to code review. Its litepaper says the protocol is being audited by Trail of Bits and Zenith with more than 34 audit-weeks spent so far, which is the vendor's account of work under way rather than a published report a buyer can read.
Compliance here is being built into the product instead of certified around it. Hindi said Circle froze about $12.5 million of USDC inside Zama's cUSDC contract in 2026 after a court order, and the court later lifted it. Zama then said it would accelerate its compliance roadmap, add automatic enforcement of the compliance actions asset issuers take, and set up a compliance council. [s14, s4, s8]
| Company | Relationship | Note |
|---|---|---|
| Hinkal | competes with | Hinkal publishes a comparison page positioning its confidential settlement product against Zama. |
| Inco | competes with | A rival's published comparison names Inco alongside Zama as a developer confidentiality option, and the same page says Zama powers Inco. |
A closer look at the company's product strategy, measuring how defensible it is against market forces and examining the eight areas behind it.
reinforce or reposition
Zama says it spent five years making fully homomorphic encryption fast and usable enough for developers. Its protocol runs across named operators including Ledger, Fireblocks, and Open Zeppelin. The encryption engine is published as open source, and Zama's own documentation says all of its technologies are patented and that commercial use of that code requires buying a patent license. The reviewed sources name no private dataset and no security certification. A funded rival can read the same code, and the litepaper says using that technology outside the Zama Protocol requires a license. The patent position around published code is the most durable thing the record shows.
| Dimension | Score | Rationale |
|---|---|---|
| Value Delivery Does the product sell software as the product, or judgment, trust, or accountability with software as the delivery mechanism. | 1/3 | A customer's own developers build confidential applications with a Solidity library and deploy them on a protocol that named operators run. The reviewed sources describe no engagement in which Zama takes on a customer's outcome, so what is delivered is a software product. |
| Switching Cost How expensive leaving is for a customer: data portability, integrations, learned workflows, network effects, regulatory data residency. | 2/3 | An application built on the Zama Protocol depends on the gateway that orchestrates it, the coprocessors that run its encrypted computations, and the key-management nodes that store the key shares, which is real integration depth. That depth is inbound evidence, and the cited record neither documents what exit would cost nor sizes a migration. Customer logic does live in the contracts, because the litepaper says applications define their own compliance rules there, but that logic is ordinary Solidity rather than a vendor language of the kind the code-embedded route would need. |
| Compliance Moat Whether certifications, liability acceptance, or audit trails block an easy replacement. | 1/3 | The reviewed sources carry a responsible disclosure policy and no certification or attestation on any probed surface, and the litepaper leaves regulatory compliance to the applications built on the protocol. The cited record shows no certification or liability commitment that would stand between a buyer and a replacement, and Zama said after the 2026 freeze on its confidential USDC contract that it would accelerate its compliance roadmap. |
| Problem Complexity Whether the product requires ML, optimization, real-time systems, or years of specialized expertise. | 3/3 | Zama says fully homomorphic encryption had been too slow, too limited, and too hard for developers, and that solving that took its team five years. Its protocol combines that encryption with zero-knowledge input proofs and multi-party key management run across 18 operators, and the International Association for Cryptologic Research recognized its chief technology officer for contributions to homomorphic encryption. |
| Buyer Profile Whether buyers are SMB operators, mid-market IT teams, or regulated enterprises and governments with procurement gates. | 2/3 | Zama addresses regulated financial institutions, and The Block reported encrypted distribution deployed for KAIO partners including BlackRock, Hamilton Lane, and Brevan Howard. That deployment reached those institutions through KAIO rather than through Zama, and no cited source names a party that contracts with Zama, which keeps the evidenced buyer below the enterprise procurement level. |
| Layer Whether the product is an end-user application, a platform with application features, or infrastructure other applications depend on. | 3/3 | A confidential application on the Zama Protocol cannot run without the gateway that orchestrates it, the coprocessors that compute on its ciphertexts, and the key-management nodes that decrypt them, so the protocol is execution infrastructure other software depends on. Blockscout built explorer support on top of that layer. |
| Proprietary Data, Content, or IP Whether the product accumulates datasets, content licenses, or IP that a rival cannot recreate from scratch. | 2/3 | Zama publishes TFHE-rs and FHEVM on GitHub and groups Concrete and Concrete ML with them as open-source libraries, and its own documentation says all of its technologies are patented and that commercial use of that code requires buying a patent license. That patent position is the accumulated asset the record names, and the reviewed sources do not set out what the patents cover or whether a rival could design around them. |
Zama aims at institutions that want to use public blockchains and cannot afford to show what they are doing. Its homepage says the exposure of amounts and balances has made onchain finance a non-starter for institutions operating in regulated markets, and the uses it names are tokenized real-world assets, corporate payments, payroll, confidential trading, and token distribution.
Named use of the protocol appears across payroll, trading, block exploration, and token distribution. Zama's homepage says Bron ran payroll on the protocol and GSR executed a trade on it, Blockscout added explorer support for its confidential tokens, and The Block reported that KAIO, an institutional real-world asset protocol built by WebN Group and Nomura's Laser Digital, deployed encrypted distribution for partners including BlackRock. The reviewed sources do not identify who contracts with Zama or on what terms.
Zama's documentation still describes the company as serving blockchain and AI, and its 2025 announcement says it had licensed the technology to dozens of companies across both. No machine-learning deployment is named in the reviewed sources, so a buyer weighing those libraries has published code to read and no reference to check.
The capability Zama sells is arithmetic on data nobody has decrypted. Its protocol keeps amounts and balances encrypted at all times, including while a smart contract processes them, and it runs on chains that already exist rather than asking users to move to a new one.
Three cryptographic techniques divide the work. Fully homomorphic encryption does the computing, a multi-party key-management network holds the decryption key in shares across separate operators, and zero-knowledge proofs verify that a user encrypted their inputs correctly. The litepaper says 18 operators run the protocol under delegated proof-of-stake, initially 13 key-management nodes and 5 coprocessors.
Zama does the AI work in its machine-learning libraries, and the protocol handles blockchain confidentiality only. Concrete ML offers model classes close to those in scikit-learn and converts PyTorch models, so a team can run inference or training on encrypted data. Zama's documentation still describes the company as building for blockchain and AI, and no machine-learning deployment is named in the reviewed sources.
Zama runs a developer channel and a direct sales effort at the same time. Deploying an application on the protocol is free and needs no extra license, and its legal notice names a commercial team that uses a prospect-identification tool to find professional contacts.
Zama has described licensing as its commercial model. Its litepaper says the FHE libraries are free for non-commercial use and require an enterprise license for commercial use, and it lists hosted services and premium support beside them. Its June 2025 announcement says the technology had been licensed to dozens of companies across blockchain and AI, and beyond that count the reviewed sources put no contract value or revenue figure on any of it.
Partnerships carry the rest. Zama names T-REX Ledger, Bron, and GSR among the deployments running on its protocol, Blockscout added explorer support for its confidential tokens, and The Block reported KAIO's encrypted distribution for partners including BlackRock, Hamilton Lane, and Brevan Howard. In May 2026 Zama bought TokenOps, a token lifecycle platform that by its own account had processed more than $2 billion in distributions, and The Block reported that TokenOps would continue under its own brand.
Zama prices the protocol per operation rather than per seat or per customer. The litepaper says a user pays a fee in $ZAMA tokens to have encrypted inputs verified, to decrypt a value, and to move an encrypted value between chains.
Fees are not collected as a payment to Zama. Under the published design the protocol burns every fee and mints new tokens to reward the operators who run the network, and the litepaper lists Zama itself among those operators. The reviewed sources put no figure on what that arrangement returns to the company.
The libraries are priced separately from the protocol. The litepaper says they are free for non-commercial use, prototyping, research, and personal projects, and that commercial use requires an enterprise license or building on a protocol that already holds one.
Zama delivers a network that named operators run. The litepaper says 18 operators run the protocol under delegated proof-of-stake, initially 13 key-management nodes and 5 coprocessors, and it names Conduit, DFNS, Etherscan, Figment, Fireblocks, InfStones, Layer Zero, Ledger, Omakase, Open Zeppelin, Stake Capital, Unit 410 and Zama among the key-management nodes.
Customers integrate through code. A developer imports a Solidity library and writes a confidential contract, Zama's announcement says that takes no knowledge of cryptography, and its homepage says the work needs no new language.
The libraries themselves ship as source. TFHE-rs and the FHEVM framework are published on GitHub under the zama-ai organization, and Zama's documentation groups TFHE-rs, Concrete, and Concrete ML as open-source libraries, so a team can run the encryption without touching the protocol. Zama's own documentation says commercial use of those libraries requires buying the company's patent license.
Zama's published assurance is a disclosure policy and a bug bounty. The security page sets out reporting channels through GitHub Security Advisories and email, a safe harbour for good-faith research, and an in-scope list covering smart contract, key management, and consensus issues.
No certification or attestation appears on the probed trust surfaces or anywhere else in the reviewed sources.
What Zama points to instead is code review and partnership. Its litepaper says Trail of Bits and Zenith are auditing the protocol with more than 34 audit-weeks spent so far, and no audit report appears in the reviewed sources. Its press page also carries a Hypernative deployment to monitor its confidential token contracts and an Elliptic partnership for compliance screening. Hindi said Circle froze about $12.5 million of USDC inside Zama's cUSDC contract in 2026 after a court order, and the court later lifted it. Zama then said it would add automatic enforcement of the compliance actions asset issuers take and establish a compliance council.
Zama is built as a platform other people ship on. Its homepage says the protocol runs natively on any L1 or L2 rather than as a chain of its own, so an application can reach it without moving its users to a new network.
The ecosystem shows up in who runs and extends it. Named infrastructure companies including Ledger, Fireblocks, Open Zeppelin, and Etherscan staff the key-management network, and Blockscout built explorer support for the ERC-7984 confidential token standard.
Zama publishes the engine that draws those builders, and rivals can read it too. Hinkal's comparison page says Zama powers Fhenix and Inco. Its litepaper says applications built on the Zama Protocol need no extra license, while forking or using the technology outside the protocol does require one.
Zama employs research talent the field recognizes on its own terms. The International Association for Cryptologic Research named chief technology officer Pascal Paillier a 2025 Fellow for essential contributions to homomorphic encryption and service to the cryptologic research community.
Chief executive Rand Hindi has built and sold a privacy company before. A Sonos filing with the Securities and Exchange Commission quotes Hindi as co-founder and chief executive of Snips, a Paris voice company built on keeping speech processing on the device, which Sonos acquired for about $37.5 million in a deal that closed in November 2019. Zama's legal notice names Hindi as chief executive and Jeremy Bradley as managing director and chief operating officer.
The company presents itself as research-led. Its About page describes the team as cryptographers, engineers, and entrepreneurs, and the AWS case study says Paillier led the research team that worked on making the encryption practical for machine learning and blockchain.
| Id | Source | Tier | Accessed |
|---|---|---|---|
| f1 | Zama: homepage | official | 2026-08-17 |
| f2 | French government company-register API record for ZAMA SAS (SIREN 879243319) | regulatory | 2026-08-17 |
| f3 | Zama: legal notice | official | 2026-08-17 |
| f4 | CoinDesk: FHE Pioneer Zama Raises $57M, Becomes First Fully Homomorphic Encryption Unicorn | press | 2026-08-17 |
This site is an experimental research aid created by Zeltser Security Corp. All its data gathering and analysis was performed autonomously without human review, and it can contain errors of fact, interpretation, and judgment that a human reviewer might catch.
The analyses are statements of opinion, not statements of fact. Machine analysis produced the scores, summaries, and matrix placements by weighing the public sources each page cites, and reasonable people can weigh the same sources differently. Where a page states a fact, it cites the public source and the date it was checked, and the statement is only as accurate as that source. Unless a profile expressly says otherwise, the analysis involves no hands-on testing and no independent validation of any company's products or services.
Nothing here is professional, security, legal, financial, investment, or purchasing advice, and nothing here is a recommendation to invest in, do business with, or avoid any company. Inclusion of a company is not an endorsement, and absence of a company is not a judgment about it. Reading this site creates no advisory or client relationship. Verify any detail you plan to act on against the vendor's current materials.
The content is provided "as is" and "as available," with all warranties disclaimed, express or implied, including merchantability, fitness for a particular purpose, accuracy, and non-infringement. No entry is warranted to be complete, current, or correct. Companies change, vendors update their claims, sources can be wrong, and automated analysis can misread them.
To the fullest extent permitted by law, the operator, Zeltser Security Corp, is not liable for any damages that arise from using this site or relying on its content, including direct, indirect, incidental, special, and consequential damages and lost profits, even if advised that such damages were possible. If you are dissatisfied with the site or disagree with these terms, your remedy is to stop using it.
Entries link to vendor pages, press coverage, and other external sites that Zeltser Security Corp does not control and is not responsible for. A link is not an affiliation with the destination or an endorsement of it. Product and company names and trademarks are the property of their owners, used here nominatively to identify the companies described. Short quotations from cited sources appear for identification and commentary.
Use, quotation, automated retrieval, and redistribution of the content are governed by the Terms of Use at cybercompanyprofiles.com/terms, which permit personal and internal business use with attribution and prohibit republication and resale.