Gatsby
React-based static site generator with a powerful GraphQL data layer. Gatsby pulls data from multiple sources (CMS, APIs, files) at build time via a unified GraphQL layer and generates a static React site. Known for its plugin ecosystem (1000+ plugins), image optimization, and performance features. Widely used for marketing sites, blogs, documentation, and e-commerce. Gatsby acquired by Netlify in 2023.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
MIT open source. Static sites have minimal attack surface. Build secrets must not be exposed in GATSBY_ variables (public bundle). Netlify acquisition adds enterprise security backing.
⚡ Reliability
Best When
You need a content-rich static site pulling from multiple CMS/data sources, heavily optimized images, and a rich React ecosystem with Gatsby's 1000+ plugins.
Avoid When
Your site has highly dynamic content, very large page counts, or your team doesn't want GraphQL — Next.js or Astro are simpler alternatives.
Use Cases
- • Build fast static marketing and documentation sites using Gatsby's pre-rendering with data from headless CMS (Contentful, Sanity, Strapi)
- • Generate static agent documentation sites pulling from multiple data sources via Gatsby's unified GraphQL data layer
- • Create highly optimized image-heavy sites using Gatsby Image's automatic WebP conversion, lazy loading, and responsive images
- • Build e-commerce storefronts using Gatsby's Shopify integration with pre-built product pages and fast checkout flows
- • Generate API documentation or developer portals from OpenAPI specs using Gatsby's source plugin ecosystem
Not For
- • Highly dynamic applications — Gatsby's build-time rendering means real-time data requires client-side fetching; use Next.js for dynamic SSR
- • Very large sites (10,000+ pages) — Gatsby's build times scale with page count; incremental builds help but Next.js or Astro handle large sites better
- • Teams new to GraphQL — Gatsby's data layer requires GraphQL knowledge; Astro or Next.js are simpler if GraphQL isn't needed
Interface
Authentication
No built-in auth for static sites. Gatsby Cloud (now Netlify) has team auth. Client-side auth via Auth0, Clerk, or custom implementation for gated content.
Pricing
Gatsby framework is MIT open source. Acquired by Netlify in 2023 — Gatsby Cloud discontinued, replaced by Netlify's hosting. Framework development continues open source.
Agent Metadata
Known Gotchas
- ⚠ Gatsby's build time scales with content volume — sites with 10,000+ pages may take 30+ minutes to build; agents triggering rebuilds on every content change need incremental builds configured
- ⚠ GraphQL data layer queries only work at build time — agents expecting to query GraphQL at runtime must use client-side queries (useStaticQuery is build-time only)
- ⚠ Gatsby's plugin order matters in gatsby-config.js — wrong plugin order causes data conflicts or missing transformations; especially important for source + transformer plugin pairs
- ⚠ Gatsby's Node.js build APIs (gatsby-node.js) run in different context from browser code — environment variables prefixed with GATSBY_ are available in browser; others are build-time only
- ⚠ Gatsby 5 requires React 18 — projects on older React cannot upgrade without React migration; verify React version compatibility
- ⚠ Gatsby Cloud is discontinued — CI/CD workflows using Gatsby Cloud webhooks must be migrated to Netlify or alternative CI platforms
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Gatsby.
Scores are editorial opinions as of 2026-03-06.