Atestan Atestan

Connect the proof layer to the systems around it

Atestan is designed around its own components rather than around replacing the communication infrastructure an organisation already runs. The integration surface is that: an API, a verification experience, a registry, an anchoring layer, and the published policy.

01

Integrations

  1. The API

    The programmatic boundary for systems that need to issue or examine evidence — so a critical-request workflow can carry proof without being redesigned around a new communication system. Built and tested; it runs publicly and is not open to a client.

  2. The verification experience

    How a recipient examines the evidence attached to a request. It is deliberately evidence-oriented: it shows what can be established rather than asserting that a request is valid. The page is deployed at its permanent address and reaches its service; with no seal issued, it says that no seal matches a code.

  3. The registry

    The record layer the later levels need. Its core is built and tested and a service runs it publicly, with no organisation enrolled; no production registry is anchored.

  4. Anchoring

    What would let evidence be reconstructed later without trusting either party. It belongs to level E and is not implied by a request having been sealed. Specified, not built.

  5. Published policy

    The published policy is part of the integration model too, and it separates two things cleanly: the request says what is being asked; the published policy says what the organisation commits to sealing. A recipient can consult it without the request in hand.

02

Where Atestan sits

Above the mailbox you already have. We are not an email provider, and we never will be.

Built and tested — not open to a client yet

  • A request sealed by an organisation that enrolled — question one.
  • A seal that names who it was for, so it cannot be replayed elsewhere — question two.
  • The verification above, on scripted cases you can run yourself.

Planned

  • Microsoft 365
  • Google Workspace
  • ERP and accounting systems
  • An API for issuing and verifying
  • Mail gateway

These integrations are part of the planned Atestan architecture. They are NOT currently available, and nothing on this page connects to them.

No replacement claim

Atestan belongs beside critical workflows as an evidence layer. It is not a replacement for ordinary email-security controls, identity systems, financial controls or approval workflows — and it is not described as an integration with any product until that integration has been built and documented.