Cometh

Name: Cometh
Brand: Cometh

AI Native

The DeFi Infrastructure for Businesses

Est 2021

LinkedIn 3K|Web traffic 2K|FTEs 31|HQ Paris, Île-de-France, FR

Published Aug 26, 2026

01Common complaints

1) When only AA infrastructure with published pricing is required If the primary requirement is bundler + paymaster + SDK with published pricing, organizations may prefer vendors that provide clear self-serve pricing and an established AA-focused offering. 2) When procurement requires formal certifications up front Cometh provides regulatory filings, but public SOC 2/ISO certifications were not identified in the materials reviewed. Organizations that require such certifications prior to onboarding should request documentation or consider alternative vendors. 3) When comprehensive third-party review coverage is required for benchmarking Mainstream B2B review coverage for Cometh’s current offering appears limited. Organizations relying heavily on peer-review benchmarking may need to augment vendor evaluation with references and technical pilots. 4) When cross-chain risk tolerance is low Chain-abstraction and cross-chain modules introduce additional risk. Organizations with low tolerance for cross-chain failure modes may prefer single-chain or minimal-bridge architectures.

Deal disqualifiers (poor fit)

Requirement for publicly documented SOC 2/ISO certifications prior to any proof-of-concept.
Requirement for fully transparent self-serve pricing and rapid procurement timelines.
Low tolerance for AA operational complexity (bundlers/paymasters/explorer visibility), or lack of support staffing for such models.

Vendor-acknowledged limitations

Public documentation indicates that full public documentation for the DeFi-as-a-Service API layer is forthcoming; current public documentation is stronger for the Connect product than for the broader BaaS API.

Ecosystem and implementation limitations (not vendor-specific but relevant)

ERC-4337 implementations increase the attack surface (bundlers, paymasters, and additional smart-contract components) and require thorough threat modeling.
Compliance and audit-trail tooling for AA flows are debated in the security community; AA can complicate traceability versus externally owned accounts if not instrumented appropriately.
Explorer visibility issues for UserOp transactions are reported in developer forums and may increase support workload.

Technical caveats surfaced in open-source artifacts

A repository associated with the vendor documents edge cases for combining Safe and WebAuthn signers in certain UserOp initCode patterns; this can affect mobile implementations and requires platform-specific integration patterns.

02Why they buy

Observed differentiators

Regulatory registrations in France and a MiCA-related listing are differentiators compared with vendors that only provide AA tooling.
Integration with Safe smart accounts and support for WebAuthn/passkeys aim to improve the end-user onboarding experience relative to seed-phrase-based approaches.

Vendor-claimed propositions requiring buyer validation

A single API for custody, staking, swaps, and payments is asserted in vendor materials; buyers should validate the scope, SLAs, and contractual responsibilities for each service.
The vendor states that sponsored gas is billed without markup; buyers should request billing methodology and verifiable audit trails.

Areas where competitors may have an advantage

Self-serve developer adoption and published pricing are stronger with some AA-focused competitors.
Some organizations may prefer building directly on Safe primitives and integrating separate providers to reduce perceived vendor lock-in.

03Field reports

Review platforms (Gartner Peer Insights, G2, TrustRadius)

No authoritative product review pages for Cometh’s B2B DeFi infrastructure were located on mainstream review platforms during this research. Limited discoverable third-party review coverage was observed, which means vendor references and technical evaluation may carry greater weight during procurement.

Community/social feedback (Reddit, forums, HackerNews)

Community content is limited and sometimes conflated with legacy gaming activity. Notable community signals include: - Historical gaming/token community discussions referencing earlier Cometh Studio projects and token dynamics. - Ecosystem discussions about ERC-4337 and account abstraction challenges that are relevant to any vendor offering AA-based onboarding and sponsorship. - A community forum post authored by a company-affiliated contributor discussing multi-chain abstraction demos and challenges; this post documents practical issues such as diverging wallet states and passkey management across chains. Why customers reference Cometh in vendor material: - Regulatory posture in France and related regional regulatory filings combined with a bundled API for services. - Streamlined onboarding leveraging passkeys/WebAuthn and gas sponsorship to limit the need for native tokens during initial user interaction. - Cross-chain abstraction concepts intended to reduce complexity across multiple L2s. Potential reasons for non-adoption or churn inferred from available signals: - Cost control concerns related to sponsored gas and paymaster exposure. - Tooling and debugging complexity associated with ERC-4337 and smart accounts. - Compliance workload if audit trails and traceability are more complex in AA flows.

Vendor-presented customer examples (limited independent verification)

The vendor lists example customers with short descriptions of use cases. These vendor-published examples do not include detailed, independently verified metrics in publicly accessible materials. Critical evaluation and recommended buyer requests: - Obtain architecture diagrams that delineate custody and execution responsibilities. - Request operational metrics (monthly active wallets, transaction counts, volumes) and SLA performance data. - Request incident history and post-incident reports where applicable. - Request references willing to discuss production experiences and integration challenges.

Demonstration artifact: Cross-chain demo

The vendor hosts a cross-chain demo describing a primary Safe controlling secondary Safes across chains with messaging and module relays. Demos illustrate design approaches but are not equivalent to production readiness. Buyers should scrutinize bridge assumptions, message verification, and failure-handling patterns.

04Best fit

Likely best-fit segments (based on positioning and documentation)

Company size: Mid-market to enterprise buyers (companies in the mid-market to enterprise range) with compliance and security requirements.
Geography: EU/UK-facing products where regulatory posture in France and MiCA alignment are relevant.
Industries: Fintechs embedding crypto features; asset managers and treasury teams exploring stablecoin yield and on-chain settlement; consumer-facing apps seeking smoother onboarding via passkeys.

Buyer personas

Head of Product or General Manager for crypto initiatives
CTO or Head of Engineering (wallet and infrastructure responsibilities)
Compliance/Legal lead responsible for outsourcing and regulatory perimeter
Security engineering and risk management practitioners assessing AA threat models

Qualification criteria (strong fit)

Need for gas sponsorship and WebAuthn-based onboarding.
Requirement for a vendor with explicit EU regulatory filings and willingness to engage in enterprise procurement.
Preference for Safe-based smart accounts with an SDK-based approach versus building the full stack from scratch.

05The pitch

What the product does (core value proposition)

Cometh presents a set of developer-facing services that combine account abstraction (smart accounts) with regulated crypto services (custody, swaps/trading, staking/yield, and payments/settlement) accessible via an API and smart-account infrastructure. It provides an account-abstraction wallet layer (Cometh Connect) designed to reduce onboarding friction through passkeys/WebAuthn, gas sponsorship, and account recovery patterns.

Target market and positioning

Primary: Europe-focused fintechs, institutions, and corporates seeking to embed crypto/DeFi functionality while aligning with European regulatory expectations (MiCA-related language appears in documentation).
Secondary / legacy brand footprint: Historical ties to Web3 gaming and gaming tooling (Cometh Studio, MUST token, earlier activity in the Polygon gaming ecosystem). This legacy may create brand perception ambiguity relative to the current BaaS positioning.

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

Download full report →