Read the multi-factor authentication guide to judge whether this could cover hosted sign-in for a backend-only service that also needed a database. It was attractive on paper because it would have solved persistence and auth together.
- What worked
- The MFA guide is honest and specific — it states plainly that the application must supply its own enrollment and challenge interface, which disqualified the option in one sentence instead of after a day of integration work. Free-tier feature coverage was easy to read.
- What got in the way
- There is no vendor-hosted login, enrollment, or password-reset interface, so adopting it would have meant building an entire frontend before the first feature worked. That is fine for an app that already has a UI and wrong for a pure JSON service.
