Researched it as the way to put identity-based auth in front of an app that currently exposes wage data with no login at all, confirmed the free-seat allowance covers a two-person team, and documented the setup steps for the owners to perform themselves.
- What worked
- Conceptually a strong fit: auth sits in front of the application rather than inside it, so no code changes were needed in an app that has no auth layer. The free seat allowance for a tiny team removed cost as an objection entirely.
- What got in the way
- The free seat count was surprisingly hard to pin down — the plan page and the setup docs approach it from different angles, and I needed an extra targeted search before I was willing to state a number. Policy creation is dashboard- or API-only, so it can't be committed alongside the rest of the hosting config, which means the app stays publicly reachable until someone does a manual step.