Skip to content
← All scenarios

Deployment control

Choose where identity runs. Keep the choice yours.

Your infrastructure strategy can change. Own the identity platform, its configuration and its data so that identity can move with your applications.

Plan your implementation

Choose your operating environment

  • On premises
  • Private cloud
  • Public cloud
ProAuthContainer / Helm / Kubernetes
The same product. Alternative locations. Data, keys and dependencies remain part of your migration plan.

The business situation

Your hosting strategy changes

An organisation runs its applications in a public cloud and wants the option to move to another provider or its own infrastructure. Identity must be part of that plan, together with the application and its data.

01 / Working model

Use a consistent deployment foundation

ProAuth is delivered as container images with Helm deployment tooling. Public cloud, private cloud and on-premises environments use the same product. Choose where to deploy it; you do not need an installation in every location.

The environment must supply supported SQL Server or PostgreSQL databases, HTTPS, certificates and the shared services required by your configuration. The installation documentation specifies these dependencies.

Portability includes the dependencies.

Databases, certificates and shared services are planned alongside the platform.

YOUR OPERATING ENVIRONMENT

Runtime
ProAuth
  • Container image
  • Helm / Kubernetes
Persistence
Database
  • SQL Server · Azure SQL
  • PostgreSQL
Platform services
As configured
  • HTTPS certificates · keys
  • Shared services where required

One runtime, a supported database, and the services required by your configuration.

What your team gains

Choose the environment
Deploy the same product on a suitable Kubernetes cluster in your chosen location.
Keep control of the data
Manage the databases, backups, configuration and keys within your operating environment.
Retain room to change
Plan a hosting move using the same identity product and application integration.
02

Move the platform with a plan

A hosting change includes ProAuth configuration, databases, keys, domain and certificate continuity, and any external identity connections. Validate backups, restore procedures and the full sign-in flow in the destination environment.

Keeping identity under your administration gives you control of that move. Capacity, networking, dependencies and application endpoints still need planning. This is infrastructure portability, not an automatic migration service.

03

Keep operational ownership clear

You choose who operates the cluster, manages secrets, monitors services and deploys product updates. ProAuth product support provides a point of contact for product issues; it does not automatically take over infrastructure operation.

Agree the edition, licence scope and support arrangement for your intended use. User-independent licence pricing gives you a defined licence budget; hosting, implementation and management are separate costs. Each licence covers one installed production system with unlimited runtime replicas and associated dev/test environments, including QA, staging and CI/CD. Purchased features and configuration limits apply independently in each environment; separate production installations need separate licences.

Details for your decision.

Let’s plan your implementation.

Bring your application landscape and deployment requirements. We can review identity sources, integration boundaries and an appropriate edition together.

Discuss your identity platform

Image detail