sigill.aiDocs
Log inGet started
Home
Integrations
API reference
SDKs
Apps
GitHubGoogle Drive
AI agents (plugin, SDKs, MCP)Browser extension
Architecture
How sigill.ai worksThe verification model
Use cases
Seal a PDF without uploading itSeal AI and agent logs with JAdESCreate detached evidence with CAdESTimestamp builds and releases in CIQualified timestamps for legal-grade evidenceSeal under your own name (BYOC)Route timestamps through your own TSA (BYOT)Prove priority: IP, research, and designsLet AI agents seal their own work (MCP, plugin + SDKs)Capture AI conversations as evidenceEvidence that outlives the infrastructureVerify a seal without a Sigill account
Concepts
Choosing a seal format: PAdES, CAdES, or JAdES
Trust center
OverviewSecurity architectureSub-processorsStandardsVerification modelCompliance postureResponsible disclosure
More
FAQVerify a file↗Blog & tutorials↗

Apps

Connect the tools you already use. Configuration lives in the app; Sigill only records which organisation it belongs to — owners connect apps under Settings → Apps.

GitHub
GitHub Actions · GitHub App

Add timestamps — qualified (eIDAS) if you choose — and advanced electronic seals to what your workflows build, with no Sigill keys or secrets in GitHub. Seal release assets with your organisation's own certificate (recommended) or the Sigill Platform Seal, optionally post-quantum hybrid; every piece of evidence is linked to the verified repository, commit and run.

Set up GitHub →
Google Drive
Google Workspace add-on

Add timestamps — qualified (eIDAS) if you choose — and advanced electronic seals to Drive files from the side panel; your files never leave Google. Seals use the Sigill Platform Seal by default, or your organisation's own certificate (recommended). Select a sealed file to see whether it is still the version that was sealed.

Set up Google Drive →

Privacy: GitHub App privacy policy · Google Drive add-on privacy policy · main privacy policy · terms