A ctlplne studio product
Topic · 8 posts

Renewal automation

ACME, renewal information, deployment and verification: what it takes to get renewal off people's calendars.

  1. 22 October 2026 · 3 min read

    Proving a renewal happened

    An auditor does not want to hear that renewals are automated. They want the record: who asked, who approved, what was issued, where it went, when it was verified, and proof the record has not been edited. What that evidence looks like when it is the system's own state.

    Audit and ownershipRenewal automationSelf-hosting

  2. 22 October 2026 · 3 min read

    Six-day and IP certificates: what they are for

    Let's Encrypt now issues certificates that live under a week and certificates for bare IP addresses. Neither is a curiosity. What each one is for, what it costs to run, and the profile menu that lets you choose.

    The 47-day scheduleRenewal automationPrivate PKI

  3. 22 October 2026 · 3 min read

    What an MSP does with 300 customers' certificates

    For a managed service provider the 47-day schedule is not a chore, it is a capacity problem: a book of business becomes tens of thousands of renewals a week. What one control plane for many customers has to guarantee, and the isolation you can prove rather than promise.

    The 47-day scheduleRenewal automationAudit and ownershipSelf-hosting

  4. 22 October 2026 · 3 min read

    Let the CA tell you when to renew

    ACME Renewal Information is the small protocol extension that turns renewal from a guess into an instruction: the authority publishes a window per certificate, and can pull it forward when something goes wrong. Why a cron job is the wrong tool, and what to do instead.

    Renewal automationThe 47-day schedulePKI fundamentals

  5. 22 October 2026 · 3 min read

    Renewal is not deployment

    The certificate renewed. The endpoint is still serving the old one. The five places a new certificate has to reach, why each one is different, and the check that tells you it got there.

    Renewal automationDiscovery and inventoryThe 47-day schedule

  6. 22 October 2026 · 3 min read

    What breaks on 15 March 2027

    The 100-day step is the first one that kills quarterly change tickets, 30-day expiry alerts, and manual domain validation. A dated checklist for the next cut in the schedule.

    The 47-day scheduleRenewal automationDiscovery and inventory

  7. 21 September 2026 · 6 min read

    Stop buying certificates. Start owning renewals.

    A public TLS certificate has been free for ten years. What you are still paying for, whether you buy it or not, is the renewal. What free already covers, where a purchase still makes sense, and the five jobs that are yours either way.

    Renewal automationThe 47-day schedulePKI fundamentals

  8. 21 September 2026 · 5 min read

    47 days: what actually changes

    The CA/Browser Forum has cut the lifetime of a public TLS certificate to 47 days by March 2029, and the proof that you own a name to ten days. The schedule, what breaks, and the four moves that make it a non-event.

    The 47-day scheduleRenewal automationPKI fundamentals