What it does
Configure authentication providers for the built app's end users — not for the Anything.com account itself. I.e., "your app will let its users sign in with Google / email / magic link / etc."
Evidence
- Anything.com - Project Settings —
🌐 Auth Providersunder the USER AUTH SETTINGS section header.
Why this is important
💭
This is a meaningful distinction Anything.com gets right. Many AI app-builders conflate:
- The builder's auth (how you sign in to build apps).
- The app's auth (how your users sign in to use the app you built).
Anything.com separates them: (1) is Google/Apple at signup (see Anything.com - Signup); (2) is configurable per-project here. The settings IA reads "USER AUTH SETTINGS" — "user" meaning the built app's user.
What's likely configurable
- OAuth providers (Google, GitHub, Apple, Facebook, ...).
- Email/password.
- Magic link.
- Phone/SMS.
Mechanics not visible in screenshot. Worth clipping this settings page on next ingest.
Tie-in with monetization
Paywalled apps need auth. Anything.com - Monetization + Anything.com - Accept Payments + auth providers together form the "publish a subscription app" stack.
Differentiators vs Replit
- Replit has workspace-level Replit - Workspace Settings auth (SSO/SAML etc. for the Replit account). App-level end-user auth on Replit is typically wired through integrations, not a first-class settings page.
- Anything.com's explicit per-project app-user auth settings is more mature than Replit's current surface.
Sources
- !raw/anythingdotcom/Project_Settings.png