Sigillum Finans
TRContact us
Sigillum/Architecture

Architecture

Recording and verification within your institution

Institution-hosted trace collection, application-layer sealing, Kafka delivery and ClickHouse storage.

01 / Data flow

Application → sealing → Kafka → ClickHouse

SDKs capture supported service activity and carry the actual transaction context. Sigillum assembles related steps, evaluates completion and signs the transaction package at the application layer.

The sealed package passes through Kafka and is written to ClickHouse in batches. Transaction metadata and related steps are retained together for review.

HOW IT WORKS

Institutional data flow

Each layer has a defined responsibility, from collecting the trace to reviewing sealed evidence.

THE INSTITUTION’S SERVERS AND NETWORK
  1. 01
    .NET · Java · Python

    Institution applications

    Actual transaction context and related service steps

  2. 02
    Assembly and sealing

    Application layer

    Evaluates transaction completion and signs the package.

  3. 03
    Durable transport

    Apache Kafka

    Delivers sealed packages to the batch writer.

  4. 04
    Compressed transaction record

    ClickHouse

    Stores transactions and steps together for retrieval.

Review and verification run through the institution portal. Users, environments and service definitions belong to the control plane.

Technical guide

02 / Verification

Verifiable integrity

Recorded content and chain signatures are checked before presenting evidence. Institution-record comparison and offline verification answer different review questions.

A valid signature establishes integrity under the verification trust basis; it does not independently establish the truth of the business decision.

HOW IT WORKS

Record and verification lifecycle

Business outcome, record integrity and institution-record comparison answer distinct questions.

THE INSTITUTION’S SERVERS AND NETWORK
  1. 01
    Actual transaction steps

    Related trace

    Record origin and service call context are retained.

  2. 02
    Chain and signature

    Sealed record

    The integrity of the stored package can be checked again.

  3. 03
    Institution business record

    Comparison

    Inspect matches and differences across configured fields.

  4. 04
    Portable evidence

    Offline verification

    Check the evidence package using verification keys.

03 / Control and storage

Separate responsibilities

Institution, user, environment, application and service definitions belong to the control plane, which uses PostgreSQL in the current installation. Sealed transaction contents belong in ClickHouse.

The active window and archival storage are operational choices. Legal retention, access and deletion requirements are determined separately for the institution.

PRODUCT INFORMATION

Frequently asked questions

Where is the product installed?

Inside the institution’s own network and infrastructure. Required internal addresses, certificates and credentials are managed by the institution.

DISCUSS YOUR REQUIREMENTS

Plan an evaluation for your institution.

Bring your workflow, integration requirements and review questions. We’ll discuss how Sigillum Finans fits your environment.

Talk to our team