Loading page…
A passwordless authentication SDK serving banks, e-commerce companies, and crypto exchanges at more than $130K in monthly revenue.
56M authentications/mo · 41 enterprise customers · 320+ paying customers
Passwordless infrastructure becomes sticky when it is embedded in a customer's login flow, but the acquisition advantage starts with developers who can try the SDK before a bank or marketplace signs the contract.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
SAWO Labs provides a passwordless authentication SDK that plugs into mobile and web applications. Its customers use it to authenticate users for cryptocurrency exchanges, e-commerce businesses, and a large bank. Founder Prabhat Sahu says the company handles 56 million authentications per month and charges $0.006 per authentication, with enterprise ticket sizes described as $10,000 to $12,000 per month or year in a garbled exchange. The business had 41 enterprise customers, additional smaller accounts paying from $18 to $100, around 9,000 total users, and more than 320 paying customers. Sahu reports monthly revenue of over $130,000, about $1M of capital raised, a planned $9M round, and a $65M valuation already closed on paper. The team grew to 53 people, 49 full-time, including 34 engineers. Customer acquisition began with a developer community: about 80 developers became 12,000, with little paid spend. The founder reports barely 0.3% churn and says product-led and community-led growth are central. The figures are founder statements and include a transcript inconsistency around per-authentication pricing.
For SAWO, the first customers came after developers had a reason to experiment with authentication before enterprise procurement began. Start with a working SDK, clear integration docs, and a sandbox that lets a developer add passwordless login to a real mobile or web flow.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Founder interview with host repetition; revenue, authentication volume, customer counts, team size, churn, fundraising, and valuation are founder-reported and unaudited. The transcript states $0.006 per authentication but later contains a garbled $0.06 repetition, and enterprise ticket-size units are unclear.
SAWO's first dollars came from usage-based authentication, with enterprise accounts paying for high-volume production traffic and smaller customers paying lower ticket sizes.
SAWO's flywheel started with developers, not with the enterprise brands that eventually paid the largest bills. An open community attracted people interested in product-led growth and authentication.
Authentication products can go quiet before they go large because a developer may test an SDK long before a company approves production use.
SAWO Labs is an authentication infrastructure layer delivered through an SDK. A customer integrates it into a mobile or web application so end users can authenticate without traditional passwords or one-time codes. The product includes client libraries, APIs, user enrollment, authentication events, session handling, recovery, and an operational dashboard. Its target accounts are high-volume digital businesses such as cryptocurrency exchanges, e-commerce platforms, and banks. The core engineering challenge is not the login screen; it is security, reliability, latency, abuse resistance, migration, observability, and a developer experience that makes the safe path the easiest path. An MVP should support one passwordless method, clear environment separation, test credentials, webhooks, usage metering, and production logs. Enterprise features such as roles, audit history, data residency, service-level commitments, and dedicated support can follow the first reliable deployment. The stated 56 million monthly authentications show why usage-based infrastructure needs careful metering and capacity planning. Keep authentication decisions deterministic and auditable; use automation to help operators investigate, not to obscure why a user was accepted or rejected.
SAWO monetizes authentication volume. The founder reports a charge of $0.006 per authentication, 41 enterprise customers, smaller accounts paying from $18 to $100, and monthly revenue above $130,000. The interview also describes enterprise ticket sizes as $10,000 to $12,000 per month or year, but the exchange is unclear, so pricing should not be normalized beyond the stated figures. A practical model has a free developer sandbox, a metered production plan, and enterprise contracts with volume commitments, security controls, support, and service-level terms. Bill on verified authentication events and show a usage ledger that both finance and engineering can reconcile. The product's gross margin depends on infrastructure, messaging, fraud prevention, support, and any external identity or delivery costs. Expansion can come from higher authentication volume, more applications, stronger compliance, and adjacent identity workflows. The reported 320-plus paying customers and 56 million monthly events suggest a broad base beneath the enterprise accounts, but the company must track revenue concentration, failed events, chargebacks, churn, net retention, and cost per successful authentication. Clear metering is part of trust, not merely billing.
SAWO's distribution model is developer-led community growth followed by enterprise conversion. The founder says the company brought developers and product managers together, gave them value, and let the product enter daily habits before targeting banks and e-commerce brands directly. Slack and Discord support that approach because implementation questions, examples, and peer recommendations travel quickly among technical users. Build framework tutorials, sample applications, migration guides, security explainers, and a local test environment. Give developers a real but bounded free path, then identify teams whose traffic or risk profile justifies a production conversation. Enterprise sales should use the developer champion as a guide while adding security, finance, and procurement materials for the buying committee. Track community activation, SDK installs, first successful authentication, production deployment, monthly events, support tickets, enterprise pipeline, and conversion by integration source. The founder reports very little paid acquisition spend, but organic community growth is slower than paid reach. Keep the education engine strong while using targeted partnerships with cloud platforms, agencies, and developer communities to reach the right technical audience.
Build SAWO as a security-first API and SDK platform. Use Next.js App Router with TypeScript and Tailwind for the developer console, Clerk for internal dashboard access, Neon Postgres with Drizzle for organizations, applications, users, credentials, events, usage, and billing, Stripe for subscriptions and metered billing, and Vercel for the console. Production authentication services should run in isolated, observable services with secrets management, rate limiting, key rotation, encrypted data, replay protection, audit logs, and regional controls. Data model: organizations, applications, environments, endUsers, authenticationMethods, sessions, events, webhooks, usageBuckets, invoices, supportCases, and auditEvents. Provide SDKs with versioning, typed errors, test credentials, local development instructions, and migration helpers. The main costs are reliable compute, event storage, security work, support, messaging or delivery providers, compliance, and incident response. Do not use an AI model to decide identity or access. Add AI only for documentation search, support triage, or operator summaries with strict redaction. The reported 53-person team and 34 engineers show that enterprise authentication requires more operational depth than a thin API wrapper.
Copy SAWO's developer-first entry point, community-led distribution, usage-based pricing logic, and focus on a painful infrastructure layer that becomes sticky after integration. Copy the decision to bring developers and product managers into the community before asking banks or marketplaces to buy. Change the evidence discipline. The transcript contains strong founder-reported numbers, but the authentication unit price and enterprise ticket-size exchange is inconsistent, so every future version needs a transparent usage ledger and a clean pricing page. Change the fundraising posture for a smaller entrant as well: prove one framework, one passwordless flow, and one production use case before building a 53-person organization. Treat security, incident response, and compliance as part of the product rather than enterprise paperwork added later. The opportunity is attractive because a successful authentication layer can expand with customer volume and applications. The danger is that a single security incident, billing surprise, or unreliable recovery path can erase years of trust. Build the community and the control plane together.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click