Companies that use Supabase

Source: Analysis of job postings that mention Supabase (using the Bloomberry Jobs API)

I noticed that Supabase purchasing decisions are primarily driven by engineering leadership, with 17% of roles being VP or Head of Engineering positions. These leaders are hiring for rapid growth and AI-first transformation. They prioritize building teams that can ship fast with modern stacks, often mentioning the need to scale from MVP to production-ready platforms. Backend engineers (23%) and full stack engineers (19%) represent the core buying influence, particularly those building AI-powered applications and serverless architectures.

The day-to-day users are predominantly full stack and backend developers working across web applications, APIs, and data-heavy interfaces. I found extensive use of Supabase alongside modern JavaScript frameworks like Next.js and React, with PostgreSQL database management being a common thread. Developers are building everything from authentication systems and real-time features to AI agent workflows and microservices architectures. Many roles emphasize AI-assisted development using tools like Cursor and Claude Code.

The pain points center on speed and autonomy. Companies want to "build systems that run the business" and "ship at lightning speed" while maintaining "technological independence." One posting seeks someone who can "turn ideas into production-ready products at startup speed," while another needs "extreme ownership" to "scale without adding headcount." Multiple roles emphasize eliminating SaaS subscriptions by building custom solutions in-house, suggesting Supabase appeals to teams seeking control and rapid iteration over vendor dependence.

Source: Analysis of Linkedin bios of 1,105 companies that use Supabase

I noticed that Supabase users are predominantly builders of digital products and platforms. These companies create SaaS tools, AI-powered applications, marketplaces, community platforms, and workflow automation systems. Many are developing customer-facing software that requires user authentication, real-time data, and content management. I see consulting platforms like Markopolo, AI chatbot builders like Chatbase, scheduling tools like skedAI, and content engines like Catalyst Content. They're not just using software, they're shipping it.

These are overwhelmingly early-stage companies. The vast majority have between 2-50 employees, with funding stages conspicuously blank across the dataset. Very few mention Series A or beyond. I see teams that describe themselves as "small," companies recently founded (Plant Futures "founded in 2008" but still growing, Tesla MR launched recently), and organizations still defining their market position. The ambitious bios combined with small team sizes signal pre-product-market fit or early traction phases.

Source: Analysis of tech stacks from 1,105 companies that use Supabase

I noticed that Supabase users overwhelmingly favor tools built for speed, community, and self-service. The dominant presence of Posthog (appearing at 150x+ higher rates across multiple features) combined with Framer and Discord tells me these are product-led companies that move fast, iterate constantly, and build in public. They're not buying enterprise software suites. They're assembling modern, developer-friendly stacks that let small teams punch above their weight.

The Posthog and Supabase pairing makes perfect sense for teams that want to own their data. Both are open-source alternatives to proprietary tools, and both let you self-host if needed. When I see Framer in the mix at 78x the normal rate, it confirms these companies prioritize shipping quickly. Framer lets non-developers build production-ready sites, while Supabase gives them a backend in minutes. The Discord correlation is particularly telling. These companies aren't hiding behind support tickets. They're building communities, getting direct user feedback, and probably have their engineering team actively talking to customers in channels.

The full stack screams product-led growth. These companies are building for developers or technical users who evaluate tools themselves rather than going through procurement. They're likely early to mid-stage startups that haven't built out large sales teams yet. The emphasis on analytics (all those Posthog features, including session recording and feature flags) shows they're running experiments, watching user behavior closely, and making data-driven decisions about what to build next.