nexart.io

    Confidential Execution · protocolVersion 1.3.1

    Prove AI execution without exposing the data.

    Confidential execution is first-class in NexArt. It is enforced inside the certified record itself, not bolted on at the storage layer.

    • Execution records are sealed and verifiable
    • Sensitive input and output never need to be shared
    • Verification works independently of NexArt
    Run the confidential demoVerify a record independently

    Protocol-native

    Confidential execution is built into the record, not bolted on

    Confidential mode is not redaction after the fact. It is built into how the record is created, sealed, and verified.

    The record contains

    • Cryptographic commitments
    • Hashes
    • Structured execution metadata

    The record does not require

    • Raw prompts
    • Raw outputs
    • Sensitive customer data

    Confidential execution is enforced inside the certified record itself, not at the storage layer.

    Verifiable claims

    What you can prove

    • The execution happened.
    • The record has not been altered.
    • The output is fixed and bound to the record.
    • The record can be verified independently.
    • The certification can be checked without accessing raw data.

    Stays in your environment

    What you do not need to share

    Certification proceeds without any of the following leaving your system.

    • Raw prompts
    • Raw outputs
    • Customer data
    • Internal context
    • Regulated information

    Architecture

    Where execution, sealing, and attestation actually happen

    01

    Execution in your system

    The AI call runs inside your environment. Inputs, outputs, and parameters are transmitted over TLS only for node-side sealing, processed transiently, and excluded from the permanent confidential proof record.

    02

    Sealing can happen locally

    Commitments and hashes are produced inside the SDK. The record is sealed before anything crosses the boundary.

    03

    Node attestation is optional

    An attestation node signs the commitments and metadata. It does not need raw data to do so.

    You are not trusting NexArt with your data. You are using NexArt to make execution verifiable.

    Verification does not require NexArt. Anyone can recompute the hash and check the signature with the public key.

    Demo · protocolVersion 1.3.1

    Try a confidential execution end to end

    The demo runs in confidential mode by default. Raw input and output are never required for certification.

    Open the demo

    The strongest answer is no longer "trust us".

    It is "verify the record".

    Try confidential certificationWhat a CER contains