Zomma builds computer-use agents for financial back-office work. The product operates existing portals, registries, PDFs, case managers and internal tools by reading and acting on the screen rather than requiring an API integration.12
Its current emphasis is compliance for payment companies: KYB/KYC screening, sanctions and PEP checks, adverse-media work, transaction-monitoring alerts, periodic reviews, reconciliations and disputes. Each workflow produces a reviewable case file with timestamped screenshots behind findings and a recommendation rather than an autonomous final determination.1
That screen-first approach is materially useful where legacy systems or third-party portals cannot be integrated conventionally. It also makes Zomma narrower than a general agent platform: the strongest evidence today is for finance/compliance operations, not arbitrary knowledge-work automation.
Pricing & access
Zomma publishes no list price. It states that pricing is a flat monthly fee per deployment, without a per-case meter, with the actual quote set after the workflow and case types are scoped.13
There is no verified public free tier. The site advertises a developer API and shows an agent attaching to a Zomma computer, but the public surface is still waitlist/limited rather than a broadly documented self-service API product.1
This model can be attractive for high-volume workflows because marginal case volume is not metered, but value cannot be verified without a proposal and a clear baseline for the labor or BPO cost being displaced.
Evidence & trust
Zomma documents several controls that matter for computer-use agents: single-tenant AWS deployment, encrypted storage, an isolated credential vault, human-cleared 2FA, logged human approval before external actions, configurable retention and model-provider terms described as zero-retention/no-training.41
Those are stronger public trust signals than many early agent products provide. However, SOC 2 Type 1 language is inconsistent: the homepage refers to a Type 1 audit, while the security page says the report will be shared when issued. AiToolMap therefore does not state that certification has been achieved.14
Y Combinator independently corroborates the company, team and product category. Its page repeats Zomma's claim of a 92% OSWorld result, but that figure is company-provided context rather than an independent product benchmark and is excluded from the rating.5
The fixed 50-source panel found no current exact-product professional review, independent benchmark or user-rating evidence. Two panel domains were inaccessible through the lawful retrieval path and were not bypassed. Rating confidence is therefore LOW.
Who it's for
Zomma is best suited to financial-services teams whose operations depend on portals, registries and internal software that do not expose useful APIs. Compliance teams are the clearest current fit because the product is built around evidence collection, procedural reasoning, analyst review and auditability.1
It is less suitable for buyers seeking a mature horizontal agent platform, transparent self-service pricing, a public developer ecosystem or a product with extensive third-party outcome evidence.
Strengths & weaknesses
Strengths
screen-level automation without migration, screenshot-backed evidence, explicit human approval, support for difficult finance/compliance workflows and relatively detailed public data-handling controls.142
Weaknesses
commercial opacity, early API access, limited independent validation and unresolved wording around formal compliance status. AiToolMap therefore scores task coverage and workflow fit strongly while keeping maturity, accessibility and confidence more conservative.