Primary Recommendations
4
Total Mentions
14
Win Rate
29%
Implementation Rate
100%
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
29% → 29%
Mention Volume
Weekly Activity
1 week of data
| Category | Recommended | Compared | Rejected | Total | Win Rate |
|---|---|---|---|---|---|
| 🗄 Database | 4 | - | - | 9 | 44% |
| ⚡ Edge Compute | - | - | - | 2 | 0% |
| unknown | - | - | - | 3 | 0% |
Constraints in prompts where this vendor was mentioned but a competitor was chosen
| Competitor | Wins Over You | Scenarios |
|---|---|---|
| Fly.io | 2 | Multi-Region API Deployment with Failover |
Upstash fits your constraints**
Prioritized by estimated impact on AI recommendation ranking • Based on 14 benchmark responses
Your win rate drops from 29% to 0% when "full nodejs runtime" is required. This constraint appears in 2 benchmark prompts. fly-io addresses it 2× in winning scenarios.
Your win rate drops from 29% to 0% when "multi region 3" is required. This constraint appears in 2 benchmark prompts. fly-io addresses it 2× in winning scenarios.
Your win rate drops from 29% to 0% when "single deploy" is required. This constraint appears in 2 benchmark prompts. fly-io addresses it 2× in winning scenarios.
Your win rate drops from 29% to 0% when "postgres multi region" is required. This constraint appears in 2 benchmark prompts. fly-io addresses it 2× in winning scenarios.
Your win rate drops from 29% to 0% when "budget conscious" is required. This constraint appears in 2 benchmark prompts. fly-io addresses it 2× in winning scenarios.
You're mentioned in 2 edge compute scenarios but only win 0. Analyze the constraints in losing scenarios for targeted improvements.
fly-io beats you in 2 head-to-head scenarios. Their advantage: addressing single deploy.