Docs
Deployment and operations
Run SignLayer on your own Linux servers with the SignLayer installer, or use the hosted Signing API.
Requirements
| Operating system | Ubuntu 20.04 LTS or newer; AlmaLinux, Rocky Linux, RHEL or CentOS 8 or newer |
|---|---|
| CPU architecture | x86-64 or arm64 (detected automatically) |
| Minimum hardware | 2 CPU cores, 4 GB RAM, 100 GB disk (SSD recommended). Scale with signing volume. |
| Network | Inbound 80 and 443; outbound HTTPS to OCSP/CRL services and Timestamp Authorities |
| You provide | Root access, a domain name, your licence key from Healiot, and an API token of your choosing |
Install
chmod +x signserver-installer.sh
sudo ./signserver-installer.sh -d your-domain.com -l '<licence key>' -a '<API token>'The installer sets up the Signing API, its internal PDF engine, the database and cache, and HTTPS for your domain. Supply a trusted certificate for production; a self-signed one is only for testing.
Place the HSM gateway on a private network
The HSM gateway runs next to your HSM. Only the Signing API should reach it: keep it on a private network or VPN, behind TLS, and firewall everything else.
Health and monitoring
GET /returns status and uptime for load balancers.- The operator configuration check reports whether each customer's HSM and Timestamp Authority are reachable.
- Usage statistics give counts per customer, per operation type and per day.
Hosted option
Prefer not to run servers? Use the SignLayer-hosted Signing API. Talk to us.