How It Works
Curb is a judgment engine that scores cloud announcements by relevance, urgency, and effortβthen helps you build a roadmap with Signal.
Our Philosophy: Cloud Intelligence
Curb closes the Cloud Capability Gap.
Enterprises already have TAMs for Breaking Changes and CSPM tools for Misconfigurations. But neither helps you plan the future of your platform based on how your cloud provider is evolving. That's what Curb does.
TAM Emails
Breaking changes & EOL notices. Reactive.
β You already have thisCSPM Tools
Misconfigurations & compliance gaps. Internal.
β You already have thisCurb Intelligence
How your CSP is evolving and what it means for your stack. Proactive.
π― This is the gapWhat Curb covers that others don't
π§ Environmental Drift
New defaults, changed behaviors, and shifted best practices that silently make your infrastructure suboptimal.
π Platform Opportunities
New services and tooling that could simplify your architecture or unlock capabilities your team doesn't know about yet.
π Strategic Foresight
Regional expansions, cost changes, and AI/ML moves that shape budget decisions and competitive positioning.
By analyzing every CSP announcement through a role-aware lens, Curb helps DevOps protect, Platform teams evolve, and Executives planβall from the same data, with different intelligence.
The Pipeline
-
Ingest
Pull AWS "What's New?" RSS feeds, security bulletins, and weekly roundups daily.
-
Classify
Determine if it's a LAUNCH (new feature), CHANGE (update/deprecation), or INCIDENT (outage/CVE).
-
Score
Apply RSDMT framework:
- Reliability impact (0-4)
- Security impact (0-4)
- Default Drift (0-4)
- Migration Cost (0-4)
- Toil Delta (-2 to +2)
-
Judge
Apply role-specific policies to assign postures:
- π₯ REMEDIATE - High Drift / Incident (Act immediately)
- π AUDIT - Medium Drift (Review and assess impact)
- π PLAN - Strategic Evolution (Add to roadmap)
- π OBSERVE - Informational (Monitor only)
-
Publish
Generate clean digests with no marketing fluff, organized by posture.
The Complete User Journey
From subscription to strategic action - all synced across devices
π‘ The Difference: Most tools show you "what's new." Curb shows you "what matters." We filter out product launches, marketing content, and hypeβkeeping only security issues, breaking changes, deprecations, and strategic opportunities that impact your infrastructure.
Posture Definitions
DevOps & Platform Teams
- π₯ Remediate - Issues requiring immediate action (outages, security vulnerabilities, breaking changes)
- π Audit - Issues requiring investigation and impact assessment
- π Plan - Future work to add to roadmap (not urgent)
- π Observe - Suppressed (not shown in digest)
Executive View
- π― Strategic - Aligns with business goals (cost optimization, AI, modernization)
- π Monitor - Track for potential strategic value
- π Optional - Low priority, informational
- π« Ignore - Suppressed (not shown in digest)
Role-Specific Policies
DevOps Teams
Focus on operational stability. Surface issues that:
- Cause outages or incidents (R β₯ 3)
- Create forced work or breaking changes (D β₯ 3)
- Reduce toil significantly (T β€ -1)
Platform Teams
Focus on infrastructure decisions. Surface issues that:
- Require IaC changes (M β₯ 2)
- Affect platform-critical services (S3, ECS, Lambda, etc.)
- Change architectural patterns
Executive
Focus on strategic alignment. Surface issues that:
- Have high strategic gravity (cost, AI, modernization)
- Affect competitive advantage
- Require governance decisions
The Signal Workflow
Once issues reach the Signal (Roadmap) page, they follow a deliberate lifecycle designed to separate thinking from execution.
1. Active (Planning)
The default state. Cards live here while you are evaluating them. Use Refine Mode to add context:
- Urgency (+): Sooner (High), Later (Medium), or Not Urgent (Low).
- Effort (T): Small, Medium, or Large resource sizing.
2. Shipped (Execution)
When ready to commit to downstream systems (Jira, GitHub), select cards and click π Ship Signal. This moves issues out of active view, crossing the boundary from "planning" to "doing".
3. Archived
For issues deemed irrelevant. Accessible via the Status filter ("Archived") but removed from the main flow.
Power Tools
- Refine Mode: Toggle to reveal "+" (Urgency) and "T" (Effort) widgets on cards.
- Global Export: Use "Export All" to generate reports for multiple quarters at once.
- Real-time Search: Instantly filter signals by service or title.
Content-Aware Filtering
Not all content is treated equally:
- Service Announcements - Scored and judged normally
- Operational Bulletins - Security/incident focus, elevated priority
- Implementation Guides - Informational, lower priority
- Marketing/PR - Suppressed for most roles
- Curation Recaps - Used to boost other issues, not published directly
Weekly Roundup Boost
Issues mentioned in AWS Weekly Roundup get the π AWS Curated badge and increased visibility.