EnglishPolski
No results found.

WolfieAuth — Build a SaaS in 5 minutes

Hosted SSO, multi-org tenancy, per-seat plans, RBAC, comp overrides. Drop-in via SDK. Stop rebuilding auth.

Build a modern SaaS in 5 minutes

You shouldn’t be writing login forms in 2026. WolfieAuth gives you the entire identity + billing + RBAC backbone of a serious SaaS, and your app talks to it via standard OIDC plus a thin SDK helper. Pick your stack from the catalog below and you’re shipping by lunch.

What you get out of the box

  • Hosted login + signup — branded per-app, magic-link / password / social, password reset, MFA / passkeys, account recovery.
  • Multi-org tenancy — every user belongs to one or more organizations, hard isolation between them, cross-org SSO when invited.
  • Per-app + per-bundle plans — flat / per-seat / volume-tiered, multi-currency, country-specific pricing, free comp overrides.
  • RBAC out of the box — five canonical SaaS templates (Solo, B2B Team, B2B Hierarchical, Marketplace, Internal Tool), one-click apply.
  • Stripe Connect — money flows to each customer org’s connected account; platform takes a 5% fee tracked locally and KSeF-invoiced monthly.
  • Per-org MCP — each customer admin can drive their own org’s settings through a sandboxed MCP token. Cannot touch other orgs by design.
  • Webhooks, audit, anomaly detection, GDPR exports, SAML/SCIM — already implemented; you don’t have to.
[your app] ──login──▶ auth.wolfieguard.com  ──┐
                                              │  PKCE OIDC
[your app] ◀─claims─ id_token + userinfo  ◀──┘
   │
   └─▶ {sub, email, name, role, wolfieauth_org_id, wolfieauth_plans[],
        wolfieauth_features[], wolfieauth_permissions[], …}

That’s the whole API. Everything else is a UI you can also drive yourself if you want.

The “5-minute SaaS” recipe

1. Register an OidcClient at auth.wolfieguard.com/admin/clients/new
   → get client_id (auto-prefixed: <orgSlug>-<myapp>) + client_secret

2. /admin/clients/<id>#users → Roles → "📋 Use template"
   → pick the SaaS shape that fits (B2B Team, Marketplace, …)

3. /admin/clients/<id>#plans → New plan
   → optional per-seat pricing, 3 free seats, $5/seat after

4. In your app:
   $ npm install @wolfieauth/sdk-sveltekit  (or sdk-react / -laravel / -sylius)
   $ paste 8 lines of config into hooks.server.ts

5. Done. Login + plans + RBAC + audit + comp overrides all work.

Continue reading

  • Getting Started — register your first app, wire the SDK, watch a user log in.
  • SDKs — the 14 framework adapters and their helpers.
  • Integrations — drop WolfieAuth into a WordPress site, Perfex CRM, or Laravel app.
  • SSO & Sessions — how the cookie + token flow actually works under the hood.
  • Plans & Billing — per-app / per-bundle / per-seat / tiered / multi-currency.
  • Admin Panel — Theme, Users, Roles, Plans, Comp overrides, MCP tokens.

Why a hosted auth provider?

You can roll your own auth — many do. But you’ll spend the next 18 months rebuilding password reset, email verification, magic links, social OAuth, MFA, passkeys, GDPR exports, audit logs, plan checkout, Stripe Connect, KSeF invoices, and per-org isolation. WolfieAuth is what you get if a small team has already done all of that, and lets you wire your downstream app with 8 lines of code.

The core invariant: WolfieAuth is your user table. Don’t keep a parallel users table in your app DB. Store userId = sub everywhere, refresh metadata from /userinfo when needed. This eliminates an entire class of stale-record bugs.

Production: auth.wolfieguard.com Admin panel: auth.wolfieguard.com/admin Source: gitlab.com/pw-other/wolfieauth