Platform Architecture

Sigigo is evidence infrastructure for software, AI agents, and enterprise workflows. We ingest structured audit events at decision boundaries, store them immutably, cryptographically sign them, batch them into Merkle trees, and export self-contained evidence packs for independent offline verification. Optional public anchoring when tenant policy allows.

End-to-End Pipeline

1. Ingestion

Client submits events to our high-throughput HTTP API.

2. Immutable Storage

Raw and deterministic canonical payloads are stored securely.

3. Cryptographic Hashing

SHA-256 digests are computed and signed with secure keys.

4. Merkle Batching

Events are grouped into Merkle trees, generating per-event proofs.

5. Optional Anchoring

Batch Merkle roots may anchor to public blockchains when policy allows — off by default for EU profiles.

6. Evidence Pack Export

Self-contained bundles with events, proofs, and VERIFY.md for offline auditor verification.

Event Lifecycle

Received

Event accepted, canonical payload stored, hash job enqueued.

Hashed

Digest computed and signed with secure key.

Batched

Included in a Merkle batch with per-event proof generated.

Anchored

Batch Merkle root optionally submitted to blockchain (tenant policy).

Exported

Evidence pack available for offline verification.

Core Technology Stack

Our platform leverages enterprise-grade cloud-native infrastructure for scalability and resilience.

  • API Layer: High-performance Fastify endpoints.
  • Messaging: Apache Pulsar for reliable, decoupled event processing.
  • Worker Services: Modular worker architecture for handling asynchronous hashing, batching, and anchoring workflows.
  • Data Storage: Immutable object storage and fast NoSQL indexing for event metadata.

Engineering Principles

Sigigo is built on a Hexagonal Architecture, ensuring separation of concerns and robust domain logic.

  • Hexagonal Architecture: Domain services are isolated from infrastructure adapters.
  • Deterministic Output: JSON canonicalization ensures verifiable hashes regardless of input order.
  • Security First: Strict separation between ingestion and asynchronous processing.
  • Independent Verification: Proof artifacts are stored openly to eliminate vendor lock-in for auditing.