CertLord
TLS certificate lifecycle automation.
Version: 1.0.1 — stable. See the release notes.
CertLord automates TLS certificate issuance, renewal and deployment. It supports ACME through Certbot and importing existing PEM certificates, stores certificates in Vault and deploys them through Auton. Optional destination TLS verification checks the certificate actually served before acknowledgement. StatusCake/Updown adapters are optional; expiry observations are exposed for an external supervision system. It uses DWho, HTTPdis and Sonicprobe.
Redis stores temporary ACME HTTP-01 challenge responses and tracks pending work, retries and deployment leases. Vault stores certificate material. Use the Docker Compose installation to run the services together, or provision them separately for the Debian installation.
Docker installation
Use the Compose guide for initialization, persistent
Vault storage, API access and deployment configuration. The application image is
decryptus/certlord:1.0.1.
Command line and terminal interface
Use ordinary commands in scripts, or explicitly open the read-only terminal browser
with certlord tui. View the illustrated guide.
Real client capture with synthetic demonstration data; this is not deployment evidence.
Names and installation
- Python distribution and package:
certlord - Command and system service:
certlord - Default configuration:
/etc/certlord/certlord.yml - Service user and group:
certlord
Requires Python 3.11+ on POSIX; CI validates Python 3.11 and 3.12.
Newer interpreters are not yet validated. Install the Python package with python -m pip install ..
System configuration and external services must also be provisioned. The
Debian 12 package includes an isolated Python environment and the service account;
follow the installation guide before enabling the service.
Repository: https://github.com/decryptus/certlord.
Validate configuration, recovery and credentials in an isolated environment before deploying your service.
See MIGRATION.md before updating an existing installation.
Project documentation
- CLI and TUI screenshots
- Evaluate your installation
- Certificate UUIDs, HTTP API, CLI and TUI
- ACME HTTP Connector integration
- Debian 12 installation and isolated dependencies
- External certificate import and replacement
- Operations and recovery
- Operation correlation and optional Auton receipts
- Coding conventions and contributions
Guide: Certificate observations and supervision.
Post-deployment TLS verification checks configured destinations before acknowledgement.
Operations and recovery: health, queues, retries and first-version limits.
See configuration validation for YAML schema coverage and compatibility.
Documentation
- Users: installation, configuration, operation and API usage in this README and the user guide.
- Contributors: architecture, tests and development.
Textual terminal interface
See the Textual guide for installation, navigation and operation confirmations.
1 maintainer
Metadata
1 maintainer
Release files for certlord 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| certlord-1.0.1.tar.gz | 1.4 MB | With provenance | Details for certlord-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certlord-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for certlord-1.0.1-py3-none-any.whl |
Total release size: 1.5 MB
Release files / certlord-1.0.1.tar.gz
| Download URL | certlord-1.0.1.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54f730ae0bff842359adea0ee9ac838efa0c0060c5d04993ae1f34f30b933561
|
|
BLAKE2b-256 checksum How to use checksums |
3810d59e367bac9e6e6dc3d203c9b3b1d4a5a0e1372bccbe384fc023df333adc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / certlord-1.0.1-py3-none-any.whl
| Download URL | certlord-1.0.1-py3-none-any.whl |
|---|---|
| Size | 82.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
590bd4d5accf8c055620872c97ab0807ce92bfb8448630b01ee9a47333c91096
|
|
BLAKE2b-256 checksum How to use checksums |
3863f8255e8b97e44d12aa9aade25860eb127f59d950cae0dedf31fdf0e77a97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for certlord 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for certlord-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
