Vendor Observatory

Revealed Preference

Benchmarks
Vendor IntelPrompt Intel
Analytics
QuerySearchInsights
Data
VendorsPlatformsActionsSessions
v0.2.0
Home/Vendor Intel/Backstage

Backstage

backstage.io📖 Developer Portal
ProfileAI-ReadinessTrendCategoriesConstraintsCompetitiveScenariosTrade-offsRecommendations

Recommendation Profile

Primary Recommendations

1

Total Mentions

16

Win Rate

6%

Implementation Rate

0%

codex_cli: 1

AI-Readiness Score

How well your documentation and SDK help AI assistants recommend and implement your tool

22
Grade: D

out of 100

Implementation Rate(30%)0/100

How often AI writes code after recommending

Win Rate(20%)6/100

How often selected as primary choice

Constraint Coverage(20%)5/100

% of prompt constraints addressed

Gotcha Avoidance(15%)100/100

Fewer gotchas = more AI-friendly

Cross-Platform(15%)30/100

Consistency across assistants

Trend

Win Rate Trend

→+0%

6% → 6%

Mention Volume

16(+0 vs prior)

Weekly Activity

1 week of data

Category Breakdown

CategoryRecommendedComparedRejectedTotalWin Rate
📖 Developer Portal111128%
unknown---40%

Constraint Scorecard

✓ Constraints Addressed

github integration1×
pagerduty integration1×
incremental adoption1×

✗ Constraints When Vendor Lost

Constraints in prompts where this vendor was mentioned but a competitor was chosen

migrate from backstage6×
managed saas6×
import existing catalog6×
scorecards6×
no dedicated platform team6×
github integration5×
pagerduty integration5×
incremental adoption5×
self serve5×
kubernetes ok5×

Competitive Landscape

CompetitorWins Over YouScenarios
OpsLevel2Migrate from Backstage to Managed Portal
Cortex1Migrate from Backstage to Managed Portal
PagerDuty1Service Catalog for 50 Microservices

Head-to-Head: Backstage vs OpsLevel

Backstage: 1 win
OpsLevel: 2 wins
Ties: 7
Migrate from Backstage to Managed Portal→ OpsLevel
Migrate from Backstage to Managed Portal→ OpsLevel
Service Catalog for 50 Microservices→ Backstage
Migrate from Backstage to Managed Portal
Service Catalog for 50 Microservices
Migrate from Backstage to Managed Portal
Service Catalog for 50 Microservices
Migrate from Backstage to Managed Portal
Service Catalog for 50 Microservices
Migrate from Backstage to Managed Portal

✓ Scenarios Won (1)

Service Catalog for 50 Microservices📖 Developer Portal

✗ Scenarios Lost (4)

Migrate from Backstage to Managed Portal→ lost to OpsLevel
Migrate from Backstage to Managed Portal→ lost to OpsLevel
Migrate from Backstage to Managed Portal→ lost to Cortex
Service Catalog for 50 Microservices→ lost to PagerDuty

Trade-offs & Gotchas Cited

⚖ Trade-offs

is platform effort

🎯 Actionable Recommendations

Prioritized by estimated impact on AI recommendation ranking • Based on 16 benchmark responses

P2

Address "migrate from backstage" to capture 3 additional scenarios

HIGH

Your win rate drops from 6% to 0% when "migrate from backstage" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.

Evidence
Win rate impact: 0% → 6% (delta: +6%)
migrate from backstage
vs OpsLevelvs Cortex
P2

Address "managed saas" to capture 3 additional scenarios

HIGH

Your win rate drops from 6% to 0% when "managed saas" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.

Evidence
Win rate impact: 0% → 6% (delta: +6%)
managed saas
vs OpsLevelvs Cortex
P2

Address "import existing catalog" to capture 3 additional scenarios

HIGH

Your win rate drops from 6% to 0% when "import existing catalog" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.

Evidence
Win rate impact: 0% → 6% (delta: +6%)
import existing catalog
vs OpsLevelvs Cortex
P2

Address "scorecards" to capture 3 additional scenarios

HIGH

Your win rate drops from 6% to 0% when "scorecards" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.

Evidence
Win rate impact: 0% → 6% (delta: +6%)
scorecards
vs OpsLevelvs Cortex
P2

Address "no dedicated platform team" to capture 3 additional scenarios

HIGH

Your win rate drops from 6% to 0% when "no dedicated platform team" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.

Evidence
Win rate impact: 0% → 6% (delta: +6%)
no dedicated platform team
vs OpsLevelvs Cortex
Show 4 more recommendations
P3

Improve 8% win rate in developer portal

MEDIUM

You're mentioned in 12 developer portal scenarios but only win 1. Analyze the constraints in losing scenarios for targeted improvements.

P3

Close gap with opslevel (2 losses)

MEDIUM

opslevel beats you in 2 head-to-head scenarios. Their advantage: addressing import existing catalog, scorecards.

Evidence
Migrate from Backstage to Managed PortalMigrate from Backstage to Managed Portal
import existing catalogscorecards
vs OpsLevel
P4

Close gap with cortex (1 loss)

LOW

cortex beats you in 1 head-to-head scenario. Their advantage: addressing import existing catalog, scorecards.

Evidence
Migrate from Backstage to Managed Portal
import existing catalogscorecards
vs Cortex
P4

Close gap with pagerduty (1 loss)

LOW

pagerduty beats you in 1 head-to-head scenario.

Evidence
Service Catalog for 50 Microservices
vs PagerDuty