OpenSignature¶

OpenSignature is an independent .NET digital-signature platform for enterprise PAdES, XAdES, CAdES, and ASiC workflows. Clients submit documents over REST; workers sign asynchronously. PostgreSQL stores metadata; file storage holds binaries; RabbitMQ carries job references only.

OpenSignature system architecture

System overview — API, storage, queue, worker, and signing providers.

Why this architecture¶

Principle	Practice
Non-blocking API	Validate → store → outbox → `202 Accepted`. No crypto in the API process.
Safe transport	RabbitMQ messages are small JSON job refs — never document binaries.
Key hygiene	Hardware providers sign digests on-device; private keys are never exported.
Tenant isolation	Storage keys, idempotency, and queries are scoped by `TenantId`.
Observable	Correlation / trace / signature / job IDs on every hop.

Quick links¶

Getting started — local Docker, API, worker, UI
Architecture — components and dependency rules
Flows & diagrams — sequence and state diagrams
REST API — endpoints and error codes
Product specification — engineering source of truth

Async signing at a glance¶

Async signing flow

flowchart LR
  C[Client] -->|POST /signatures| A[Api]
  A -->|input.bin + metadata| S[(Storage + PostgreSQL)]
  A -->|Outbox| Q[[RabbitMQ]]
  Q --> W[Worker]
  W -->|SignDigest| P[ISigningProvider]
  W -->|signed.bin| S
  C -->|GET status / content| A

Language¶

This site is available in English and Türkçe (language switcher in the header). Source code, identifiers, logs, tests, and commit messages remain English-only.

License¶

OpenSignature is licensed under the MIT License.