What shipped, and what is missing

CoverOps is pre-launch, so this is a build log rather than a release history. We publish the gaps as well as the wins.

Shipped

Drift reconciliation on a schedule

CoverOps now re-plans every environment on an interval you configure and opens a pull request when live infrastructure has diverged from the committed Terraform. Previously drift was only detected on the next manual plan.

Improved

Plan output includes cost delta

Every generated pull request now carries the estimated monthly cost change alongside the resource diff, so the trade-off is visible at review time rather than at the end of the month.

Shipped

Azure support reaches parity with AWS

Service principal delegation, resource group topologies, AKS inventory, and policy evaluation now work on Azure with the same cost model and the same config file.

Fixed

Rollback no longer waits for the full health window

A remediation playbook now fires as soon as a threshold is decisively breached, rather than waiting out the remaining observation window. Found by a design partner during a real incident.

Shipped

Import from existing Terraform

Onboarding no longer assumes a greenfield account. CoverOps reads what you already run, generates matching configuration, and shows the diff before proposing any change.

Known gaps

The things we get asked for most and do not have yet. We would rather you learn this here than three weeks into an evaluation:

  • GCP is shallow. Accounts connect, but resource depth and cost modelling are well behind AWS and Azure. Parity is on the roadmap without a date attached.
  • Provider discovery is simulated. Inventory is synthesised from a per-provider catalog while everything downstream runs for real. Replacing it with live SDK clients is the largest piece of work in front of us.
  • No self-serve signup. Onboarding goes through a conversation with us while we are in early access.
  • No published pricing. We are still learning the right shape from design partners.
  • No third-party security certification. See the security page for what we do instead.

If one of these is a blocker for you, tell us. Knowing which gap costs us the most conversations is genuinely how we decide what to build next.