Auth & Identity
by @ops Go + Postgres + Redis: Social Login Aggregator / Identity Broker
Unifies multiple OAuth providers behind one identity record — distinct from the basic Auth/SSO starter: this specifically handles linking several social logins to a single account and reconciling identity across them.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install go-social-login-identity-broker --remote $ stacktora sync # generate the files
What you get
More from the Vault
Auth / SSO starter
Session-based auth with OAuth-ready config — Postgres for users, Redis for sessions. The starting point every team currently has to build from scratch.
Java (Spring) + Postgres: SCIM Provisioning & Enterprise Directory Sync
Automatic user provisioning/deprovisioning via SCIM, a worker syncing against an enterprise identity provider — the real enterprise-B2B requirement most SaaS auth starters skip entirely: when an employee leaves, access needs to disappear without a support ticket.
Passwordless / MFA Auth Starter
WebAuthn/passkey and TOTP-ready authentication, not just sessions — a genuinely different pattern than a basic login/SSO starter, for teams building auth people actually expect in 2026: no password to leak, a second factor by default.
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.