XPScerpto

XPScerpto

Language and region

All languages

XPScerpto

Evidence-Bound Cryptographic Infrastructure

Execute FHE, PQC and governed cryptographic workloads through a controlled runtime that binds source, build, evidence and replay.

XPScerpto is the execution and assurance fabric between cryptographic code and a verifiable claim. Runtime domains, provider boundaries, evidence custody and replay remain explicit — and the public UI never invents a verdict.

Explore the platformSee the architectureOpen platform↗
SOURCEBUILDRUNTIMEEVIDENCEREPLAY
XPScerpto platform workspacePUBLIC MODEL · NO RUNTIME CLAIM
XPScerpto / WorkspacePUBLIC MODEL
PROJECT SCOPECryptographic Runtime Project
CONTROLLED BOUNDARY
SOURCE—
→
BUILD—
→
RUNTIMENOT_RUN
GOVERNED REQUESTPQC sandbox
PENDING
OPERATIONml_kem_sandbox
PQCPost-quantumAVAILABLE SURFACE
FHEFHE / CKKSAVAILABLE SURFACE
INTIntegrityAVAILABLE SURFACE
SIMDVector pathAVAILABLE SURFACE
HWHardwareAVAILABLE SURFACE
V64VeloSeal64AVAILABLE SURFACE
EVIDENCE CUSTODYExecution result
NO CLAIM
Request ID
—
Capsule ID
—
HSMD receipt
—
Replay
PENDING_REQUEST
Verification
NOT_RUN

Execution continuum

From exact source to a claim that can be independently checked.

Identity, runtime custody, cryptographic execution, evidence and replay are separate stages connected by one governed path.
  1. 01
    Source identityExact source admission
  2. 02
    Build identityReproducible build binding
  3. 03
    Controlled runtimeProvider & authority context
  4. 04
    Crypto executionFHE · PQC · SIMD · Integrity · HW
  5. 05
    Evidence custodyStructured bound result
  6. 06
    ReplayFreshness & reproducibility
  7. 07
    Claim verificationNo claim without evidence

Platform capabilities

Platform capabilities

Cryptographic execution, controlled runtime and reviewable evidence inside explicit authority boundaries.
01

FHE / CKKS

Encrypted-compute paths bound to execution identity and evidence.

02

PQC & crypto-agility

Post-quantum migration bound to implementation, parameters and runtime context.

03

Controlled runtime

Provider, policy and hardware boundaries precede every runtime claim.

04

Evidence & replay

Structured evidence, freshness and reproducible independent verification.

05

HSM / HSMD

Hardware trust admission through explicit provider and authority boundaries.

06

Integrity fabric

Integrity verification attached to evidence-bearing runtime paths.

07

SIMD & VeloSeal64

Execution domains remain inside explicit runtime custody.

08

APIs & workspaces

Scoped product surfaces without moving sovereign decision power into the UI.

Operational planes

One platform. Explicit authority boundaries.

Public presentation, scoped workspaces, administration and root/hardware authority remain separate surfaces with different permissions.
01

PUBLIC

Product, architecture and admitted public evidence

↗02

APP / COMPANY

Projects, governed requests and scoped evidence

↗03

ADMIN

Content, correspondence and operator controls

↗04

ROOT / HARDWARE

Local or hardware-gated authority

↗

Assurance fabric

Evidence before acceptance.

The UI can render state and admitted evidence. It cannot manufacture source identity, runtime truth, replay success or a final verdict.
XPScerpto verification chainTruth remains bound to the execution that produced it.
UI ≠ VERDICT
  1. 01SOURCEBOUND STAGE
  2. 02BUILDBOUND STAGE
  3. 03AUTHORITYBOUND STAGE
  4. 04RUNTIMEBOUND STAGE
  5. 05EVIDENCEBOUND STAGE
  6. 06TEMPORALBOUND STAGE
  7. 07REPLAYBOUND STAGE
  8. 08CLAIMBOUND STAGE
PUBLIC ADAPTER BOUNDARYFINAL VERDICT AUTHORITY IS NOT GRANTED TO THIS PAGE
XPScerpto

XPScerpto

See XPScerpto as an execution system — not a security brochure.

Explore the architecture, cryptographic domains and evidence model, or enter the authenticated workspace.