SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
github.comvsslack.com
which is stronger?
→vs←
clone time
3 months
contested3 months
slack.com
team messaging & AI work platform
43/ 100
wedge scorefull report ↗
moat
how deep is each moat.
github.com · aggregate
8.0/10deep moat
moat delta-2.3
slack.com · aggregate
5.7/10real moat
8.0
capital-3.0 →
5.0
8.0
technical-4.0 →
4.0
10.0
network-2.0 →
8.0
8.0
switching-2.0 →
6.0
7.0
data-4.0 →
3.0
6.0
regulatory-4.0 →
2.0
8.2
distribution+0.2 →
8.4
floor
cost + time, side by side.
monthly floorgithub.com wins
github.com
$26 + usage
slack.com
$47
delta −$21github.com costs less per month to keep the lights on.
time to cloneslack.com wins
github.com
∞
slack.com
3 months
delta · finite vs. ∞slack.com is buildable; github.com effectively isn't.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only github.com · 77
version history & creative timelinedeveloper ecosystemintegrationsmarketplacesocial loginsso (saml/oidc)webhooks
shared · 11
social graph
only slack.com · 33
serverless / edge platformapi platformsubscriptions
stack
what they're built on.
shared infra and the differentiating bits.
only github.com · 77
AxiomCloudflare WorkersFly.ioGitHubRenderS3Sentry
shared infra · 33
CloudflarePostgresCloudflare R2
only slack.com · 88
MeilisearchNextAuthNext.jsResendSalesforceSupabaseSupabase AuthVercel
the verdict
ATTACK SLACK FIRST
same comparison surface, two different walls. give the slack attack a month. circle back to github only if you genuinely need what it does that the other doesn't.
the case
a full tier easiershallower moat
full reportfortress · 20
→ read the github.com report
full reportcontested · 43
→ read the slack.com report
← saaspocalypse · directoryhead-to-head