Primary Recommendations
1
Total Mentions
25
Win Rate
4%
Implementation Rate
0%
How well your documentation and SDK help AI assistants recommend and implement your tool
out of 100
How often AI writes code after recommending
How often selected as primary choice
% of prompt constraints addressed
Fewer gotchas = more AI-friendly
Consistency across assistants
Win Rate Trend
4% → 4%
Mention Volume
Weekly Activity
1 week of data
| Category | Recommended | Compared | Rejected | Total | Win Rate |
|---|---|---|---|---|---|
| 📊 Observability | 1 | 2 | - | 16 | 6% |
| 🔀 Cross-Category | - | - | - | 2 | 0% |
| 📖 Developer Portal | - | - | - | 4 | 0% |
| unknown | - | - | - | 3 | 0% |
Constraints in prompts where this vendor was mentioned but a competitor was chosen
| Competitor | Wins Over You | Scenarios |
|---|---|---|
| New Relic | 1 | Full-Stack Observability for Express on ECS |
| Backstage | 1 | Service Catalog for 50 Microservices |
| Honeycomb | 1 | Managed OTel Backend Replacing Self-Hosted Jaeger |
| PagerDuty | 1 | Service Catalog for 50 Microservices |
Prioritized by estimated impact on AI recommendation ranking • Based on 25 benchmark responses
Your win rate drops from 4% to 0% when "github integration" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 4% to 0% when "pagerduty integration" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 4% to 0% when "incremental adoption" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 4% to 0% when "self serve" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 4% to 0% when "kubernetes ok" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
You're mentioned in 16 observability scenarios but only win 1. Analyze the constraints in losing scenarios for targeted improvements.
You're mentioned in 4 developer portal scenarios but only win 0. Analyze the constraints in losing scenarios for targeted improvements.
new-relic beats you in 1 head-to-head scenario. Their advantage: addressing free tier.
backstage beats you in 1 head-to-head scenario. Their advantage: addressing github integration, pagerduty integration, incremental adoption.
honeycomb beats you in 1 head-to-head scenario.