Trust

Processing verification and delivery trust built into the platform

Signed processing receipts, node certification, jurisdiction controls, and delivery verification — not afterthoughts.

Every inference request generates a cryptographically signed receipt — proof that work was done correctly.

Processing nodes are verified by hardware capability. Ed25519 signatures authenticate every node interaction.

Route inference to nodes in specific countries. Data sovereignty built into the API.

Request history, node assignments, costs, and receipts — all inspectable from the dashboard.

Security model

Explicit about scope and limits

Public and certified processing separated. Policy and delivery always visible.

In scope

Signed receipts for every completed processing stage.

Policy-aware routing across public and certified processing pools.

Signed webhook delivery when enabled.

Buyer-visible output storage status.

Intentionally constrained

Public processing does not include certified-tier guarantees by default.

Certified processing depends on node trust level, policy compliance, and hardware capability.

Certification

Node capability and trust level — not just online/offline.

Open

Typical use: Standard spatial processing with default delivery and billing.

Evidence posture: Node eligibility visible. Standard verification — not certified-tier trust.

Review

Typical use: Nodes under evaluation for certified processing eligibility.

Evidence posture: Hardware and compliance signals under review before advancement.

Certified

Typical use: High-trust workloads with explicit jurisdiction and compliance requirements.

Evidence posture: Country, trust level, and certification status are real scheduling inputs.

Tier	Typical use	Evidence posture
Open	Standard spatial processing with default delivery and billing.	Node eligibility visible. Standard verification — not certified-tier trust.
Review	Nodes under evaluation for certified processing eligibility.	Hardware and compliance signals under review before advancement.
Certified	High-trust workloads with explicit jurisdiction and compliance requirements.	Country, trust level, and certification status are real scheduling inputs.

Operations

Processing health, output storage, and delivery visible by default.

Runtime health

Public health and readiness endpoints.

Storage and delivery

Output artifacts, processing logs, and delivery callbacks are explicit.

Operational reference