Sandbox demo — every provider, payment, clinical, education, device and delivery action is simulated. No real credentials or integrations.

Product portfolio

One platform. The modules your enterprise actually needs.

Explore governance, agent security, evidence, DevTrust and integrations. Each module shows its current catalog status, and none is approved to run for customers yet — product availability is kept separate from commercial eligibility.

One customer experience, separate authorities

  1. Agent

    Coordinates the work and proposes actions.

  2. Proofence Engine

    Verifies evidence and security truth.

  3. AtlasProof

    Governs: policy, review, approval and audit.

  4. Proofence Gate

    Controls execution where separately authorized.

Approval is not execution authorization: recording a decision never runs the action.

Nine modules, one governed platform

Start with governance and add specialised modules when their prerequisites are accepted.

AtlasProof Governance

Catalog foundation · not live

Who approved this AI-assisted business decision?

Keep policies, accountable approvals, roles and governance decisions visible in one place.

  • Policy and decision lineage
  • Actor and authority context
  • Review and audit workflows
AtlasProof:
Governs: policy, review, approval and audit lineage
Proofence Engine:
Verifies: evidence and security truth

Defined in the AtlasProof product catalog. Not running for customers; runtime readiness is not approved.

Agent Security

Dependency gated · not live

Which agent did what, under whose authority?

Understand registered agents, investigate incidents and route sensitive agent activity to review.

  • Agent inventory and risk workflows
  • Investigations with evidence references
  • Controlled escalation
AtlasProof:
Governs: enterprise workflows and review
Proofence Engine:
Verifies: agent security truth

Waits on an accepted Proofence contract. AtlasProof will not recreate that verification or security truth.

Verified Capture

Dependency gated · not live

Can the source of a document or capture be trusted?

Turn source capture events into reviewable enterprise evidence workflows.

  • Capture intake and review
  • Provenance view
  • Evidence chain references
AtlasProof:
Governs: intake, review and decision record
Proofence Engine:
Verifies: capture roots and provenance

Waits on an accepted Proofence contract. AtlasProof will not recreate that verification or security truth.

DevTrust

Catalog foundation · not live

Can an AI-authored change move safely through review?

Help engineering teams govern code changes, dependencies and release decisions.

  • Repository and pull-request governance
  • Supply-chain evidence view
  • Release review orchestration
AtlasProof:
Governs: review operations and release decisions
Proofence Engine:
Verifies: code and supply-chain evidence

Defined in the AtlasProof product catalog. Not running for customers; runtime readiness is not approved.

LLM & Model Governance

Catalog foundation · not live

Which models may process which business information?

Organize model usage, provider choices, evaluation references and review obligations.

  • Model and provider policy binding
  • Usage and token visibility
  • Evaluation evidence references
AtlasProof:
Governs: policy, review, approval and audit lineage
Proofence Engine:
Verifies: evidence and security truth

Defined in the AtlasProof product catalog. Not running for customers; runtime readiness is not approved.

Evidence & Audit

Catalog foundation · not live

How will an auditor reconstruct the decision?

Trace policy, action and evidence references for accountable AI operations.

  • Reviewable evidence timelines
  • Decision provenance
  • Export readiness
AtlasProof:
Governs: audit history and evidence references
Proofence Engine:
Verifies: evidence roots and signatures

Defined in the AtlasProof product catalog. Not running for customers; runtime readiness is not approved.

Device & Physical AI Trust

Dependency gated · not live

How do we constrain AI actions across devices?

Bring hardware, device and cyber-physical AI workflows into governed review.

  • Device governance workflows
  • Authority and lease visibility
  • Incident review
AtlasProof:
Governs: device review workflows
Proofence Engine:
Verifies: device attestation
Proofence Gate:
Controls execution where accepted

Waits on an accepted Proofence contract. AtlasProof will not recreate that verification or security truth.

Enterprise Integrations

Availability not established

How do governance decisions fit daily workflows?

Connect governed work to business systems through explicitly approved adapters.

  • Versioned API contracts
  • Connector governance
  • Enterprise onboarding
AtlasProof:
Governs: which decisions reach which system
Customer systems:
Consume decisions; nothing runs from approval alone

No canonical product record establishes this module's readiness. Talk to us about scope and feasibility.

Private Deployment

Planned · not live

How can operating data stay within our boundaries?

Explore dedicated or on-premises deployment for regulated environments.

  • Private environment proposals
  • Data residency planning
  • Enterprise SLA discovery
AtlasProof:
Governs: policy, review, approval and audit lineage
Proofence Engine:
Verifies: in your environment, when deployed

Planned in the AtlasProof product catalog. Not running for customers; talk to us about scope.

A module's place in this portfolio does not imply an accepted Proofence contract, an active entitlement or a purchase. Runtime readiness is not approved for any module, billing is not configured, and no page here activates anything.

How to read a module’s readiness

Catalog foundation · not live
Defined in the AtlasProof product catalog. Not running for customers; runtime readiness is not approved.
Planned · not live
Planned in the AtlasProof product catalog. Not running for customers; talk to us about scope.
Dependency gated · not live
Waits on an accepted Proofence contract. AtlasProof will not recreate that verification or security truth.
Availability not established
No canonical product record establishes this module's readiness. Talk to us about scope and feasibility.

Source: the AtlasProof product taxonomy atlasproof.feature-catalog.v1 — reconciled metadata, not an entitlement. Readiness is shown as recorded there; a card never upgrades it.

Start with one governed workflow.

Tell us which decisions need accountable review. We scope a pilot around accepted capabilities only.