Sigill AS

About Sigill AS

Sigill.ai provides cryptographic evidence infrastructure for digital records, timestamps, seals, and verification workflows. We help teams prove that a specific file, record, release, or transaction existed at a specific point in time — and that it has not changed since. Sigill combines RFC 3161 timestamping, PAdES seals for PDFs, CAdES detached signatures for non-PDF files, tenant-scoped audit logs, and independent verification flows. Sigill is built as a trust hub, not as the trust anchor. Timestamp requests are relayed to independent Timestamp Authorities, and seals are bound to organisational certificates issued by external Certificate Authorities. Proofs returned by Sigill can be verified against the upstream authorities without Sigill being involved. The product is API-first and designed for regulated systems, AI workflows, document-heavy businesses, software supply chains, and compliance-sensitive platforms where “who did what, when, and to which data” must be independently provable. For timestamping and verification, only a cryptographic hash crosses the network; the file itself stays on the customer side. File sealing is the exception: the document bytes are processed in memory so PAdES or CAdES signatures can be produced, then streamed back without being retained as document storage. Sigill AS is based in Trondheim, Norway. The Sigill.ai data plane runs in AWS, with customer evidence records, signing keys, audit logs, and database backups hosted in the EU region. We avoid vague claims such as “tamper-proof documents”. Sigill provides narrow, verifiable evidence: proof of existence, proof of integrity, proof of origin, and auditable evidence trails anchored in external cryptographic trust services.