SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation

litellm.aivsvexp.dev

which is stronger?

clone time
2 weeks
soft

litellm.ai

OpenAI-format LLM gateway

84/ 100
wedge scorefull report ↗
clone time
8 weeks
soft

vexp.dev

local-first context engine

81/ 100
wedge scorefull report ↗
moat

how deep is each moat.

litellm.ai · aggregate
1.6/10shallow ditch
moat delta+0.3
vexp.dev · aggregate
1.9/10shallow ditch
1.0
capital±0
1.0
3.0
technical+1.0 →
4.0
1.0
network±0
1.0
2.0
switching±0
2.0
0.0
data±0
0.0
1.0
regulatory-1.0 →
0.0
distribution
floor

cost + time, side by side.

monthly floorlitellm.ai wins
litellm.ai
$27 + usage
vexp.dev
$46 + usage
delta −$19litellm.ai costs less per month to keep the lights on.
time to clonelitellm.ai wins
litellm.ai
2 weeks
vexp.dev
8 weeks
delta −4× faster2 weeks vs. 8 weeks.
overlap

where they fight, where they don't.

features only one ships, plus the small middle they share.
only litellm.ai · 00
litellm.ai is a strict subset of the shared surface.
shared · 11
llm inference
only vexp.dev · 11
marketplace
stack

what they're built on.

shared infra and the differentiating bits.
only litellm.ai · 1010
CloudflareCloudflare WorkersFramerNeonOpenAIPostgresCloudflare R2SentrySupabaseSupabase Auth
shared infra · 33
PostmarkResendVercel
only vexp.dev · 22
GitHubNext.js
the verdict
TOO CLOSE TO CALL

litellm and vexp land on the same moat depth, sit in the same tier, and present the same wall. either is a defensible angle of attack — the choice is taste, not difficulty.

the read
matched tiermatched wedge scoreland on the same moat depth
read both reports →
full reportsoft · 84
→ read the litellm.ai report
full reportsoft · 81
→ read the vexp.dev report