Datumo

• Requirement for publicly available SOC 2 or ISO 27001 documentation prior to procurement.
• Requirement for transparent self-serve pricing or a preference for an open-source stack.
• Need for extensive out-of-the-box integrations with specific ecosystems that Datumo does not support.

• Pricing transparency: no published tiers for Datumo Eval were found.
• Security and compliance transparency: no public SOC 2/ISO documentation was located in accessible sources.
• Limited mainstream review footprint: few reviews on major B2B platforms were found publicly.
• Brand and entity confusion: multiple online entities using the Datumo name create potential for diligence and contracting confusion.

Marketing and investor commentary indicate continued R&D in automated evaluation and global expansion, but there is no detailed public roadmap with dates available in the sources reviewed.

• An evaluation workflow that covers dataset generation, scoring, dashboards, and red-teaming (as described in documentation).
• Documented client adoption in South Korea according to press reports and investor commentary.
• A positioning that emphasizes evaluation and safety testing workflows rather than solely prompt experimentation.

• "First" or similar priority claims are difficult to verify independently and should be validated against patent databases and academic literature if relevant.
• Benchmark or methodology claims should be compared to other published evaluation frameworks and verified where possible.

Datumo’s LinkedIn activity shows conference and event participation (for example, industry conferences and exhibition programs) and indicates the company is using Datumo as the global brand for the SelectStar lineage.

Some testimonial-style comments appear on third-party directory or partner sites; these are typically about services engagements rather than verified SaaS user reviews of Datumo Eval. For example, a partner directory includes a statement attributed to a data engineering lead praising Datumo engineers’ ownership and technical skills; this appears to concern services and professional engagement.

Press and investor material describe a customer demand path from data labeling to requests for scoring and comparing AI outputs, which contributed to the creation of a packaged evaluation platform. Press reports cite adoption among large enterprises in Korea and present Datumo as targeting organizations that want to formalize evaluation workflows without heavy engineering effort.

There is insufficient publicly accessible negative end-user review content specifically about Datumo Eval on major review platforms. An independent teardown or blog post made assertions about limited review presence and questioned pricing and partnerships; however, some statements in that post conflict with reporting from a major tech publication and should be treated as speculative unless corroborated.

Press reporting has cited reported revenue figures and client counts in a specific regional market. These numbers are journalistic reporting and have not been audited in this research.

Based on press references to enterprise clients and broader funding context, Datumo appears to target mid-market to enterprise organizations, with deployments large enough to justify formal evaluation pipelines and governance.

Datumo’s materials and press references indicate vertical activity in e-commerce, finance, education, legal, healthcare, and customer service. Press mentions include major enterprises and banks in Korea.

• Product owners for LLM applications (chatbots, RAG, agents)
• ML/AI platform teams
• Trust & Safety, Policy, and Compliance stakeholders
• QA and reliability engineering functions for AI products

• Need for repeatable evaluation and safety testing rather than ad hoc prompt trials.
• Requirement for generating domain-specific evaluation datasets quickly.
• Interest in a vendor with documented adoption in Korea and wider Asia enterprise environments.

Datumo Eval is presented to teams that need to systematically evaluate LLM-based products (chatbots, RAG applications, agent workflows, customer service LLMs, etc.), including non-engineering stakeholders (policy, compliance, trust & safety) in a no-code context referenced in press coverage.