Gatsby

United States · www.gatsbyjs.com · 13 vendors

Gatsby, Inc. provides an open-source frontend framework built on React and GraphQL for developing fast, secure, and scalable websites and web applications. It offers tools for integrating data from various sources and optimizing web performance.

Resilience scores

Technology vendors

Services catalogue

2 services in catalogue across 1 category; runs on 13 sub-vendors.

Insights

Last updated 2026-04-16 · revision 1

13 direct vendors, 161 subvendors

Direct vendors by controlling owner country (sample)

Subvendors by controlling owner country (sample)

Migration Readiness: 7/10

Assessed by AI based on technology stack characteristics (cloud-native vs legacy, containerization, microservices), regulatory environment, data residency requirements, financial stability, and vendor lock-in risks. The score ranges from 0-10, where higher scores indicate better readiness for technology migration.

Gatsby exhibits strong migration readiness from a technical perspective due to its modern, cloud-native friendly architecture. Its core framework leverages technologies like React, GraphQL, SSG/SSR/DSG, JAMstack, and supports CDN-based deployment and Cloud Functions, making it highly adaptable to various cloud environments. The existence of "Gatsby Adapters" further enhances its flexibility for deployment across different hosting platforms. However, a significant challenge to migration readiness is the high degree of vendor lock-in with Netlify. Despite the provided "Vendor Relationships" data stating "Total Vendors: 0", the company's internal tech stack and product evolution (Gatsby Cloud sunset, Gatsby Data Layer evolving into Netlify Connect) show a deep integration with Netlify's ecosystem. Migrating away from this integrated Netlify platform would involve considerable effort and potential re-architecture for existing users of Gatsby Cloud features. The lack of data regarding financial stability, specific regulatory requirements, and data residency needs prevents a full assessment of these potential migration complexities.

Compliance

3 in-scope frameworks identified; showing 3.

GDPR (source) — Assessment Required

Gatsby is a US-based company that explicitly processes personal data of EU/EEA residents through their cloud services and website. Their privacy policy acknowledges GDPR compliance obligations and includes specific sections for EEA residents. Risk is medium due to their established privacy framework and data protection measures, but ongoing compliance monitoring is required given the complexity of GDPR requirements for international data transfers.

Evidence: https://www.gatsbyjs.com/privacy-policy

ISO 27001 (source) — Assessment Required

No evidence found of ISO 27001 certification despite Gatsby being a cloud service provider handling customer data. While they have SOC2 compliance, ISO 27001 would provide additional assurance for information security management. Risk is medium as the absence doesn't indicate non-compliance, but certification would strengthen their security posture.

SOC 2 (source) — Compliant

Gatsby explicitly states SOC2 Type II compliance in their privacy policy, indicating they have undergone third-party security audits. This demonstrates strong security controls for a cloud service provider. Risk is low due to documented compliance and the nature of their cloud services requiring robust security measures.

Evidence: https://www.gatsbyjs.com/privacy-policy

Financials

Three-year financials

Financial Resilience Score: 2/10

Gatsby, Inc. demonstrated critically weak financial resilience, ultimately resulting in a distressed acquisition by Netlify in February 2023. Despite raising approximately $47M across Seed, Series A, and Series B rounds, the company was unable to raise a Series C, strongly indicating that it could not demonstrate sufficient revenue growth or a credible path to profitability to attract new capital at 2021–2022 market valuations. The acquisition was publicly characterized as a rescue transaction, with Netlify's own language acknowledging 'uncertainty around the future of Gatsby JS before Netlify stepped in,' confirming that equity value had deteriorated significantly relative to total capital invested. The company's open-core business model — free open-source framework driving adoption, with Gatsby Cloud as the sole commercial monetization layer — proved insufficient to generate the revenue scale needed for independent sustainability. Converting a large free developer user base into paying cloud customers is notoriously difficult, and Gatsby Cloud never achieved the commercial traction required. The immediate sunset of Gatsby Cloud by Netlify post-acquisition confirms the commercial product was not viable as a standalone offering. External pressures compounded internal weaknesses. Intensifying competition from Vercel (Next.js), Netlify, and Astro eroded Gatsby's market share significantly from 2021 onward. The 2022 tech downturn and rising interest rates further compressed valuations for growth-stage SaaS companies, making a standalone fundraise or premium exit untenable. The absence of any disclosed revenue figures, combined with the distressed exit outcome, reflects a company that exhausted its runway without achieving financial self-sufficiency. The sole mitigating factor is Gatsby's strong open-source brand and developer community, evidenced by Netlify retaining and maintaining the Gatsby JS framework post-acquisition and noting that Gatsby was used by more than 20% of Netlify Enterprise customers. However, this brand value accrued to the acquirer rather than providing resilience to the independent entity, and does not materially offset the overall picture of financial failure.

Key strengths: Strong open-source ecosystem with millions of npm downloads and large global developer community, Gatsby JS used by more than 20% of Netlify Enterprise customers at time of acquisition, Dual open-core revenue model with Gatsby Cloud as commercial SaaS monetization layer, Recognized brand in the Jamstack/modern web development ecosystem, Enterprise traction with paying Gatsby Cloud customers on structured contracts, Total of approximately $47M raised across Seed, Series A, and Series B rounds

Risk factors: Failed to raise Series C — unable to demonstrate sufficient revenue growth or path to profitability, Distressed acquisition by Netlify at undisclosed price, widely reported as below-expectation outcome, Gatsby Cloud immediately sunset post-acquisition, confirming commercial product was not viable, Intensifying competition from Vercel (Next.js), Netlify, and Astro eroded market share from 2021 onward, Open-source to paid conversion challenge — free user base failed to convert to commercial revenue at scale, Macroeconomic headwinds in 2022 compressed growth-stage SaaS valuations and dried up fundraising, No audited financial statements or revenue figures ever publicly disclosed, Equity value significantly deteriorated relative to ~$47M total capital invested

Revenue by geography

Revenue by product/service

Workforce by country

Signed-in users can see whether their own company is exposed to this vendor's disruption, plus the full sub-vendor list and country breakdowns, every in-scope compliance framework plus gaps and next steps, and alerts when any of it changes.

View the full interactive report