SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
github.comvsgoogle.com
which is stronger?
→vs←
moat
how deep is each moat.
github.com · aggregate
8.0/10deep moat
moat delta+1.0
google.com · aggregate
9.0/10deep moat
8.0
capital+1.0 →
9.0
8.0
technical+1.0 →
9.0
10.0
network±0
10.0
8.0
switching±0
8.0
7.0
data+3.0 →
10.0
6.0
regulatory+2.0 →
8.0
8.2
distribution—
—
floor
cost + time, side by side.
monthly floortie
github.com
$26 + usage
google.com
usage-based
monthly floor is roughly the same on both sides.
time to clonetie
github.com
∞
google.com
∞
neither is buildable as a clone — the fight here is the moat, not the build.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only github.com · 55
version history & creative timelineintegrationssocial loginsso (saml/oidc)webhooks
shared · 11
marketplace
only google.com · 11
payment rails
stack
what they're built on.
shared infra and the differentiating bits.
only github.com · 1010
AxiomCloudflareCloudflare WorkersFly.ioGitHubPostgresCloudflare R2RenderS3Sentry
shared infra · 00
no shared dependencies.
only google.com · 11
Rails
the verdict
ATTACK GITHUB FIRST
same comparison surface, two different walls. neither is a layup — github is the thinner wall. circle back to google only if you genuinely need what it does that the other doesn't.
the case
shallower moat
full reportfortress · 20
→ read the github.com report
full reportfortress · 10
→ read the google.com report
← saaspocalypse · directoryhead-to-head