Transparent, predictable enterprise pricing

Each licence covers one installed production ProAuth system, normally within one Kubernetes cluster, with unlimited runtime instances and replicas for scaling and availability. Each separate production installation needs its own licence, even within the same company or cluster. Multiple tenants within one installation do not themselves create additional deployments.

Yes, for supported versions during an active subscription or perpetual upgrade coverage. Basic Support covers reporting and triage of suspected product defects, applicable remedies and security advisories, with an initial substantive response within one business day. Business hours are 09:00–17:00 Europe/Zurich local time, including daylight-saving time, Monday–Friday excluding public holidays in Volketswil, Zurich. First response is not a resolution deadline. Mandatory vulnerability handling and security remedies remain separate.

Configuration, integration, deployment and upgrade assistance are available through escalation packs or the optional Enterprise Standard, Enterprise Premium and Enterprise Managed support plans.

One technical support case for configuration, integration, deployment or upgrade assistance, covering up to 5 hours of engineering work. Confirmed product defects, security issues and quick clarifications resolved in under 15 minutes do not consume escalations.

A subscription permits use and includes edition updates while active. Expiry without renewal ends use rights, including associated dev/test use; there is no contractual use grace period. Enterprise perpetual includes 12 months of upgrade coverage unless your order provides longer. You may use covered versions indefinitely after coverage ends, subject to the agreement.

No. You retain indefinite use of covered versions. After the included 12 months, optional software upgrade coverage costs CHF 9'800/year for later feature releases and ordinary fixes. Expiry does not remove security remedies required by applicable law. A support plan alone does not extend upgrade coverage.

No. ProAuth does not charge per user, MAU or DAU. Your purchased edition and tier determine application-registration, user-store and federated identity-provider configuration limits. A provider configuration is a connection to an upstream identity provider, not a runtime replica. Production limits apply across the installation, not separately per tenant or replica.

No. Unlimited runtime instances and replicas can scale the licensed installation without additional instance fees. Separate installed production systems require separate licences.

Each independent ongoing production installation requires a separate licence, even within the same company or Kubernetes cluster. Passive disaster recovery and limited temporary overlap are included as described below.

Only under an agreed redistribution, OEM or custom licence. A normal Enterprise subscription or Enterprise perpetual licence does not automatically grant redistribution rights. Contact ProAuth for commercial terms.

Using ProAuth to authenticate users of your own business applications or SaaS product is permitted within your licence scope. Selling a standalone identity or authentication service to third parties requires a separate written agreement; a standard software licence does not grant that right.

Included escalations expire at the end of the contract year. Separately purchased escalation packs are valid for 12 months from purchase; unused escalations expire.

Yes. Each production licence includes the same purchased features for unlimited associated development, QA, testing, staging and CI/CD environments. Application-registration, user-store and federated identity-provider configuration limits apply independently in each environment; test configurations do not consume production allowances. Unlimited environments do not mean unlimited features or configuration allowances. Non-production environments must not serve live business operations.

Passive disaster recovery is included. Temporary production overlap for failover, failback or migration of the same system is included for up to 30 days per event. Independent ongoing production installations need separate licences. See section 3.4 of the agreement for transition qualifications.

Required security remedies are not conditional on paid upgrade coverage. Where the EU Cyber Resilience Act support-period requirements apply to a perpetual supply, the agreement provides five years from that supply’s delivery, or longer where legally required. This is not a voluntary five-year promise for all sales. Release maintenance may follow .NET lifecycles; a qualifying newer version can provide the required remedy without an upgrade fee under sections 7.4–7.8. This does not promise maintenance of every old release or access to every optional future feature.

Unless your order states otherwise, subscriptions renew annually unless cancelled at least 30 days before the term ends. Renewal price increases require 60 days’ notice; late notice leaves that renewal at the old price unless you expressly agree otherwise. Perpetual upgrade coverage and separate support renew automatically only if your order expressly selects it. Standard payment terms are 30 days.

Only your subsidiaries expressly named by legal name in the order may share your licensed installation. Parent companies, sister companies and other group entities are not included. Separate production installations still require separate licences.

No. Supplier defence or indemnity for third-party intellectual-property claims requires a separate agreement signed by both parties. Edition names and support plans do not include it. See sections 15 and 17 for remedies and liability terms.

No. Agreement version 3.0-2026-09-28 applies to orders that incorporate it. A website update, software update or continued use does not automatically replace existing customer contracts; changes require agreement.