skip to content
vortx.ai

Check an answer, don't just believe it.

  • verifya fact yourself: recompute its blake3, check its ed25519 signature, offline
  • carrythe proof with the fact, so nobody has to trust the provider
  • bounda private tenancy by a line enforced in the code, on every read and write

Check one fact, here, now.

  • fetchCubbon Park's NDVI as canonical CBOR: GET https://emem.dev/v1/facts/eheadieomxr2zusg…
  • hashthe bytes with blake3: you get eheadieomxr2zusg…, its own name, because the address is the content
  • verifythe receipt's ed25519 signature against emem's key 777er3yi…, offline, at emem.dev/verify; nothing calls back to us
  • watchevery one of those checks run in your browser: the proof page

The tenancy line, in the code.

  • enforcegeo.qa's boundary per organisation, in the query layer, on every read and every write: not a setting, not a clause
  • combinea public emem reading with one of your private ones under one receipt, without your data leaving your tenancy

What we claim, and what we don't.

  • claimsigned facts, content addresses, a witnessed log and a boundary enforced in code: each one checkable by you
  • skipcertifications we don't hold; none is listed here until it is real
  • sharedetail for a procurement or security review under NDA, and walk your team through the rest

ask for a security review