What is built, and what is not
Most roadmaps are a wish list with the failures deleted. This one comes from the codebase.
How to read this. Everything under “in the console today” is running code you can be shown in a demo. Everything under “next” and “later” is not built yet, and we have not attached dates because we would only be guessing. The build log records what actually landed and when.
In the console today8
You can open these screens right now. Nothing here is a promise.
Live audits on AWS, Azure, GCP, DigitalOcean and Oracle Cloud
Connect an account with the read-only role CoverOps generates (Terraform, CloudFormation or CLI). Inventory, utilisation and cost come from the provider's own APIs, and every figure says whether it came from billing data or list prices.
Self-serve signup and the audit report
Sign up and connect one account for a free scan: your total waste and the top three findings. The audit lists every finding, priced per month in ₹ or $, with the evidence and the fix, reviewed by an engineer within 3 working days.
The console: cloud accounts, findings, approvals, audits and billing
Cloud inventory and cost, findings priced in rupees, approvals with rollback, the audit with its report, GST invoices and credit notes, a data export, and staff visits only with a reason. Kubernetes, GPU and agent screens run on demo data only.
Approved fixes with rollback
On AWS: stop, rightsize and delete-volume proposals on resources you tag coverops:managed=true. Each is re-checked against the live resource at approval and keeps a snapshot to roll back from.
Alerting across 26 metrics
One rule builder over infrastructure, cost and security metrics, sent in-app, by browser push, email, Slack, webhook and PagerDuty. GPU and agent metrics come from the demo estate only.
CoverOps Agent
A personal cloud agent inside the console. It reads your accounts through the read-only access you granted and tells you what to do now, this week and this month, with the exact command for each fix. It never changes anything itself. Chat is not available yet.
DigitalOcean and Oracle Cloud, live
Read-only inventory, billed cost and CPU utilisation through a scoped, expiring token on DigitalOcean and a signed API key on Oracle Cloud. Being proven on the first real accounts. Fixes on these two clouds are advice-only for now.
Alerts by email, Slack, webhook and PagerDuty
Alerts now send for real, as well as in-app and browser push. Every webhook destination is checked before anything is sent to it, and a failed delivery tells you why.
Next2
Being built now.
Off-hours schedules and storage tiering
Approved fixes that stop dev and test machines at night and move cold storage to cheaper tiers (S3 lifecycle, gp2 to gp3). Not built yet, so the audit lists them as advice today.
WhatsApp, Microsoft Teams and SMS
Approvals and alerts where Indian teams already talk. These channels are not connected yet, and the console says so.
Later1
Real intent, no date. Better undated than an invented quarter.
SOC 2 programme
We are not certified and will not imply otherwise. Today the platform keeps a named approval on every change and an audit log you can export as JSON.
Deliberately never1
Not a gap. A boundary, and the reason the rest is safe to adopt.
Hosting your workloads
This is a boundary, not a gap. CoverOps reads and changes your cloud; it never hosts it. The moment we run your workloads, leaving us stops being easy.
What would change our order
This is our current read, not a commitment. What moves an item up is hearing it is the reason a team cannot adopt us. If your blocker is a provider we do not cover live, or a certification we do not hold, say so. Knowing which gap costs us the most conversations is how we decide what to build next.
Tell us what is blocking you, or read the platform overview for what the four domains do today.