About
Resolution you can just turn on.
Real fragment-to-entity resolution has always been gated: the tools with their own data put you through weeks of credentialing, and the self-serve ones have no data. Ahel is the one box that is both — own-data identity resolution you turn on yourself in minutes, over REST and MCP, priced per call. Built in Estonia, and on the record: the fact panel below is the same primary registry entry Ahel would return for any company you asked about, only this one is ours.
The company
All of the above is filed with the Estonian Centre of Registers and Information Systems and is public. Ahel Technologies OÜ is a solo venture, incorporated in Tallinn and operated from Estonia.
The engine: Arkenstone
Every resolve, find, connect, and verify that Ahel runs is powered by Arkenstone — our in-house entity-resolution engine. Arkenstone takes a single identifier — a name, a domain, a company number, a wallet address — and returns one resolved entity, every field carrying the source it came from. Under the hood it reads live registries, the GLEIF legal-entity index, sanctions and PEP lists, and the open web, then folds what comes back onto an entity-resolution graph so one subject comes out the other side rather than a pile of half-matched records.
The distinction Arkenstone is built around is the one most tools skip: it keeps is this datum correct separate from is this datum about the subject you asked for. A perfectly accurate record about the wrong namesake is still the wrong answer, and the graph is what stops it from being promoted. Every field that reaches you carries the source it came from, so the reasoning is auditable end to end.
Arkenstone is the engine; Ahel is how you use it — an API you turn on yourself, an MCP server your agent calls directly, or the Composer. No application, no credentialing gauntlet. See the products for the surfaces, and the methodology for how confidence is scored.
How we handle trust
We host in the European Union, encrypt the credentials you connect, and name every subprocessor we rely on. The full picture — hosting, encryption, subprocessors, and GDPR posture — is on the security page. For anything else, write to [email protected].