ProAuth identity provider, with dotNET lab as your Benelux partner

Keep control of identity as your software grows

  • Control over hosting and identity data.
  • Manage customer identities centrally, without per-user licence fees.
  • Clear responsibilities for implementation, updates and support.

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.

Illustration: a receptionist hands a light blue badge to a visitor at a desk; behind them hang four application windows with an open padlock, and a small European flag stands on the desk.

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

Where ProAuth makes the difference

Three situations where a shared identity platform helps your team stay in control as your software and customer base grow.

  • Illustration: someone slides a light blue card next to three identical cards into one large application window.

    You sell a SaaS platform to dozens of customers

    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.

  • Illustration: someone kneels next to a server tower and plugs a cable with a light blue plug into the front.

    Your product runs at the customer, sometimes without internet

    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.

  • Illustration: someone holds a large door open with a light blue key in hand, while a row of small figures in the distance walks towards the door.

    Your portal counts tens of thousands of users

    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

Login should not be rebuilt in every application

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.

Illustration: on the left someone struggles under a wobbly stack of door panels each with a keyhole, on the right someone relaxed shows a single panel with one keyhole.

How it fits your landscape

One identity provider between your identity sources and all your applications

Applications sign users in through OIDC. APIs validate OAuth access tokens. User and group provisioning is separate from authentication.

Where identities come from

  • Own user stores (SQL Server, Azure SQL, PostgreSQL)
  • Entra ID or AD FS via OIDC
  • External OIDC identity providers
  • Enterprise: SCIM / AD Directory Sync

What relies on that one login

  • Applications via OIDC; tenant login views in Enterprise
  • Customer and member portals
  • APIs: OAuth token and proof validation
  • Local products with local dependencies

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

Licence, implementation and follow-up from one hand

We help assess the fit, choose the edition and define integration and operational responsibilities. The proposal records the scope and support arrangements.

Licence and edition advice

Starter and Business are annual subscriptions. Enterprise also offers a perpetual licence. Redistribution or OEM requires a separate agreement.

Tenant and access design

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.

Installation and integration

Applications use OpenID Connect for sign-in. APIs validate OAuth access tokens. Configuration, monitoring and security controls are integrated for your environment.

Migration of existing logins

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.

Support and management

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

4tecture GmbH

  • Develops and maintains the product
  • Delivers updates and security patches
  • Second line for product defects

Benelux partner

dotNET lab

  • Licences and pricing proposal
  • Design, installation and integration into your software
  • Support and operations as agreed

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

First the tenant model, then the installation

A workable deployment starts with your applications, users and risks. We define the design, migration steps and responsibilities before switching.

  1. 01

    We map applications, customers and identity sources

    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.

  2. 02

    We choose the edition and where it lands

    We match edition, licensing and hosting to required features and dependencies. Offline operation requires a fully local setup.

  3. 03

    We capture tenants, applications, permissions and MFA policy as configuration

    Repeatable per environment, from test to production: user stores, federations, MFA policy per tenant or application, branding and the claims each application receives.

  4. 04

    We switch over, application by application

    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.

  5. 05

    We take care of management and evolution

    We define monitoring, logging, update testing, deployment and incident handling. Timing and support coverage depend on the integration and agreement.

Under the bonnet

Technical capabilities, with clear edition boundaries

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.

Compare editions

  1. Authentication

    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.

  2. Federation and user stores

    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.

  3. Authorisation

    Enterprise: the Claims Rule Engine shapes claims per client. Applications and APIs must still enforce their own authorisation rules.

  4. Tokens and API security

    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.

  5. Audit and observability

    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.

Standards, objects and tooling

  • OpenID Connect and OAuth 2.0
  • Authorization code with PKCE
  • FAPI 2.0 opt-in; integrated DPoP/mTLS
  • Passkeys and TOTP in all editions
  • SQL Server, Azure SQL or PostgreSQL
  • OIDC federation, such as Entra ID or AD FS
  • Enterprise: Claims Rule Engine and SCIM
  • Enterprise: tenant-specific login views and audit trail
  • Portal, Management API and CLI
  • Validate updates against topology and compatibility

Data sovereignty

Your login process runs where your data runs

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 logo PostgreSQL can run locally in the same cluster. It remains a database dependency that needs management, backups and recovery.

Editions

Choose the edition for your deployment

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.

  • Starter: annual subscription; 5–15 client applications, 1 user store and 1–2 federation configurations, depending on tier
  • Business: annual subscription; 15–30 clients, 2 user stores and 2–5 federation configurations
  • Enterprise: subscription or perpetual licence; no licence count caps on clients, user stores and federation; additional features such as SCIM and audit trail
  • Redistribution/OEM: separate agreement, not automatically included
  • Basic Support during active subscription or upgrade coverage; additional support according to the selected plan

Who it is for

For organisations with many users or complex requirements

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.

Request a demo
Illustration: three professionals from different organisations side by side; the middle one holds a single key with both hands to the chest.

Related

4tecture’s current product information is the source for edition boundaries and terms. Your proposal defines the agreed scope.

FAQ

Frequently asked questions

What exactly is ProAuth?

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.

What is the role of dotNET lab?

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.

How does the licence work and what does ProAuth cost?

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.

Where does ProAuth run?

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.

Does ProAuth support SAML?

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.

Why ProAuth and not Keycloak, Duende IdentityServer or Auth0?

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.

We already use Entra ID or Active Directory. Is ProAuth still useful?

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.

Can we migrate from IdentityServer or a home-grown login module?

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.

First step

Curious whether ProAuth fits your architecture?

Tell us which applications, customers and identity sources exist today.

We show ProAuth in a demo on your situation and give a concrete estimate of edition, where it lands and the implementation.