Heka Global

• Organizations that cannot accept public web intelligence on governance grounds
• Workflows requiring strict US-only data residency (unless Heka offers US hosting not visible in public sources)
• Very small teams needing self-serve pricing and lightweight onboarding

• Heka states it processes publicly available data and does not access login-gated sources—this inherently limits coverage for individuals with low public footprints.

No detailed public roadmap with dates was found.

No public performance or throughput benchmarks were found.

• SOC 2 status is described as "aligned" in public materials, which may not meet procurement requirements unless reports are available under NDA.
• Public documentation does not clearly list enterprise features such as SSO/SAML/SCIM/audit logs.

• Pensions tracing focus with partner validation: Partnerships and industry coverage (ZEDRA, Dalriada; professional publications) indicate adoption in the UK pensions tracing niche.
• Source-linked outputs: The vendor emphasizes outputs that include links to supporting web sources, which can be relevant in audit-heavy contexts.

• Broad global coverage claims (50+ countries; 3,000+ sources) require buyer testing for specific target geographies.
• Vendor-reported customer metrics (e.g., percent reductions in losses) are published without disclosed methodology.

• Larger incumbents may have deeper proprietary data assets, consortium intelligence, and longer operating histories.
• More mature platforms may offer more turnkey orchestration, dashboards, and rule-building tooling.

Heka’s homepage contains curated testimonials attributed to partners such as ZEDRA and Dalriada. These statements emphasize improved tracing outcomes in pensions-related workflows.

Caveat: These are vendor-curated testimonials; treat them as directional and not independently validated without reference checks.

• Searches for "Heka Global" on Reddit largely return unrelated posts due to the broad use of the term "Heka"; there is no meaningful, attributable Reddit review corpus for Heka Global specifically.
• No relevant Hacker News thread about Heka Global was found in the searches performed.

Based on partner announcements and pensions-focused writeups, customers appear to use Heka for:

• Tracing beyond traditional databases when contact data is stale
• Access to outputs that include source links to support auditability
• Ability to identify deceased members and next-of-kin indicators in pension workflows

Because public review coverage is sparse, churn reasons are not well documented. Plausible risk factors (to validate in reference calls):

• Data coverage variability by country and demographic
• False positives creating manual review load
• Procurement/security friction for web-intelligence approaches
• Cost versus traditional tracing vendors if uplift is inconsistent

• Heka announced a partnership with ZEDRA Governance following a pilot where Heka’s tracing identified a substantial portion of previously unreachable members.

Critical evaluation:

• The reported figure appears in partnership announcement materials. The methodology, sample size, definition of "unreachable," and validation approach are not disclosed. Treat as vendor-reported and not independently validated.

• Reports indicate Dalriada Trustees partnered with Heka to locate previously untraceable fraud victims, noting that poor member records had prevented tracing by traditional methods.

Critical evaluation:

• This is supported by partner and industry publication mentions but lacks detailed methodology (match confidence thresholds, accuracy validation, time-to-trace).

Most plausible ICP based on product and compliance posture:

• Mid-market to enterprise financial organizations (mid-to-large enterprise scale)
• Smaller fintechs with high fraud exposure and strong compliance needs

• Pensions and trusteeship / pension administrators
• Banks and payment processors
• Insurance underwriting

Decision makers:

• Head of Fraud / Fraud Strategy
• Head of Financial Crime / Risk
• Head of Operations (pensions administration)
• Compliance / Data Protection Officer
• CISO / Vendor Risk Management

End users:

• Fraud analysts / investigators
• KYC operations teams
• Pensions member-tracing teams

• High cost and low yield of traditional tracing
• Thin or stale customer records
• Synthetic identity / manipulated identity signals not visible in internal data
• Regulatory need for decisions supported by traceable evidence

Heka is aimed at regulated financial services and adjacent regulated workflows, including:

• Banks, payment processors, fintechs
• Insurers
• Pension funds / trustees / administrators

Positioning: Heka markets the product to financial services organizations and describes outputs as structured to support audit processes and regulatory review, with emphasis on traceability and explainability.