Replace permanent SSH keys with short-lived certificates tied to verified identities. Works with standard OpenSSH—no custom clients needed.
{`# Request SSH certificate
$ ssh user@securd.example.com sign
✓ Identity verified
✓ Certificate issued
✓ Valid for 1 hour
# Connect to server
$ ssh user@prod-server-01
Welcome to prod-server-01!
Last login: Mon 10:32 from 192.168.1.100
# Certificate auto-expires
# No key rotation needed`}
Static SSH keys create security risks and operational headaches. Certificates solve both.
{benefit.description}
No custom clients required. Works with standard OpenSSH on servers and user machines.
{step.description}
{step.code}
The only requirement is OpenSSH 5.6+ on both client and server. Works on Linux, macOS, and most Unix systems.
See why organizations are switching from static SSH keys to certificate-based authentication.
| Feature | Static SSH Keys | SSH Certificates |
|---|---|---|
| {row.feature} | {row.static} | {row.cert} |
SSH certificates work for teams of all sizes and across different use cases.
{useCase.description}
Configure your servers to trust the Secuird CA. One configuration change, and all your servers accept certificates.
{`# Trust Secuird CA for user authentication
TrustedUserCAKeys /etc/ssh/securd_user_ca.pub
# (Optional) Use host certificates
HostCertificate /etc/ssh/ssh_host_ed25519_key-cert.pub
TrustedUserCAKeys /etc/ssh/securd_host_ca.pub
# Restart SSH to apply changes
$ systemctl restart sshd`}
Everything you need to manage SSH access at scale.
{feature.description}
Start your free trial today. Set up your first SSH CA in minutes and see the difference certificates make.