European identity infrastructure
Secure every application without giving up control
FoxIDs is an identity platform for teams that need open standards, European hosting, and the freedom to run cloud, self-hosted, or hybrid without forcing a separate product for every use case.
- Choose FoxIDs Cloud, self-hosted, or hybrid deployment.
- Integrate OpenID Connect, OAuth 2.0, and SAML 2.0 across modern stacks.
- Use one platform across customers, employees, partners, APIs, and AI workloads.
Trusted by organisations across Europe,
and the rest of the world
Why teams choose FoxIDs
Focus on the platform decisions that matter most: control, compliance, cost, and implementation speed.
Deployment Flexibility Without Lock-In
Choose cloud, self-hosted, or hybrid while keeping control of infrastructure, data, and architecture.
EU-First and Compliance
Built for European regulations, data protection, and sovereignty by design.
Low Cost and Predictable Pricing
Consumption-based pricing keeps identity costs predictable as you scale.
Complex Logic - Simple Implementation
Configure advanced authentication flows, claims, and policies without complex custom development.
Multi-Tenant Identity Architecture
Scale securely across tenants with isolation, flexibility, and control.
One Platform, Every Use Case
Use one identity engine across B2C, B2E, and B2B scenarios.
One platform across providers and applications
Connect identity providers, user populations, applications, and APIs with open standards.
Bring external identity providers, modern applications, and multiple user types together in one platform instead of stitching separate products together.
Identity Providers
- Enterprise Identity: Microsoft Entra ID, AD FS, Okta, Google Workspace, Ping Identity, Auth0
- Social & Public: Google, Facebook, LinkedIn, National IdPs
- Flexible Federation: Connect with Keycloak and other standard-compliant providers
Key Capabilities
- Bridge between SAML 2.0 and OpenID Connect
- Environment linking
- Customisable built-in login UI
- Advanced Token Exchange features
Relying Applications
- Web Frameworks: ASP.NET Core, Node.js, Java, PHP
- Frontend (SPA): React, Angular, Vue, Blazor WASM
- Mobile Apps: iOS, Android, React Native, .NET MAUI, Ionic
- Backend Services: .NET services, Java, background scripts
- APIs: ASP.NET Core, Node.js, Java, Python, Go
One Platform, Every Use Case
Run customer, employee, and partner access on the same identity engine instead of splitting policy, deployment, and operations across separate tools.
Built and hosted in Europe
The European Alternative
FoxIDs takes a different path from US-first identity platforms: more deployment control, lower lock-in, and an EU-first approach to data protection and operations.
Scalability & Pricing
Consumption-based with a low, predictable total cost of ownership (TCO).
Architecture & Deployment
Multi-tenant, open architecture available as SaaS, self-hosted, or hybrid.
Data Privacy & Compliance
EU-first by design, supporting GDPR compliance by default.
Vendor Lock-in
Minimal lock-in through rigorous adherence to open standards.
AI Assistant Prompt
Built for developers
Use the AI Assistant prompt to plan integrations faster and keep implementation grounded in open standards across the platforms your teams already run.
- Support the languages, frameworks, and platforms your teams already use
- Use one identity platform across web apps, SPAs, mobile apps, APIs, and backend services
- Manage tenants and environments, identity flows, access control, and customisable login experiences
- Give teams a reusable AI Assistant prompt to plan and implement integrations faster
Help me add OpenID Connect support with FoxIDs to my application. Before writing code, ask concise questions to determine the app type, language, framework, hosting model, existing authentication, callback URLs, logout URLs, current settings location, and whether the app is server-based or not. Then implement the integration using these mandatory rules: - Add settings for `Authority` and `ClientId` - If the application is server-based: - add `ClientSecret` - use a session cookie - keep tokens on the server - `PKCE` optional - If the application is not server-based: - do not use `ClientSecret` - use authorisation code flow with `PKCE` - Set response type to `code` - Set scopes to include `openid`, `profile`, `email` - If possible set: - Name claim type to `sub` - Role claim type to `role` - Use `JWT` claims - Prefer validating JWT tokens using OpenID Connect Discovery - If not supported, use the user info endpoint at `Authority + /oauth/userinfo` (authorize and token endpoints at `/oauth/authorize` and `/oauth/token`) - Implement login and log off - Add Log in and Log off buttons - After login, show the claims for debugging and clearly note that this must be deleted later Guardrails: - Do not introduce unrelated refactoring - Do not remove existing features unless strictly required for FoxIDs OIDC integration - Keep home page changes minimal and only add what is needed for Log in, Log off, and debug claims display When done, always: - print the redirect domain or redirect URI to configure in FoxIDs - clearly show exactly where settings are configured - list the files changed - explain any manual steps needed - briefly explain how to add and configure the application in FoxIDs (as an OpenID Connect Application registration) after it has been enabled for OIDC
Customer Success Stories
Discover how organisations are leveraging FoxIDs to solve complex identity challenges and enhance security.
European identity infrastructure
Start with the deployment model that fits your organisation
Start on FoxIDs Cloud or plan a self-hosted rollout with the same platform, open standards, and European trust profile.