Select is a curated day of talks by @Supabase and the industry's best builders. It will take place on October 2nd, in San Francisco, CA.

If you've been building on Supabase (or thinking about it), this is where you see what's next first and where you meet their team.

Supabase just hit 100,000 GitHub Stars. They also announced 8,000,000 developers building with Supabase.

This year again, Supabase surveyed 2,000+ startup founders to uncover what's powering modern startups: their stacks, their GTM motion, and how they approach AI.

Many things have changed between 2025 and 2026.

The funds will boost open-source / Postgres tools, grow the platform, and liquidity for the employees.

Two months ago, @Supabase announced 8,000,000 developers building with the platform. [1] They're now nearly 10 million, with databases launches growing by 600% over the past year.

One recurring issue we ve been seeing with Supabase setups is not the database itself, but how credentials are managed across environments. The common pattern looks something like:

• credentials stored in .env files or secrets managers

• multiple environments (dev, staging, prod)

• manual propagation or duplication across those environments

It works, but over time it seems easy for things to drift:

• a key gets rotated in one environment but not others

• a redeploy misses an env var

• credentials get misconfigured during setup or migration

Some metrics shared by @copple on X:

There's never been a better time to build. AI tools, smaller teams, faster product cycles.

Last year, @Supabase surveyed over 2,000 startup founders and builders to uncover what's powering modern startups: tech stacks, GTM, and approach to AI.

Many things have changed since then, and they want to know what building at startups looks like in 2026.

Supabase recently surveyed over 2,000 startup founders and builders to uncover what's powering modern startups: tech stacks, GTM, and approach to AI.

See full report here