Licence and edition advice
Starter and Business are annual subscriptions. Enterprise also offers a perpetual licence. Redistribution or OEM requires a separate agreement.
ProAuth identity provider, with dotNET lab as your Benelux partner
A new customer, more users or another application need not become another login project. ProAuth brings authentication together in a self-hosted identity provider. You choose where it runs; dotNET lab helps configure and integrate it, with support agreed for your deployment.

Why ProAuth
You choose the environment
Your own infrastructure or a cloud of your choice. Offline operation requires local authentication and dependencies.
Repeatable customer onboarding
Manage tenants and OIDC federation centrally. Tenant-specific login views and SCIM are Enterprise features.
Clear accountability
4tecture develops the product and supplies patches. We agree who integrates, tests, deploys and operates it.
Recognisable situations
Three situations where a shared identity platform helps your team stay in control as your software and customer base grow.

Connect customers to their own Entra ID or another OIDC provider. Manage tenants and federation centrally; the edition determines configuration limits. Enterprise adds tenant-specific login views. We design and test the application integration first.

Choose a self-hosted installation, including locations without internet. This requires local authentication, databases and other dependencies. Shipping ProAuth with your product requires a separate redistribution or OEM agreement.

You want to grow without per-user licence fees. ProAuth is licensed per production installation. Budget infrastructure, implementation, operations and any SMS or email services separately.
Want ProAuth to run on European infrastructure and have us manage it? See Sovereign EU cloud & management.
Why an identity provider
When customers, partners and applications use separate logins, access management becomes fragmented. A shared identity provider lets you manage authentication and policy centrally. ProAuth is a product developed by 4tecture in Switzerland that you can run in your own environment.
Control: Hosting location, applicable jurisdiction and external dependencies are separate choices. Total cost: Compare licensing, infrastructure, implementation, messaging and operations together. Responsibility: Define who tests updates, handles incidents and operates the environment.

How it fits your landscape
Applications sign users in through OIDC. APIs validate OAuth access tokens. User and group provisioning is separate from authentication.
Where identities come from
What relies on that one login
Conceptual diagram. Federation authenticates; SCIM and Directory Sync provision. Claims Rule Engine and signed audit trails are Enterprise features. The design specifies integrations and offline dependencies.
What you get
We help assess the fit, choose the edition and define integration and operational responsibilities. The proposal records the scope and support arrangements.
Starter and Business are annual subscriptions. Enterprise also offers a perpetual licence. Redistribution or OEM requires a separate agreement.
Which customers get their own user store and which federate, which claims each application needs, which MFA policy applies per tenant. Captured as configuration we repeat per environment.
Applications use OpenID Connect for sign-in. APIs validate OAuth access tokens. Configuration, monitoring and security controls are integrated for your environment.
First assess accounts, password hashes, MFA, passkeys, application identifiers and claims. Then plan a staged migration with testing and rollback. Existing accounts can be preserved where the source system and formats permit.
4tecture provides Basic Support during active coverage and optional support plans. Enterprise Managed lists a two-hour initial response for Sev-1 and 24/7 availability for critical issues, not a resolution deadline. dotNET lab operations are agreed separately.
ProAuth is developed by 4tecture GmbH in Switzerland. As a Benelux partner, dotNET lab helps with licensing, integration and agreed support.
Developer
Benelux partner
Behind the implementation: a team that has been building software for 25+ years, with development, security, cloud and identity under one roof.
How we work
A workable deployment starts with your applications, users and risks. We define the design, migration steps and responsibilities before switching.
Which applications use OIDC, which APIs validate OAuth tokens and which customers federate through Entra ID or AD FS/OIDC? We assess AD user and group provisioning separately.
We match edition, licensing and hosting to required features and dependencies. Offline operation requires a fully local setup.
Repeatable per environment, from test to production: user stores, federations, MFA policy per tenant or application, branding and the claims each application receives.
First assess accounts, password hashes, MFA, passkeys, application identifiers and claims. Then plan a staged migration with testing and rollback. Existing accounts can be preserved where the source system and formats permit.
We define monitoring, logging, update testing, deployment and incident handling. Timing and support coverage depend on the integration and agreement.
Under the bonnet
ProAuth uses OpenID Connect for sign-in and OAuth 2.0 for API access. These controls support security reviews and audits; outcomes also depend on configuration, integration, operations and audit scope.
Passkeys and TOTP are available in all editions. Email as a factor is available from Business; SMS in Enterprise. Choose and test the factors your environment needs.
User stores on SQL Server, Azure SQL or PostgreSQL, or OIDC federation such as Entra ID or AD FS. SCIM provisioning and ProAuth Directory Sync for AD users and groups are Enterprise features.
Enterprise: the Claims Rule Engine shapes claims per client. Applications and APIs must still enforce their own authorisation rules.
FAPI 2.0 is opt-in, not enabled by default. DPoP and mTLS require compatible clients and API validation. We configure and test these controls for your environment.
Enterprise provides a signed audit trail. Logging, metrics, retention and access to audit data are configured for your requirements.
Manage tenants, clients and federation through the portal, API or CLI. Availability and limits depend on the edition. New customer configuration can avoid an application release when the integration is designed for it.
Data sovereignty
A fully offline deployment is possible with local authentication and dependencies. External Entra federation, SMS services and other external integrations still need connectivity.
We assess hosting location, data processing, jurisdiction and operating arrangements separately. Self-hosting gives control, not an automatic compliance guarantee.
PostgreSQL can run locally in the same cluster. It remains a database dependency that needs management, backups and recovery.
Editions
Compare editions · Licensing and support
One licence covers one production installation, including multiple runtime instances or replicas within it. Separate production installations each need a licence. Infrastructure, integration, operations and messaging are separate costs.
Who it is for
ProAuth fits organisations where many people have to sign in, customers, members, citizens or partners, across several applications, and where requirements apply around MFA, audit and the place where identity data lives.
Together we assess integration, desired control and available operational capacity. A demo shows how the relevant features work in your chosen edition.

Related
4tecture’s current product information is the source for edition boundaries and terms. Your proposal defines the agreed scope.
FAQ
ProAuth is a self-hosted identity provider developed by 4tecture GmbH in Switzerland. Applications use OpenID Connect for sign-in and single sign-on; APIs validate OAuth access tokens. The edition determines features and configuration limits.
ProAuth is developed by 4tecture GmbH in Switzerland. As a Benelux partner, dotNET lab helps with licensing, integration and agreed support. We explicitly agree who tests and deploys patches, operates the environment and handles incidents.
One licence covers one production installation, including multiple runtime instances or replicas within it. Separate production installations each need a licence. Infrastructure, integration, operations and messaging are separate costs. Starter and Business are annual subscriptions. Enterprise also offers a perpetual licence. Redistribution or OEM requires a separate agreement.
A fully offline deployment is possible with local authentication and dependencies. External Entra federation, SMS services and other external integrations still need connectivity. PostgreSQL can run locally in the same cluster. It remains a database dependency that needs management, backups and recovery.
No. ProAuth is an OpenID Connect and OAuth 2.0 server; federation to external identity providers runs through OIDC. If you have SAML integrations with older systems, we look in the first conversation at whether a bridge is enough or another choice fits better.
Compare hosting control, product features, total costs and operational responsibilities. Cloud platforms can offer European regions and enterprise options; commercial support also exists for open-source products. ProAuth combines self-hosting with product licensing and support. The right choice depends on your requirements.
ProAuth can federate with Entra ID or AD FS through OIDC. Provisioning AD users and groups is a separate task, using ProAuth Directory Sync and SCIM in Enterprise. This does not mean direct LDAP or Kerberos authentication.
First assess accounts, password hashes, MFA, passkeys, application identifiers and claims. Then plan a staged migration with testing and rollback. Existing accounts can be preserved where the source system and formats permit.