Supabase

1.1 Identity and business model

Founded in 2020 by Paul Copplestone and Ant Wilson, Supabase packages a managed Postgres database with authentication, data APIs, edge functions, realtime data, storage, and vector capabilities. The product is positioned as an open-source development platform rather than a single database utility, with a free entry point and paid plans plus usage charges as projects scale. The legal and operating presentation needs precision: Supabase's privacy notice identifies Supabase Pte. Ltd. as the controller, and Tracxn records an active Singapore entity incorporated on February 20, 2020, while FundedIQ and the October financing release present San Francisco as the operating base. The distinction matters for contracting, governance, tax, and domicile diligence.[CO001, CO002, CO003]

1.2 Leadership and governance

The two founders remain the visible operating leaders: Copplestone is CEO and Wilson is CTO. That continuity supports product coherence and founder-market fit, but it also concentrates strategic and technical authority in two people. Tracxn's public board record lists only the two founders as active members and one past independent member; this is not a definitive cap-table or statutory-board disclosure. No assigned source establishes current outside directors, observer rights, voting thresholds, founder ownership, or investor protective provisions. Those omissions make governance documents, succession coverage, and reserved-matter rights priority diligence items rather than facts to infer from investor prestige.[CO002, CO004, CO005]

1.3 Capitalization and operating scale

Supabase announced a $500 million Series F in June 2026 at a $10 billion pre-money valuation, or approximately $10.5 billion post-money. Four months later, a company-issued release announced another $150 million led by GIC and the acquisition of Turso, without disclosing a new valuation. Cumulative funding cannot be stated as one verified number: RevenueMemo reports about $996 million through the June round, FundedIQ captures $880 million across four rounds, and Tracxn reports $1.19 billion across eight rounds after October. These scopes are not interchangeable, and part of the financings included employee liquidity, so funding raised should not be treated as cash available.[CO006, CO007, CO008, CO009, CO010]

1.4 Momentum, milestones, and open metrics

Company-reported reach increased from nearly 10 million developers in June to more than 13 million in October. The October release also claimed more than one million users and four million databases added per month, with 70% of new databases created by agents or AI-driven tools. These are usage indicators, not customer, revenue, retention, or monetization metrics. Workforce datasets also conflict: FundedIQ gives a 101-250 band, while Tracxn states 439 employees as of August 2026. A financing process should therefore obtain dated payroll, customer, ARR, gross-margin, burn, and net-retention schedules before using usage growth or funding size as a proxy for operating performance.[CO011, CO012, CO013, CO014, CO015, CO016]

1.5 Exhibits

2.1 Market Boundary, Category Scope, and Spend Definition

Supabase operates across the developer backend infrastructure and managed database market, specifically centered on the PostgreSQL relational ecosystem. The primary category encompasses managed database hosting, developer backend-as-a-service (BaaS), authentication and identity management, serverless edge compute execution, file and object storage, real-time data streaming, and vector embedding indexing via pgvector. Included customer spend consists of dedicated database compute instances, monthly active user identity bands, origin and cached bandwidth egress, operational storage capacity, and enterprise compliance add-ons such as SOC2, ISO 27001, and HIPAA certifications. Conversely, excluded customer spend comprises front-end web application hosting (dominated by ecosystem partners such as Vercel and Netlify), full-suite enterprise data warehousing and analytical OLAP infrastructure (such as Snowflake and Databricks), and legacy proprietary enterprise NoSQL databases. Rather than replacing the web hosting platform, Supabase sits adjacent to modern application frameworks: 40.05% of detected Supabase production domains run alongside Vercel, demonstrating that Supabase functions as a composable data layer rather than an all-in-one PaaS monolith. Primary substitutes include legacy cloud BaaS platforms like Google Firebase, hyperscaler primitives such as AWS Amplify with DynamoDB and Cognito, and emerging serverless Postgres vendors such as Neon.[CM001, CM002, CM005, CM006, CM014]

2.2 Addressable Market Sizing, Growth Horizons, and Sizing Discrepancies

Sizing the addressable market for Supabase requires evaluating distinct horizons rather than accepting a single top-down total addressable market (TAM) figure. At the macro level, the global database management systems (DBMS) and cloud data infrastructure market represents a $100B+ aggregate spend category expanding at double-digit compound annual growth rates, with relational systems remaining the standard across 80% of startup engineering stacks. Within this landscape, the serviceable addressable market (SAM) for developer-centric backend platforms, managed Postgres, and BaaS solutions accounts for an estimated $12B to $18B. Supabase's serviceable obtainable market (SOM) is specifically anchored in self-service developer subscriptions (Pro plans at $25/month), team collaboration environments ($599/month), and custom enterprise contracts for security-sensitive organizations. Industry benchmarks from independent web crawlers reveal that Supabase commands 0.83% of the broad PaaS category across 19,361 tracked domains as of August 2026, ranking #11 among 41 monitored technologies. However, market adoption metrics display a sharp dichotomy: while top-line database creation surged over 600% year-over-year—propelled by autonomous coding agents and AI builders launching over 60% of new projects—commercial monetization remains highly concentrated. Public domain detections and community forums frequently isolate Supabase to microsites, hackathons, or subsidiary subdomains rather than core enterprise transactional ledgers. Sizing models that equate 10 million registered developer users directly with commercial ARR risk vastly overstating true enterprise wallet capture.[CM003, CM004, CM005, CM011, CM012, CM014]

2.3 Buyer Personas, User Segmentation, and Procurement Ownership

Customer segmentation and budget ownership within the Supabase ecosystem divide cleanly into three tiers: individual developers and proto-startups, growth-stage engineering teams, and regulated enterprises. The entry-level user persona is an individual developer, hobbyist, or non-technical founder building an initial application. These users operate on the generous Free tier (supporting two active projects, 500 MB database disk, and up to 50,000 monthly active users) and are motivated by instant SQL APIs and zero initial capital outlay. The economic buyer at the growth stage is typically a technical founder, CTO, or VP of Engineering who upgrades to the Pro tier ($25 per organization/month) once an application requires production reliability, daily backups, and SLAs. At this level, budget ownership resides within departmental engineering credit card spend. The third segment comprises established mid-market companies and enterprises requiring organizational controls, single sign-on (SSO), 14-day to 90-day log retention, SOC2/ISO 27001 compliance (standard on the $599/month Team tier), or dedicated HIPAA agreements and private Slack channels on custom Enterprise contracts. In enterprise environments, the purchasing authority shifts from individual developers to central IT procurement, security review boards, and finance directors who scrutinize data processing addenda and regulatory guarantees.[CM007, CM008, CM010, CM013]

2.4 Structural Growth Drivers and Critical Adoption Constraints

Supabase's rapid market expansion is propelled by two structural tailwinds: the industry-wide consolidation around PostgreSQL and the explosion of AI-assisted code generation. In the startup ecosystem, Postgres penetration expanded to 80% in 2026, while legacy NoSQL alternatives like MongoDB, MySQL, and Firebase consistently lost market share. Furthermore, the advent of AI coding agents such as Claude Code and Codex has fundamentally accelerated database provisioning: over 60% of newly launched Supabase databases are spun up automatically by AI tooling. Native support for pgvector within standard relational tables allows developers to build retrieval-augmented generation (RAG) pipelines without deploying separate vector database infrastructure. However, material constraints govern enterprise adoption. Foremost among these is pricing predictability and overage risk: while baseline plan pricing is low, project compute instances are billed per project ($10 monthly credit covers only one micro instance), and high-traffic applications face cumulative fees for database storage, egress bandwidth ($0.09/GB for origin egress), and identity quotas. At 100,000 monthly active users, identity and compute bills can swing total costs unexpectedly. Additionally, switching costs away from entrenched cloud providers (AWS, Google Cloud) remain high for large enterprises with negotiated volume discounting and established IAM governance.[CM001, CM005, CM009, CM010, CM011]

2.5 Market Diligence Priorities, Gaps, and Sizing Inconsistencies

A rigorous evaluation of Supabase's market standing exposes critical diligence gaps that prevent conclusive sizing of its long-term enterprise penetration. First and foremost, audited figures for Annual Recurring Revenue (ARR), revenue run-rate, and net revenue retention (NRR) remain private and undisclosed. Although the company secured a $500M Series F funding round at a $10.5B post-money valuation in June 2026, private estimates of ARR vary widely without third-party audit verification. Second, third-party domain crawl intelligence indicates that while Supabase is detected on 19,361 domains, 15% of historical detections drop between crawls due to front-end JavaScript detection volatility, and primary customer references frequently reside on non-critical community subdomains rather than primary application backends. Third, the long-term conversion rate from free AI-generated hobbyist projects into stable, recurring enterprise contracts remains unproven. Diligence must establish whether autonomous coding agents generate durable, high-ACV enterprise software or ephemeral prototypes that abandon paid tiers after free trials lapse.[CM003, CM004, CM008, CM012, CM014]

2.6 Exhibits

3.1 Competitive Landscape & Market Segmentation

The developer infrastructure landscape surrounding Supabase spans four primary segments: hyperscale cloud providers assembling à la carte primitives, proprietary backend-as-a-service platforms, focused serverless database specialists, and open-source or bring-your-own-cloud (BYOC) frameworks. Hyperscalers such as Amazon Web Services dominate overall cloud developer workloads, with PostgreSQL serving as the primary relational database across the industry. However, assembling production backends on AWS requires configuring VPC networking, security groups, IAM policies, and disparate services like RDS, Cognito, S3, and Lambda, which introduces substantial operational complexity for early-stage teams. Proprietary platforms like Google's Firebase offer fast onboarding and mature mobile tooling, but lock developers into proprietary NoSQL document stores and specialized query models. In contrast, serverless Postgres offerings like Neon concentrate narrowly on database autoscaling and branching rather than bundling application-level services. Meanwhile, BYOC frameworks like Encore and Northflank provide infrastructure deployment into a customer's own cloud account, offering architectural flexibility for engineering organizations that outgrow managed multi-tenant services.[CP001, CP002, CP007]

3.2 Feature Capabilities & Architectural Trade-offs

Supabase differentiates primarily through its developer experience and unified product packaging, providing managed PostgreSQL alongside row-level security, built-in authentication, object storage, serverless edge functions, and WebSocket-based realtime streaming from a single console. This architectural bundling eliminates the integration friction typically required to wire independent infrastructure components together. Compared to Firebase, Supabase provides standard PostgreSQL with complete relational schema flexibility, advanced indexing, and pgvector extensions, directly benefiting applications incorporating artificial intelligence workflows. However, the bundled architecture involves deliberate technical compromises. Supabase Edge Functions execute on the Deno runtime with bounded execution times, which limits their suitability for long-running compute jobs or heavy asynchronous background processing. For complex asynchronous task orchestration or high-concurrency microservice architectures, development teams often supplement Supabase with dedicated compute workers or hybrid cloud services.[CP003, CP004, CP008, CP012]

3.3 Pricing Inflection Points & AWS Migration Dynamics

Total cost of ownership between Supabase and hyperscale cloud providers diverges sharply depending on user scale and resource consumption mix. For early-stage and growing applications with up to 100,000 monthly active users, Supabase delivers substantial economic advantages. A typical 100,000 MAU workload on Supabase incurs approximately $600 to $650 per month, whereas an equivalent on-demand architecture on AWS totals $3,000 to $3,200 monthly. This asymmetry is driven overwhelmingly by authentication costs: AWS Cognito charges $0.015 per MAU beyond its 10,000-user free tier, representing a 4.6x premium over Supabase's $0.00325 per MAU overage fee. As applications reach 1,000,000 or more active users, however, the economic calculus shifts. At higher scales, enterprise agreements, Reserved Instance compute commitments offering 30% to 60% discounts, and granular network optimization enable hyperscalers to deliver superior unit economics. Bandwidth egress at $0.09 per gigabyte and vertical compute instance upgrades on Supabase also represent significant expense drivers that encourage high-throughput platforms to evaluate migrating workloads directly into native cloud environments.[CP005, CP006, CP011]

3.4 Moat Durability, Switching Costs & Displacement Risks

Supabase derives strong defensibility from its open-source positioning, developer mindshare, and integrations with modern AI application builders including Lovable, Replit, and Figma. By standardizing on open-source PostgreSQL, the company offers a high degree of core relational data portability, allowing teams to export schemas and dump data into any standard Postgres installation with minimal impedance mismatch. Nevertheless, meaningful switching costs persist at the application layer. Migrating away from Supabase requires refactoring platform-specific authentication helpers, client SDK calls, row-level security rule assumptions, and WebSocket subscriptions. Furthermore, Supabase faces structural architectural constraints at the upper end of the enterprise market. Because the platform relies on a single-writer PostgreSQL compute model without native horizontal sharding, workloads requiring distributed multi-region writes or extreme transactional throughput eventually hit vertical ceilings. Additionally, gating enterprise single sign-on (SAML) and HIPAA compliance behind upper-tier commercial agreements creates adoption friction for regulated enterprises.[CP009, CP010, CP013, CP014]

3.5 Exhibits

4.1 Revenue Model and Pricing

Supabase monetizes a bundled cloud platform rather than a single database product. Its official site describes Postgres database, authentication, APIs, edge functions, realtime, storage, and vector capabilities, while Sacra characterizes the commercial model as tiered subscription SaaS with additional charges tied to database size, bandwidth, and monthly active users. Sacra lists Free, Pro at $25 per month, and Team at $599 per month, but these are secondary-source list prices, not evidence of realized contract value, discounting, or revenue recognition. The public source set also does not disclose how much revenue comes from base subscriptions, usage, enterprise terms, or Supabase for Platforms. That distinction matters because a large developer funnel can produce very different revenue quality depending on conversion, workload persistence, and the share of metered consumption.[CI005, CI006, CI010, CI012, CI013, CI014]

4.2 Traction and GTM Efficiency Proxies

Public traction signals are strong but should not be conflated with audited revenue. Supabase said in June that it had more than 250,000 customers and that Supabase for Platforms customer count had grown 370% in six months. In October it reported adding more than one million users and four million databases per month, with 70% of new databases created by agents or AI-driven tools. CNBC separately reported a 350-person workforce in June, while Sacra argues that coding-assistant distribution lowers go-to-market costs. Together these metrics suggest efficient product-led distribution, not a measured CAC payback period: the retained sources provide no paid/free split, sales and marketing spend, cohort conversion, NRR, or customer concentration. Sacra's $170 million May ARR estimate is therefore useful as a directional third-party estimate, not a substitute for a management revenue ledger.[CI004, CI008, CI009, CI010, CI011]

4.3 Cost Structure and Capital Adequacy

The clearest public cost signal is Sacra's assessment that hosting and storage pressure gross margin, which is directionally consistent with a managed database platform but does not quantify COGS or margin. In 2026, Supabase announced $650 million of financing across the June and October rounds, including a $500 million Series F at a $10.5 billion post-money valuation and a $150 million October financing tied to the Turso acquisition. Proceeds were intended for product development and employee liquidity. Financing raised is not cash on hand: the retained sources do not disclose primary versus secondary allocation, acquisition consideration, current cash, debt, monthly burn, capex, or committed infrastructure obligations. Those omissions prevent a defensible runway calculation or a conclusion that near-term financing risk is low.[CI001, CI002, CI003, CI007, CI015, CI016]

4.4 Underwriting Verdict and Diligence Blockers

The financial case is attractive at the demand layer and incomplete at the economics layer. Subscription plus usage pricing can expand with customer workloads, and agent-led distribution may reduce acquisition cost, but infrastructure consumption rises with the same activity and no retained source establishes contribution margin, retention, or profitability. Even headline financing totals require care: Multiples reports $996 million across eight rounds, whereas Supabase's June release said more than $1 billion before the additional October round. The discrepancy may reflect source timing or aggregation methodology, but it should not be silently reconciled. Investment underwriting therefore requires management evidence for ARR definition, GAAP revenue, gross margin by product, free-to-paid conversion, NRR, customer concentration, cash, burn, financing terms, and Turso consideration before assigning a durable growth or runway conclusion.[CI004, CI006, CI007, CI008, CI014, CI015, CI016]

4.5 Exhibits

5.1 Product surface and customer workflow

Supabase is delivered as an integrated backend development platform rather than as a standalone database. A developer starts with a full Postgres database and can add authentication, generated data APIs, realtime synchronization, object storage, edge functions, and vector search through one product surface. The customer workflow compresses infrastructure assembly: teams model relational data, attach row-level access policies, call generated APIs or client libraries, and use adjacent services without selecting and integrating a separate vendor for each layer. This breadth is verified primarily from Supabase's current website and architecture documentation; a commercially interested third-party explainer corroborates the broad module set but is not an independent benchmark. The product therefore has a credible breadth advantage, while measurable time-to-production and migration outcomes remain deployment-specific.[CE001, CE002, CE003, CE004, CE005, CE006, CE007, CE010]

5.2 Architecture, composition, and portability

Postgres is the system of record and is not hidden behind a proprietary database abstraction. Supabase composes established components around it: GoTrue issues tokens for authentication, PostgREST exposes relational data through REST, Realtime handles WebSocket presence and database-change streams, Storage uses an S3-compatible service with metadata in Postgres, Deno runs edge functions, and Supavisor pools Postgres connections. This decomposition creates two advantages: customers can adopt modules incrementally, and standard Postgres export paths reduce data lock-in. It also creates an integration burden because the delivered experience depends on several runtimes, protocols, and release trains behaving coherently. The architecture is well documented, but the public sources reviewed do not quantify failure isolation, service-level performance, or the operational burden of self-hosting the complete stack.[CE002, CE003, CE004, CE005, CE006, CE007, CE008, CE009, CE010]

5.3 Deployment maturity, reliability, and scale

The available evidence indicates both active scale investment and unresolved implementation risk. TechCrunch reported in June 2026 that Supabase launched Multigres to centralize Postgres scaling tasks including read replicas, failovers, connection limits, and backups. That is evidence of roadmap response, not proof that a specific workload will meet its latency, availability, or recovery objectives. An independent self-hosting practitioner separately asked how connection limits interact with API traffic and how to stress-test a pending traffic increase, demonstrating that capacity planning is not self-evident from the product surface. A historical 2023 practitioner review also reported local-versus-remote parity problems and client transaction limitations. Those reports are anecdotes rather than fleet-wide measurements, but they define concrete diligence tests: load, failover, migration, rollback, connection-pool, and local-to-hosted parity exercises on the buyer's actual topology.[CE011, CE012, CE013, CE016]

5.4 Differentiation, trust controls, and diligence verdict

The strongest technical differentiation is the combination of integrated developer experience with recognizable open-source primitives and direct Postgres access. This makes portability more credible than a proprietary data model would, but self-hosting transfers operating responsibility rather than eliminating it. On privacy, Supabase states that it acts primarily as a processor for customer-submitted end-user data and uses commercially reasonable physical, technical, and organizational safeguards; the same notice explicitly declines to guarantee absolute security. These are useful governance statements, not an independent control audit. Underwriting should therefore request current audit reports, subprocessor and residency mappings, incident and uptime history, recovery test results, and architecture-specific performance data. The product appears broad and technically coherent, but confidence in mission-critical maturity should remain conditional on workload-level proof rather than feature availability or marketing certifications alone.[CE009, CE014, CE015, CE016]

5.5 Exhibits

6.1 A self-serve core with a project-level enterprise tail

The clearest independent segmentation signal is a web-technology dataset, not a customer ledger. TechnologyChecker detected Supabase on 19,361 domains in its August 2026 reading and matched 12,450 of those domains to company records. Within the employee-resolved subset, 69.4% belonged to organizations with 1-10 employees, indicating a large long tail of founders, small teams, and agency-built projects. The same dataset found a broad geographic and vertical spread, while warning that recognizable enterprises commonly appeared on a single community site, portal, or microsite. The likely buyer therefore ranges from an individual developer to a departmental innovation lead; the end user may be a developer, an internal builder, or an app's customer, and the budget owner is not observable from public detections.[CU001, CU002, CU003, CU004, CU005, CU007]

6.2 Strong adoption signals, but incompatible denominators

Adoption appears substantial across two different lenses that must not be combined into a single funnel. TechnologyChecker's 19,361-domain reading measures detectable web implementations and explicitly attributes much of the apparent monthly increase to wider signal coverage, not platform growth. TechCrunch separately reported Supabase's company claim of nearly 10 million developers and more than 600% year-over-year growth in database launches, with more than 60% of launches initiated by an AI tool. Domains, matched organizations, developers, and database launches are different populations; none reveals active paid accounts, utilization, revenue, or retention. Vercel co-occurrence and Supabase's code-first agent tooling nevertheless suggest that frontend platforms and AI builders are important adoption surfaces.[CU001, CU002, CU006, CU013, CU014, CU015]

6.3 Named references demonstrate production use, not portfolio quality

Supabase's homepage provides concrete but company-curated reference points. It says Lovable powers millions of AI-generated apps with Supabase, eXp Realty enables more than 2,000 employees to build production software, Phoenix Energy migrated critical infrastructure from MongoDB with zero downtime, and Chatbase scaled its own business to $10 million of ARR on one Postgres-backed platform. TechCrunch independently names Lovable among products choosing Supabase, strengthening identification but not auditing Supabase's claimed scale or customer outcomes. These examples show varied use cases and credible production intent; they do not disclose contract value, tenure, renewal behavior, support burden, or what share of each customer's stack and workload Supabase serves.[CU008, CU009, CU010, CU011, CU012]

6.4 Commercial durability remains the decisive evidence gap

Public evidence does not support a retention or concentration conclusion. No assigned source reports NRR, GRR, logo or revenue churn, cohort retention, renewal rates, average contract length, expansion revenue, paid conversion, customer acquisition cost, or top-customer revenue share. Competitor-authored comparisons identify genuine adoption friction around SQL expertise, setup, debugging, scaling costs, and workload fit, but those sources have commercial incentives and cannot quantify realized churn. The investment case should therefore treat broad adoption and strong named references as top-of-funnel and production proof, not as evidence of durable monetization. Closing this gap requires private cohort schedules, customer-level revenue concentration, renewal data, and reference calls spanning self-serve, Team, and Enterprise customers.[CU016]

6.5 Exhibits

7.1 Risk posture and thesis-break conditions

The risk profile is asymmetric: strong developer adoption and a familiar Postgres core lower product-adoption risk, but rapid AI-assisted creation expands the population of inexperienced operators who can misconfigure access controls. The most decision-relevant monitor is therefore not raw database launches; it is the rate and severity of exposed projects, time to customer notification and remediation, and whether safer defaults reduce recurring incidents. The thesis should be paused if material exposures continue without measurable reduction, if a primary-database bottleneck causes repeated production failures, or if commercial conversion and durable workloads do not support the expectations embedded in the June 2026 financing. The matrix is a qualitative prioritization rather than a measured probability model.[CR001, CR002, CR011, CR013, CR014]

7.2 Security, privacy, and legal exposure

UpGuard's reported exposure finding is evidence of a real ecosystem-level failure mode, but it is not proof that Supabase itself was breached or that all affected projects shared one root cause. Supabase says projects are secure by default and assigns configuration responsibility to customers; that allocation does not eliminate reputational, support, or regulatory spillover when hosted applications expose personal data. The privacy notice distinguishes Supabase's controller role for account data from its processor role for Customer Data and describes international transfers and subprocessors. Diligence should obtain the exposure methodology, affected-project denominator, incident chronology, default-policy changes, notification service levels, DPA and SCC package, and current independent assurance reports before treating legal and control maturity as fully verified.[CR001, CR002, CR003, CR004, CR005, CR006, CR007, CR015]

7.3 Operational resilience and product execution

Managed Supabase reduces infrastructure assembly work, but it does not remove database engineering. Independent analysis describes a conventional project as centered on one primary Postgres database: replicas distribute reads, while writes still converge on the primary. Multigres was characterized as alpha and not production-ready as of September 2026, so it should not be underwritten as a current solution to horizontal write scaling. Reviews also identify 200-400 millisecond Edge Function cold starts, absent native analytics, queues and advanced caching, and limited immediate support channels. These are workload-dependent constraints rather than universal defects. Confirmed recovery tests, customer-specific RPO/RTO evidence, saturation thresholds, escalation response times and a production Multigres roadmap are the appropriate underwriting evidence.[CR003, CR008, CR009, CR010, CR011, CR012]

7.4 Partner, financial, and model dependencies

Supabase's privacy disclosures name a broad operating chain that includes cloud, edge, payments, communications, analytics and AI providers. The list establishes dependency breadth but not spend concentration, contractual substitution rights, correlated-failure exposure or recovery times. The model also relies on converting open-source and AI-generated adoption into persistent paid workloads. TechCrunch reported a $500 million Series F at a $10 billion pre-money valuation, while TechCrunch and Nexuswild repeat company-reported acceleration in database activity. Funding raised is not cash available, launch growth is not revenue, and public evidence does not disclose audited unit economics. Investment diligence should require vendor concentration, SLA and exit-plan data plus cohort conversion, retention, gross margin, burn and workload-quality metrics.[CR013, CR014, CR016]

8.1 Recommendation and price discipline

The recommendation is track/research-more, with medium-low confidence and high valuation risk. The positive case is unusually strong adoption momentum: company-issued material reported more than 250,000 customers, and independent coverage reported database launches up more than 600% year over year and nearly 10 million developers. The product also spans database, authentication, storage, edge functions, realtime, and vector capabilities while retaining an open-source posture. The counterweight is price. The June 2026 mark remains the latest explicit valuation anchor because the October financing did not publish a new price, but current revenue was withheld and no audited ARR, retention, margin, burn, or cash evidence appears in the assigned public record. Entry should therefore be conditional on private operating evidence and terms, not on the headline usage metrics alone.[CV001, CV007, CV008, CV009, CV011, CV014, CV016]

8.2 Financing context and capital-structure overhang

The June round was reported as $500 million at $10 billion pre-money and $10.5 billion post-money, following a $100 million Series E at a $5 billion valuation. In October, Supabase disclosed another $150 million financing alongside the Turso acquisition, but the acquisition consideration and October valuation were not disclosed. The latest round also included employee liquidity without quantifying the primary-versus- secondary split, so funding raised cannot be treated as cash available. Forge lists a 1.0x, non-participating preference for the displayed Series F classes, but a full cap table, all seniority layers, option dilution, secondary transfers, and acquisition consideration require primary diligence. Public totals also differ by provider and round convention, making the capitalization table—not an aggregator total—the proper source of truth.[CV001, CV002, CV003, CV004, CV005, CV006, CV010, CV013]

8.3 Scenario framing and comparable discipline

The scenario bands use the disclosed $5 billion and $10.5 billion private financing marks as decision anchors, not intrinsic-value estimates. A bull outcome requires audited paid conversion, durable enterprise retention, attractive gross margins, and a credible liquidity path before any value above the latest mark is supportable. The base case is continued operating progress but insufficient public economics, which favors waiting or negotiating materially better protection. The bear case is conversion weakness, support or infrastructure costs that outrun revenue, multiple compression, or acquisition integration risk, potentially returning valuation below the earlier $5 billion mark. No revenue multiple, public-company multiple, or M&A multiple is defensible from the assigned evidence because current revenue and the Turso consideration are undisclosed.[CV001, CV005, CV008, CV010, CV011, CV015, CV016]

8.4 Exit readiness, diligence asks, and thesis-break triggers

Financing access is strong, but exit readiness is unproven. Forge labels market activity as limited and shows no available Forge price, while the evidence contains no IPO filing, audited public financials, or reliable secondary-market clearing price. Before investment, diligence should reconcile the fully diluted cap table; primary and secondary proceeds; all liquidation preferences; ARR and recognized revenue; cohort retention; gross margin by workload; cloud and support cost; burn and cash; customer concentration; and Turso purchase and integration terms. Thesis-break triggers are a down round, material deterioration in paid conversion or retention, persistent gross-margin compression, acquisition integration failure, or evidence that database creation growth does not translate into retained paid workloads. A verified liquidity path or a sufficiently protected entry price could improve the recommendation.[CV005, CV006, CV011, CV012, CV013, CV015, CV016]

8.5 Exhibits