Onboard businesses into your SaaS
Let customers use local accounts or their own identity provider. Build tenant configuration into your onboarding tools and keep a common integration in your application.
Explore B2B customer onboardingSovereign identity for your organisation
Own Your Identity Platform
Run identity on infrastructure you choose. Keep control of your identity data. Connect employees, partners and customers to your applications with a platform you can operate and move as your infrastructure strategy evolves.
Self-hosted · OpenID Connect & OAuth · Supported by 4tecture
Your platform. Your infrastructure.
Under your operational control
- OpenID Connect 1.0
- OAuth 2.0
- FAPI 2.0
- FIDO2 / WebAuthn
FAPI 2.0 Security Profile: opt-in.
Choose where it runs
Different environments. Your identity platform.
For internal systems, software products and digital services, keep identity aligned with the way your organisation operates.
Bring identity into your business applications
Connect business applications to a maintained identity platform. Combine enterprise federation and local accounts in one deployment, with control over integration and branding.
Explore business application identityRun identity on infrastructure you choose
Deploy on premises, in a private cloud or with your chosen public-cloud provider. Keep control of identity data and plan hosting changes on a supported Kubernetes foundation.
Explore deployment controlKeep sign-in available offline
Run identity on site for applications that need local sign-in. Keep accounts and required services within the local environment.
Explore local and offline sign-inSovereignty means keeping your choices.
Decide where the platform runs, retain control of its data and choose how it is operated. ProAuth gives those decisions a concrete technical foundation.
Choose where identity runs
Deploy ProAuth on your own infrastructure, in a private cloud or with your chosen public-cloud provider. Container delivery and Kubernetes tooling support a consistent deployment approach across those environments.
Review deployment requirementsTake your platform and data with you
Keep control of ProAuth configuration, user-store databases and encryption keys. When you change hosting providers, these form the basis of a planned platform move, with documented backup and recovery procedures.
See how platform data is preservedKnow who supports the product
4tecture develops ProAuth and provides product support. Basic support covers product defects; escalation packs and Enterprise support plans add configuration and integration assistance.
See support scope and response timesOne identity platform for the applications you rely on.
Connect internal systems, workforce applications and customer-facing services through OpenID Connect and OAuth. ProAuth can use its own user stores or federate sign-in to existing providers such as Microsoft Entra ID.
Your applicationsInternal · partner · customer
OIDC / OAuth
Your ProAuth deployment
Sign-in · tenants · token issuanceProAuth user storesSQL Server / Azure SQL or PostgreSQL
OIDC federation
Existing identity providersEntra ID · other OIDC providers
Need customer-specific login views, Claims Rule Engine, audit trails or SCIM provisioning? These are Enterprise features.
Compare ProAuth editionsFor advanced API requirements, FAPI 2.0 is opt-in. DPoP and mTLS token binding require the corresponding client and API integration.
Explore security controlsWhat integration can look like
ProAuth customer projects inform these implementation patterns. Explore how teams make identity part of their product and operating model.
Identity inside the product experience
Deployment tooling configures ProAuth, while the product uses its APIs for user administration.
Explore this implementation pattern: Identity inside the product experienceCustomer choices built into onboarding
A customer-built wizard collects identity requirements and applies tenant configuration through the Management API.
Explore this implementation pattern: Customer choices built into onboardingLocal sign-in under local control
Local identity sources and services support applications with offline sign-in requirements.
Explore this implementation pattern: Local sign-in under local controlYour platform. Clear responsibilities.
Evaluate one representative application and identity source. Decide where ProAuth runs, who operates it and how you retain control as requirements change.
Map your environment
Identify workforce, partner and customer applications, identity sources and required claims. Assess existing accounts, credential formats and MFA enrolments before planning a migration.
Validate a working integration
Configure a tenant, connect an application and test sign-in, permissions and recovery. Confirm the edition features and infrastructure your setup needs.
Prepare to operate and evolve
Assign monitoring, backups and upgrade testing. For a hosting move, plan the identity endpoint, certificates, dependencies and licence scope. Agree any managed operation separately.
Choose the edition
Check feature entitlements and limits for applications, user stores and federated providers.
Compare Starter, Business and EnterprisePlan the licence budget
Starter and Business are annual subscriptions. Enterprise also offers perpetual licensing. Infrastructure, implementation and operation have their own costs.
See licence prices and terms