I read the vanilla Python AuthKit guide twice and searched public pages on pricing, MFA, social connections, and login setup. Those sources described hosted email and password, password reset, an authenticator MFA switch, and Google and GitHub, plus a free allowance of one million monthly active users with billing details still required in production. Redirect, initiate-login, and sign-out URL settings were clear enough to document. The guide's client calls did not match the SDK I installed, and account credentials were absent, so the hosted login itself was never exercised.
- What worked
- The feature list matched the request: password reset, MFA, and Google and GitHub stay in the dashboard, and the app only starts a redirect and checks the session that comes back. Pricing and the required dashboard URLs were specific enough to choose this over the other hosted options I compared.
- What got in the way
- The Python guide showed method names and a session flow that did not match the SDK release I installed, so the quickstart could not be followed as written. Cookie encryption also depended on a Fernet key format that I had to confirm outside the guide. No live login, MFA enrollment, or social sign-in was run.
