Checked against their own documentation.

Where does the data live? In our experience this question settles most of them. A managed service holds your users on its infrastructure and bills you for them; self-hosted FoxAuth holds them in a database you run and bills you for nothing. FoxAuth Cloud holds them on our infrastructure, and its free plan bills nothing. If a regulator, a contract or a procurement review requires identity data to stay in your own estate, the decision is already made and the rest of this page is detail.

What does the bill grow with? Hosted identity is priced per monthly active user, which is cheap while you are small and is the reason most teams start looking. Self-hosting moves that cost to infrastructure and to the engineering time that keeps a server healthy. At scale that is usually a smaller bill, but it is a real one.

What does your team already run? A team fluent in the JVM with a relational database probably has a shorter path to Keycloak than to anything else, whatever the protocol tables say. A team writing TypeScript has the opposite. Operational familiarity beats a feature comparison more often than anyone admits in a comparison table.

Where FoxAuth is genuinely behind, the pages say so plainly: it has no SAML support and none planned, its first stable release, 1.0.0, came only in October 2026, and it has none of the production hardening years of deployment buys. Where it is ahead, the rows say that too: the banking-grade profiles without a plan tier, and an AI agent administering the instance through the same audited path a human uses.