B2B SaaS that sells to companies
Your customers are teams inside companies. Sooner or later an IT department asks for SSO, audit trails and invoices, and a lost email or an outage costs you a contract.
11 makers' products and 15 open-source projects use at least half of these 9 tools.The picks
The framework most B2B SaaS starters and enterprise auth SDKs target first.
Chosen for frontend framework by 1506 makers' products we track · the alternatives →SAML SSO and SCIM directory sync, the two things enterprise buyers ask for, as a service — with sign-in for small teams on the free tier.
Chosen for authentication by 19 makers' products we track · the alternatives →Managed Postgres with branching, so every preview and migration test gets its own copy of the schema.
Chosen for database by 95 makers' products we track · the alternatives →One schema file, typed queries and reviewable migrations — useful when a second developer joins.
Chosen for database access & ORMs by 37 makers' products we track · the alternatives →Invoices, seats, purchase orders and tax IDs — the billing features company buyers expect.
Chosen for payments by 869 makers' products we track · the alternatives →Transactional-only sending with fast, reliable delivery, so password resets and invites don't land in a corporate spam filter.
Chosen for transactional email by 612 makers' products we track · the alternatives →Reliable multi-step work — imports, syncs, scheduled reports — with retries and a history you can show support.
Chosen for background jobs & cron by 16 makers' products we track · the alternatives →Errors tied to the customer and release, so you can answer "is it fixed?" when an account manager asks.
Chosen for error monitoring by 162 makers' products we track · the alternatives →What this costs you
Enterprise-ready pieces cost more from day one — WorkOS charges per SSO connection, Postmark's free plan is small. If your first customers are small teams, start with Clerk or Better Auth and add WorkOS when the first SSO request arrives with a contract.
Who builds this way
Using at least half of these tools, each with a source: makers' products from their own words, customer stories, subprocessor lists or websites; open-source projects from their code.