Insomnia
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
Comparison · Infra & APIs
Certbot vs kOps
A side-by-side editorial comparison of Certbot and kOps — release velocity, themes, recent moves, and the top alternatives to consider.
Certbot vs kOps: at a glance
What is Certbot?
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
Certbot is on a roughly monthly minor cadence and the defining change in this window is IP address certificate support. 5.3.0 added the --ip-address flag for the standalone and manual plugins and began renaming the API's domain concept to identifier; 5.4.0 extended IP issuance to the webroot plugin. The other visible work is structural: the nginx and apache plugin code moved into the certbot package as extras, the pyOpenSSL dependency is being unwound through a series of deprecations, and certbot.ocsp is scheduled for removal from the public API.
What is kOps?
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
kOps publishes alpha and beta tags rather than finals to this feed, with long commit lists dominated by provider-specific work. The 1.36 cycle removed Amazon Linux 2 support outright and changed omitted authorization to default to RBAC instead of AlwaysAllow. The 1.37 alpha continues along provider lines: Azure node identity now uses the IMDS attested metadata document, AWS reconciles target group health check changes on existing groups, GCE does the same for HTTP health checks, and Linode gained SSH key management.
Certbot vs kOps: editorial side-by-side
Certbot
2.5INFRA · APIS
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
◆ Current state
Certbot is on a roughly monthly minor cadence and the defining change in this window is IP address certificate support. 5.3.0 added the --ip-address flag for the standalone and manual plugins and began renaming the API's domain concept to identifier; 5.4.0 extended IP issuance to the webroot plugin. The other visible work is structural: the nginx and apache plugin code moved into the certbot package as extras, the pyOpenSSL dependency is being unwound through a series of deprecations, and certbot.ocsp is scheduled for removal from the public API.
◆ Where it's heading
The identifier rename is the tell — Certbot's data model assumed a certificate subject was a domain name, and IP address issuance forced that assumption out of the type system. Expect that refactor to continue reaching further into the plugin API, since get_chall_pref has already changed signature. In parallel the project is shedding dependencies and consolidating packaging: plugins as extras rather than separate distributions, pyOpenSSL functions deprecated batch by batch, and Docker images tracking new Python versions promptly. The releases have become small and predictable, with most content in the Changed and Fixed sections rather than Added.
◆ Prediction
Expect IP address support to reach the remaining plugins, following standalone and manual then webroot, and expect the pyOpenSSL removal to land as a major version once the deprecation cycle completes. Given 5.5.0 already deprecated certbot.ocsp for removal in the next major, that release is the one to watch for breaking changes.
kOps
2.5INFRA · APIS
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
◆ Current state
kOps publishes alpha and beta tags rather than finals to this feed, with long commit lists dominated by provider-specific work. The 1.36 cycle removed Amazon Linux 2 support outright and changed omitted authorization to default to RBAC instead of AlwaysAllow. The 1.37 alpha continues along provider lines: Azure node identity now uses the IMDS attested metadata document, AWS reconciles target group health check changes on existing groups, GCE does the same for HTTP health checks, and Linode gained SSH key management.
◆ Where it's heading
Two patterns run through these tags. The first is reconciliation — kOps is closing the gaps where it created a resource but never re-checked it, which is what turns a provisioning tool into something that can be run continuously. The second is deliberate narrowing: dropping Amazon Linux 2 and defaulting authorization to RBAC both trade compatibility for a safer, smaller supported matrix.
◆ Prediction
The health check reconciliation pattern has now landed for AWS and GCE in the same cycle, so Azure and the smaller providers are the likely next targets.
Alternatives to Certbot and kOps
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Certbot or kOps.
Headlamp
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Kubeshark
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
electerm
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
Robusta
Alpha-tagged releases doing unglamorous enterprise plumbing — logs, RBAC, ingestion.
See all Certbot alternatives → · See all kOps alternatives →
Recent activity from Certbot and kOps
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agoCertbot5.7.0 fixes nginx parsing of comments inside multi-line directives
- 25d agokOpsAzure attested node identity; AWS and GCE health check reconcile
- 1mo agokOpsOmitted authorization now defaults to RBAC instead of AlwaysAllow
- 2mo agokOpsAmazon Linux 2 support removed; warm pools take user-defined images
- 2mo agoCertbot5.6.0 bumps dependency floors and rebases Docker on Python 3.14
- 4mo agoCertbot5.5.0 folds the nginx and apache plugins into certbot extras
- 5mo agoCertbot5.4.0 extends IP address issuance to the webroot plugin
- 6mo agoCertbot5.3.1 rebuilds snaps with updated dependencies
- 6mo agoCertbotCertbot adds IP address certificates and an identifier-based API ⚡
Frequently asked questions
What is the difference between Certbot and kOps?
They serve adjacent needs but don't currently overlap on shipped themes. Certbot and kOps are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Certbot better than kOps?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Certbot and kOps are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Certbot?
Top Certbot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Certbot alternatives" section above for the current picks, or visit /alternatives/certbot for the full list with editorial commentary on each.
What are the best alternatives to kOps?
Top kOps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "kOps alternatives" section above for the current picks, or visit /alternatives/kops for the full list with editorial commentary on each.