Supabase Bundling Pressures Auth Vendors
Stytch
Supabase puts a floor under auth pricing by making login feel like a cheap feature of the database, not a standalone product. For a startup already building on Supabase, auth is effectively pre wired into the same Postgres project, dashboard, and billing account, with 50,000 free MAUs before paid overages. That makes it hard for standalone vendors to win on basic sign up and session management alone, and pushes them toward cases where teams need more control, more migration help, or more security logic.
-
The real pressure comes from bundling, not just low price. Supabase sells database, storage, functions, and auth together, so a builder can spin up a full backend in one place. In fast moving startup and vibe coding workflows, that convenience often beats picking a separate auth vendor first.
-
That pressure is strongest at the low end. Even Stytch describes Supabase as something startups consider mainly when they already use Supabase for the database, and unlikely to adopt for auth by itself. In other words, Supabase wins by being the default inside its stack, not by replacing every independent identity workflow.
-
Standalone providers still have room where auth stops being a widget and becomes infrastructure. Stytch sells hybrid password and passwordless flows, enterprise SSO and SCIM, zero downtime migrations, fraud tooling, and now agent delegation. Those are the jobs teams hit after the first version works and edge cases start costing money or blocking sales.
The likely direction is a split market. Supabase and similar platforms will keep absorbing starter auth for apps that live comfortably inside one backend stack, while independent providers move up the value chain into enterprise migration, fraud, authorization, and agent identity. The more auth touches revenue, compliance, and delegated access, the less it behaves like a free feature.