Server Edition
High-volume document signing automation
Folder Watch — Automatic signing
Drop files into department folders and XignAll signs them automatically. No API, no integration, no cloud.
- ✅ Department-isolated subfolders — Economic/, Legal/, HR/
- ✅ Auto-converts DOCX, XLSX, images to PDF before signing
- ✅ Signed files moved to Signed/ subfolder automatically
- ✅ No API, no cloud, no integration required
- ✅ Compatible with shared network drives and NAS
Signing can use the organizational SEAL or a qualified certificate from a hardware token. The latter is technically supported; however, a qualified certificate is personally bound to its holder. Whether delegated use is appropriate is the sole responsibility of the certificate owner.
# Folder structure
/SEAL/
├── Economic/
│ ├── invoice1.docx ← drop file here
│ ├── invoice1.pdf ← XignAll converts to PDF
│ └── Signed/
│ └── invoice1_signed.pdf
├── Legal/
│ └── Signed/
│ └── contract_signed.pdf
└── HR/
Telegram Bot — Remote Authorization
Telegram Bot — Remote authorization
Authorize signing sessions remotely via Telegram — no VPN, no web portal, no exposed APIs.
- ✅ Send DOCX, XLSX, PDF or phone photos — received signed in seconds
- ✅ Auto-converts any format (including JPG/PNG) to PDF before signing
- ✅ Whitelist-only — bot silently ignores unauthorized users
- ✅ No VPN, no web portal, no exposed API endpoints
- ✅ Works from anywhere with a Telegram connection
- ✅ Your bot token — fully under your infrastructure control
The bot signs using the organizational SEAL or a configured qualified certificate. Delegating a personal qualified certificate to a shared bot is technically supported; compliance with applicable regulations is the responsibility of the certificate holder.
Organizational SEAL
Automatically apply the organization's qualified electronic seal at the end of every signing workflow.
- ✅ eIDAS-compliant qualified electronic seal (eSEAL)
- ✅ Applied automatically after all individual signers complete
- ✅ PKCS#12 (.p12) or hardware PKCS#11 token
- ✅ PIN entered once — all documents sealed automatically
- ✅ Wrong-PIN protection prevents token lockout
- ✅ Any authorized network user can trigger SEAL — no individual certificate required
Signing workflow order:
- ① Signer 1 (individual certificate)
- ② Signer 2 (individual certificate)
- ③ Signer N (individual certificate)
- ④ Organizational SEAL ← applied last
An organizational SEAL (eSEAL) is issued to a legal entity, not an individual. Any employee authorized by the network administrator may trigger it — this is fully compliant with the eIDAS regulation.
Free · PRO · Server Edition
| Feature | Free | PRO | Server |
|---|---|---|---|
| Single file signing | ✅ | ✅ | ✅ |
| PKCS#12 + PKCS#11 hardware token support | ✅ | ✅ | ✅ |
| Single signer profile | ✅ | ✅ | ✅ |
| PDF Merge + Split | ✅ | ✅ | ✅ |
| Signature verification | ✅ | ✅ | ✅ |
| Aria AI chatbot | ✅ | ✅ | ✅ |
| macOS + Windows + Linux | ✅ | ✅ | ✅ |
| Bulk folder signing (unlimited) | ❌ | ✅ | ✅ |
| Unlimited signer profiles | ❌ | ✅ | ✅ |
| Serial multi-signer workflow | ❌ | ✅ | ✅ |
| All 9 PDF Tools + Utilities | ❌ | ✅ | ✅ |
| TSA timestamp (RFC 3161) | ❌ | ✅ | ✅ |
| Up to 3 device activations | ❌ | ✅ | ✅ |
| Folder Watch — automatic SEAL signing | ❌ | ❌ | ✅ |
| Telegram remote signing authorization | ❌ | ❌ | ✅ |
| Runs as background service | ❌ | ❌ | ✅ |
| Signing log + audit report (PDF) | ❌ | ❌ | ✅ |
| Department-isolated signing queues | ❌ | ❌ | ✅ |
| Per-organization license | ❌ | ❌ | ✅ |
| Internal .p12 certificate issuance | ❌ | ❌ | ⏳ in development |
Ready to automate your signing infrastructure?
Server Edition — €49.99/month · €499/year · €799 one-time