OpsCurb
Sign in
product

Roadmap

Upcoming improvements to scans, accountability workflows, and accountability automation.

4 min read
Updated 2026-03-08

Product Roadmap

This page reflects current priorities, not contractual delivery commitments.

OpsCurb is built for AWS-heavy teams that need to find waste, decide what matters, and push cleanup to completion without handing over write access. We prioritize roadmap work that improves one of these three outcomes:

  1. Faster time to first useful finding
  2. Better ownership and follow-through on savings work
  3. Stronger visibility into spend risk before the bill lands

On this page

Recently shipped

These are already in the product and should not be considered "coming soon":

  • AI guidance and model choice: remediation guidance, step-by-step fix help, and tier-based model access
  • Cost forecasting and budget tracking: month-end forecast, budget thresholds, and forecast risk visibility
  • Multi-account support: linked AWS accounts with org-level rollups on higher tiers
  • Slack, Discord, and email notifications: anomaly alerts, weekly digests, and Slack accountability workflows
  • Jira and Linear integrations (Growth / Scale): push findings directly into tickets with resource details, monthly waste, priority, and due date; ticket status syncs back in real-time
  • Deep Inspect and accountability workflows: owner assignment, status tracking, hygiene visibility, and richer finding analysis
  • Findings operating views for small ops teams: My Queue and Central Ops with owner-gap, commitment-gap, repeat-issue, and ticket-linked accountability rollups; profile-based owner assignment; first-scan assignment lanes by resource type
  • Remediation Briefs: every finding now carries a structured brief with a safe execution window, approval tier, reversibility rating, rollback command availability, and a Terraform/IaC state hint where applicable
  • Tagging and savings workflows: tagging policy controls plus reserved-instance and savings-plan views

Now

Highest-priority work for the next phase:

  • Founder-led audit workflow improvements: tighter first-scan narrative, clearer "what to do this week" output, and less noise in early findings
  • Shareable executive-summary output: cleaner first-scan brief that can be forwarded to founders, CTOs, or finance without editing
  • Webhook events: initial outbound events focused on scan completion, new findings, and anomaly detection
  • Custom dashboards and rollups: better summary views for teams managing several AWS accounts or recurring weekly reviews
  • Integrations that fit existing operator workflows: GitHub Actions for engineering-driven review loops and Microsoft Teams for customer teams not using Slack

Next

Likely after the current tranche, assuming continued customer demand:

  • Datadog and Grafana integrations: pushing findings into monitoring tools teams already use for triage
  • Persisted remediation approval state: storing the Remediation Brief to the database and tying approval-tier transitions to the finding lifecycle so approvals are trackable, not just visible
  • Expanded reporting surfaces: more export/share formats for weekly reviews, audit snapshots, and stakeholder updates
  • Enterprise workflow depth: more controls around retention, access patterns, and handoff between engineering, finance, and leadership

Later

Important, but not current front-of-queue work:

  • Kubernetes cost optimization
  • Chargeback/showback and broader FinOps reporting
  • Multi-cloud expansion (Azure or GCP) if demand becomes strong enough to justify the added complexity
  • Mobile experience improvements if customers need lightweight review workflows away from desktop

Not a near-term priority

To keep the product focused, we are not currently optimizing for:

  • becoming a generic observability platform
  • broad cloud-management automation with default write access
  • expanding to multiple clouds before AWS workflows are stronger
  • feature volume over clarity in the first-scan and weekly-review experience

How to influence the roadmap

The roadmap moves most when we hear repeated, concrete workflow pain from real teams. Good requests usually include:

  • what job you are trying to get done
  • who needs the output
  • what tool or step OpsCurb currently fails to replace
  • whether the blocker affects first-scan value, weekly review, or cleanup execution

Have a feature request? Submit it at feedback.opscurb.com or email support@opscurb.com.