Product roadmap
Hortval follows a pragmatic approach: build a strong ACME/ADCS core, then add visibility & management layers.
What the number means. It says what the product becomes, not what the upgrade will cost you. A patch (1.0.1) is replace and restart. A minor (1.1) adds a capability: back up, replace, restart. A major (2.0) gives the product a shape it did not have, it splits, distributes, gains a console: the same three steps.
A major is therefore neither a rewrite, nor a new licence, nor a migration project. Your licence covers every version, your ACME clients never change because the interface is RFC 8555 and not our API, and from 1.0.0 onward no release asks you to edit your configuration.
Stable does not mean 1.0.0. The product runs in production today, it does not crash, and it issues certificates daily. 1.0.0 says something else: it is the point where its configuration stops moving. Quality on one side, commitment on the other.
- ACME endpoint on your internal server
- Certificate issuance via ADCS
- HTTP-01, DNS-01 and TLS-ALPN-01 challenge support
- Compatible with certbot, acme.sh and any standard ACME client
- SQLite database
- PostgreSQL database
- SQL Server database
- Automatic cleanup / retention of expired records V1
- Health / metrics endpoints for supervision V1
- Split deployment: ADCS connector on Tier 0 + ACME responder on separate host
- Warm Active/Passive and Active/Active high availability (multi-node, requires PostgreSQL or SQL Server)
- Distributed validation agents for segmented networks (DMZ, multi-segment)
- Admin console
- Certificate expiry tracking
- Network scan — discover unmanaged TLS services