Clique

Name: Clique
Brand: Clique

AI Native

Clique builds MPC/TEE enterprise solutions for confidential compute and secure systems

Est 2022|Valuation $31M|Raised $11M|22 Ref Customers

LinkedIn 970|Web traffic 10K|FTEs 16|HQ San Francisco, California, US

Published Oct 15, 2026

01Common complaints

- Regulated enterprise procurement (finance, healthcare, government) that mandates SOC 2 or ISO certifications as part of initial vendor evaluation: public materials do not disclose such certifications. - Organizations whose security posture disallows reliance on TEEs (for example, environments that prohibit enclave-based trust or where TEE risk is unacceptable): alternatives include zero-knowledge-based approaches or centralized trusted services that match the organization’s risk model. - Small teams seeking rapid time-to-value and low integration overhead: implementing attestation and oracle logic can require substantial engineering effort compared with simpler managed services. - Budget-constrained buyers that need transparent, self-serve pricing and predictable costs.

Deal disqualifiers (poor fit)

Organizations that require publicly documented third-party compliance certifications before procurement.
Teams that require fully self-serve pricing and instant onboarding.
Use cases that are purely Web2 and do not benefit from on-chain verification or attestations.

Publicly visible limitations

Public product detail on the main site is limited in places; technical details are often found in documentation rather than on the marketing homepage.
No public pricing was identified.
No publicly documented SOC 2 or ISO compliance artifacts were found.

Architectural limitations typical of the approach (due diligence items)

Reliance on TEEs introduces a specific threat model that should be clearly documented (attestation pipeline, key management, patch and disclosure SLAs, side-channel mitigations).
The integrity of attestation-based claims depends on end-to-end design elements such as attestation validity checks, replay protection, handling of chain reorganizations, and secure key handling.

Roadmap notes

Documentation references plans to support additional enclave technologies and hardware (AMD SEV-SNP, Intel TDX, NVIDIA H100). Public timelines and firm commitments were not available in the reviewed materials.

02Why they buy

(Validated primarily by vendor documentation and vendor-hosted case studies; independent verification is recommended.) - A TEE network aimed at executing off-chain compute tasks and producing attestations or proofs that smart contracts can verify. - Capability to perform private TLS/API calls from within an enclave and produce attestations linking those calls to on-chain outcomes. - Integrations and workflow templates oriented toward campaign management, social verification, and incentive distribution for Web3 use cases. Caveat: These capabilities are documented by the vendor and supported by vendor-hosted case studies; procurement teams should request audits, reference customers, and operational SLAs for independent validation.

Caveat: These capabilities are documented by the vendor and supported by vendor-hosted case studies; procurement teams should request audits, reference customers, and operational S…

Key Differentiator

03Field reports

What’s available publicly (major limitation)

There is limited independent user review content for Clique (vendor website) on mainstream B2B review platforms. Searches on major review sites and directories returned few or no clearly attributable user reviews for the product itself. Some directory entries appear to reference unrelated products with the same or similar name.

Vendor-hosted testimonials (case-study language)

Clique publishes case studies that include vendor-hosted testimonials and promotional language. These materials present favorable statements about the product and vendor collaboration; they should be treated as marketing collateral and corroborated through independent references where possible. Example: A vendor-hosted Arbitrum Arcade case study contains a testimonial that praises Clique's technical contribution to the project. The statement is vendor-provided and uses promotional language; it has not been independently verified in the public record.

Community discussions (Reddit / Hacker News)

There were few direct, attributable discussions specifically about the vendor product quality; searches for "clique" are noisy due to other uses of the word.
Community discussions about TEEs and confidential computing raise common concerns that are applicable to Clique’s approach:
- Risk of hardware-level vulnerabilities and side-channel attacks.
- Implementation complexity and operational overhead.

Likely customer value (inferred from case studies and documentation)

Mechanisms to reduce Sybil attacks without full KYC for certain use cases.
Tools for large-scale incentive distribution with verifiable eligibility signals.
Private API access (TLS oracles) where credentials must be protected during off-chain data retrieval.

Reasons customers might avoid or leave (inferred)

Need for formal compliance attestations (SOC 2 Type II, ISO 27001) that are not publicly documented.
Concerns about the trust model associated with TEEs (vendor lock-in to specific enclave technologies, historical SGX issues, patch management).
Preference for more standardized solutions (cloud vendor confidential VMs plus in-house attestation layers) or simpler managed services.

1) Arbitrum Arcade (vendor-hosted case page)

Stated results (vendor-provided): - A large user base, a substantial number of attestations issued, and a high volume of compute pipeline executions. Critical evaluation: - Metrics are presented without a detailed methodology (for example, definitions of "user" or what constitutes a "pipeline execution"). - Attribution between the vendor’s role and the campaign design by the protocol should be validated before inferring causal impact.

2) Trip.com "Trekki Trip" NFT collection (vendor-hosted case page)

Stated results (vendor-provided): - A large user base, several thousand NFTs minted, and a notable amount of cryptocurrency raised. - Clique was used to evaluate social account quality and engagement signals for eligibility decisions. Critical evaluation: - Results are not independently audited in public sources. - Campaign outcomes that depend on social signals require careful attention to gaming risks; resilience depends on the specific detection rules and configurations used.

3) Other ecosystem examples in documentation

Documentation cites integrations and examples with various ecosystems and reports volumes or partner names. These should be corroborated against on-chain data, partner announcements, or third-party reports for validation.

04Best fit

Company sizes

Mid-market to enterprise Web3 organizations and well-funded protocols (e.g., teams ranging from small to large sizes with significant token treasuries or marketing budgets).
Brands running sizable NFT or loyalty activations with measurable growth targets.

Industries / verticals

Web3: L2 ecosystems, DeFi, gaming, consumer dApps.
Potential non-crypto verticals where private API calls plus verifiable proof are required, though prominent public examples remain crypto-native.

Roles and personas

Decision makers: Head of Ecosystem, Growth Lead, Protocol Engineering Lead, Security/Infrastructure Lead.
End users: smart contract engineers, backend engineers implementing campaign logic, data engineers defining eligibility rules.

Qualification criteria (good fit)

Organizations that require verifiable off-chain computation feeding on-chain logic.
Use cases that require protection of secrets or credentials (API keys, OAuth tokens) during off-chain data access.
Programs that operate at scale for incentive distribution and require tooling to mitigate Sybil attacks.

05The pitch

What the product does (objective summary)

Clique describes its offering as confidential computing infrastructure intended for enterprise use in Web3 and smart-contract-adjacent scenarios. The product centers on a TEE (Trusted Execution Environment) network that runs off-chain computation with confidentiality and verifiability, and can anchor results on-chain via attestations or proofs. Key product areas visible in public materials: - TEE Network / “off-chain AWS Lambda”: Executes workloads inside TEEs (documentation emphasizes Intel SGX and references plans to support AMD SEV-SNP, Intel TDX, and NVIDIA H100) and returns verifiable results that smart contracts can consume. - TLS Oracle / Arbitrary TLS calls: Enables API/TLS calls from within a TEE to retrieve off-chain data while keeping credentials inside the enclave and producing attestations of the operation. - Attestations / data attestation tasks: Framework for producing verifiable on-chain attestations about off-chain facts (for example, activity or reputation signals). - Clique Wallet (custodial, TEE-controlled keys): Describes a wallet architecture in which keys are generated, stored, and used inside a TEE.

Target market & positioning

Public materials and examples indicate a focus on:

Web3 ecosystems (L2s, DeFi, games, NFT campaigns) that require Sybil resistance, incentive distribution, and proof of off-chain behavior.
Protocols and brands running large-scale campaigns, airdrops, or loyalty/incentive programs.
Enterprise Web3 teams that require verifiable off-chain computation and confidential data access (for example, protecting API keys, OAuth tokens, or private model inputs).

Get a comprehensive analysis of Clique including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Regulated enterprise procurement (finance, healthcare, government) that mandates SOC 2 or ISO certifications as part of initial vendor evaluation: public materials do not disclose such certifications.
Organizations whose security posture disallows reliance on TEEs (for example, environments that prohibit enclave-based trust or where TEE risk is unacceptable): alternatives include zero-knowledge-based approaches or centralized trusted services that match the organization’s risk model.
Small teams seeking rapid time-to-value and low integration overhead: implementing attestation and oracle logic can require substantial engineering effort compared with simpler managed services.
Budget-constrained buyers that need transparent, self-serve pricing and predictable costs.

Deal disqualifiers (poor fit)

Organizations that require publicly documented third-party compliance certifications before procurement.
Teams that require fully self-serve pricing and instant onboarding.
Use cases that are purely Web2 and do not benefit from on-chain verification or attestations.

Publicly visible limitations

Public product detail on the main site is limited in places; technical details are often found in documentation rather than on the marketing homepage.
No public pricing was identified.
No publicly documented SOC 2 or ISO compliance artifacts were found.

Architectural limitations typical of the approach (due diligence items)

Reliance on TEEs introduces a specific threat model that should be clearly documented (attestation pipeline, key management, patch and disclosure SLAs, side-channel mitigations).
The integrity of attestation-based claims depends on end-to-end design elements such as attestation validity checks, replay protection, handling of chain reorganizations, and secure key handling.

Roadmap notes

Documentation references plans to support additional enclave technologies and hardware (AMD SEV-SNP, Intel TDX, NVIDIA H100). Public timelines and firm commitments were not available in the reviewed materials.

02Why they buy

(Validated primarily by vendor documentation and vendor-hosted case studies; independent verification is recommended.)

A TEE network aimed at executing off-chain compute tasks and producing attestations or proofs that smart contracts can verify.
Capability to perform private TLS/API calls from within an enclave and produce attestations linking those calls to on-chain outcomes.
Integrations and workflow templates oriented toward campaign management, social verification, and incentive distribution for Web3 use cases.

Caveat: These capabilities are documented by the vendor and supported by vendor-hosted case studies; procurement teams should request audits, reference customers, and operational SLAs for independent validation.

Caveat: These capabilities are documented by the vendor and supported by vendor-hosted case studies; procurement teams should request audits, reference customers, and operational S…

Key Differentiator

03Field reports

What’s available publicly (major limitation)

Vendor-hosted testimonials (case-study language)

Example: A vendor-hosted Arbitrum Arcade case study contains a testimonial that praises Clique's technical contribution to the project. The statement is vendor-provided and uses promotional language; it has not been independently verified in the public record.

Community discussions (Reddit / Hacker News)

There were few direct, attributable discussions specifically about the vendor product quality; searches for "clique" are noisy due to other uses of the word.
Community discussions about TEEs and confidential computing raise common concerns that are applicable to Clique’s approach:
- Risk of hardware-level vulnerabilities and side-channel attacks.
- Implementation complexity and operational overhead.

Likely customer value (inferred from case studies and documentation)

Mechanisms to reduce Sybil attacks without full KYC for certain use cases.
Tools for large-scale incentive distribution with verifiable eligibility signals.
Private API access (TLS oracles) where credentials must be protected during off-chain data retrieval.

Reasons customers might avoid or leave (inferred)

Need for formal compliance attestations (SOC 2 Type II, ISO 27001) that are not publicly documented.
Concerns about the trust model associated with TEEs (vendor lock-in to specific enclave technologies, historical SGX issues, patch management).
Preference for more standardized solutions (cloud vendor confidential VMs plus in-house attestation layers) or simpler managed services.

1) Arbitrum Arcade (vendor-hosted case page)

Stated results (vendor-provided):

A large user base, a substantial number of attestations issued, and a high volume of compute pipeline executions.

Critical evaluation:

Metrics are presented without a detailed methodology (for example, definitions of "user" or what constitutes a "pipeline execution").
Attribution between the vendor’s role and the campaign design by the protocol should be validated before inferring causal impact.

2) Trip.com "Trekki Trip" NFT collection (vendor-hosted case page)

Stated results (vendor-provided):

A large user base, several thousand NFTs minted, and a notable amount of cryptocurrency raised.
Clique was used to evaluate social account quality and engagement signals for eligibility decisions.

Critical evaluation:

Results are not independently audited in public sources.
Campaign outcomes that depend on social signals require careful attention to gaming risks; resilience depends on the specific detection rules and configurations used.

3) Other ecosystem examples in documentation

04Best fit

Company sizes

Mid-market to enterprise Web3 organizations and well-funded protocols (e.g., teams ranging from small to large sizes with significant token treasuries or marketing budgets).
Brands running sizable NFT or loyalty activations with measurable growth targets.

Industries / verticals

Web3: L2 ecosystems, DeFi, gaming, consumer dApps.
Potential non-crypto verticals where private API calls plus verifiable proof are required, though prominent public examples remain crypto-native.

Roles and personas

Decision makers: Head of Ecosystem, Growth Lead, Protocol Engineering Lead, Security/Infrastructure Lead.
End users: smart contract engineers, backend engineers implementing campaign logic, data engineers defining eligibility rules.

Qualification criteria (good fit)

Organizations that require verifiable off-chain computation feeding on-chain logic.
Use cases that require protection of secrets or credentials (API keys, OAuth tokens) during off-chain data access.
Programs that operate at scale for incentive distribution and require tooling to mitigate Sybil attacks.

05The pitch

What the product does (objective summary)

Key product areas visible in public materials:

TEE Network / “off-chain AWS Lambda”: Executes workloads inside TEEs (documentation emphasizes Intel SGX and references plans to support AMD SEV-SNP, Intel TDX, and NVIDIA H100) and returns verifiable results that smart contracts can consume.
TLS Oracle / Arbitrary TLS calls: Enables API/TLS calls from within a TEE to retrieve off-chain data while keeping credentials inside the enclave and producing attestations of the operation.
Attestations / data attestation tasks: Framework for producing verifiable on-chain attestations about off-chain facts (for example, activity or reputation signals).
Clique Wallet (custodial, TEE-controlled keys): Describes a wallet architecture in which keys are generated, stored, and used inside a TEE.

Target market & positioning

Public materials and examples indicate a focus on:

Web3 ecosystems (L2s, DeFi, games, NFT campaigns) that require Sybil resistance, incentive distribution, and proof of off-chain behavior.
Protocols and brands running large-scale campaigns, airdrops, or loyalty/incentive programs.
Enterprise Web3 teams that require verifiable off-chain computation and confidential data access (for example, protecting API keys, OAuth tokens, or private model inputs).

Get a comprehensive analysis of Clique including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →