SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
google.comvsvexp.dev
which is stronger?
→vs←
moat
how deep is each moat.
google.com · aggregate
9.0/10deep moat
moat delta-7.1
vexp.dev · aggregate
1.9/10shallow ditch
9.0
capital-8.0 →
1.0
9.0
technical-5.0 →
4.0
10.0
network-9.0 →
1.0
8.0
switching-6.0 →
2.0
10.0
data-10.0 →
0.0
8.0
regulatory-8.0 →
0.0
—
distribution—
—
floor
cost + time, side by side.
monthly floortie
google.com
usage-based
vexp.dev
$46 + usage
monthly floor is roughly the same on both sides.
time to clonevexp.dev wins
google.com
∞
vexp.dev
8 weeks
delta · finite vs. ∞vexp.dev is buildable; google.com effectively isn't.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only google.com · 11
payment rails
shared · 11
marketplace
only vexp.dev · 11
llm inference
stack
what they're built on.
shared infra and the differentiating bits.
only google.com · 11
Rails
shared infra · 00
no shared dependencies.
only vexp.dev · 55
GitHubNext.jsPostmarkResendVercel
the verdict
ATTACK VEXP FIRST
same comparison surface, two different walls. wedge into vexp this weekend. circle back to google only if you genuinely need what it does that the other doesn't.
the case
a full tier easiershallower moat
full reportfortress · 10
→ read the google.com report
full reportsoft · 81
→ read the vexp.dev report
← saaspocalypse · directoryhead-to-head