SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
castordoc.comvsgithub.com
which is stronger?
→vs←
moat
how deep is each moat.
castordoc.com · aggregate
4.4/10shallow moat
moat delta+3.6
github.com · aggregate
8.0/10deep moat
6.0
capital+2.0 →
8.0
6.0
technical+2.0 →
8.0
2.0
network+8.0 →
10.0
5.0
switching+3.0 →
8.0
3.0
data+4.0 →
7.0
2.0
regulatory+4.0 →
6.0
—
distribution—
8.2
floor
cost + time, side by side.
monthly floorgithub.com wins
castordoc.com
$27 + usage
github.com
$26 + usage
delta +$1github.com costs less per month to keep the lights on.
time to clonecastordoc.com wins
castordoc.com
8 weeks
github.com
∞
delta · finite vs. ∞castordoc.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 castordoc.com · 33
etl / data pipelinellm inferencerole-based access control
shared · 33
version history & creative timelineintegrationssso (saml/oidc)
only github.com · 33
marketplacesocial loginwebhooks
stack
what they're built on.
shared infra and the differentiating bits.
only castordoc.com · 1111
AnthropicBigQueryCloudflare PagesGA4OpenAIPlausibleSnowflakeStripeSupabaseVercelWebflow
shared infra · 44
CloudflarePostgresCloudflare R2Sentry
only github.com · 66
AxiomCloudflare WorkersFly.ioGitHubRenderS3
the verdict
ATTACK CASTORDOC FIRST
same comparison surface, two different walls. give the castordoc 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 reportcontested · 56
→ read the castordoc.com report
full reportfortress · 20
→ read the github.com report
← saaspocalypse · directoryhead-to-head