Your identity has a place.
Profile and security controls belong together. Keep account work separate from shopping, software publishing and product licensing.
PLATINUMAUTH
IDENTITY, ON YOUR TERMS
IDENTITY, ON YOUR TERMS
An account you can understand.
A focused home for identity: who you are, which applications you use, and the keys, devices and sessions that connect them. Built to give people clear choices and organizations a workspace of their own.
In development. Evaluation features and availability may differ from the public release.
A closer look.
Explore account, security and organization tools.
A clear boundary for each application.
The Auth integration is built around explicit application identity and permission checks. Moving between applications should keep their purpose and authority clear.
Your organization, your service.
PlatinumAuth is being developed as an independently licensable service, with managed and self-hosted deployment options. It does not require a Software Hub purchase to define your identity system.
Account security your team can manage.
Key-based identity, without a required username
A cryptographic key can identify an account without a public username. A deployment may still request a verified contact or other information for its own enrollment and recovery policies.
Local keys, local protection
Protect local key material with a local password where supported by the client and key provider. Proving possession means answering an authenticated challenge, not uploading the private key as a substitute for signing.
Understand what is connected
Review the applications, sessions and devices involved in your account. Identity controls should make the boundaries legible, including which application is asking and what data it needs.
An identity service that stands on its own
Auth owns identity, groups, security and consent. Software purchases, release publishing and licensing operations belong to Software Hub, with distinct application permissions.
Security suited to the deployment
The interface provides a place for session policies, providers and recovery controls. Choose session, recovery and provider policies that fit the people using your service. We configure these with your administrators during deployment.
Privacy as a product choice
We favor minimal identity information and explicit sharing, rather than building advertising profiles or selling user data. Configured services may still process personal data, security events or operational logs; minimization is not a claim that every deployment records nothing.
One identity system. Different kinds of work.
A branded front door
Make sign-in recognizable to your own organization. Keep the account workspace separate from the applications it opens, with explicit destinations rather than a tangle of unrelated administration tabs.
Know who has access.
Give people a clear place to manage their identity, devices and sessions. Cryptographic sign-in proves control of a key, while application permissions decide what that identity can do. Keep recovery, enrollment and administrative access understandable to the people responsible for them.
Choose the identity information your organization needs and share it deliberately with applications. We do not build advertising profiles or sell identity data. During evaluation, we help you match account policies, recovery and service settings to your own requirements.
A MORE COMFORTABLE WAY TO WORK
Keep the work in view.
Recognizable controls, readable information and direct actions. The Platinum approach makes room for the details without hiding the next useful step.
For the person signing in
A recognizable account workspace, understandable prompts and a clear destination.
For your administrators
Identity administration, users and groups, with security and deployment controls in the same focused application.
For your developers
Integrate identity through the PlatinumSDK contracts while keeping your application’s own data and authorization boundaries.
Let’s find the right fit.
Contact us to arrange an evaluation and discuss licensing, deployment timing and the integrations your team needs. Public downloads are coming soon.
We review your account, recovery and identity-service requirements with you during setup.
Talk to Winnitude! ↗A shared foundation for everyday work.
A shared foundation for security, integration and responsive applications. Spend less time connecting separate systems and more time doing useful work.
Security built into the foundation.
Identity has its own home. Application permissions, user identity and software ownership stay separate, so access can be granted deliberately instead of inherited by accident.
Integrate once. Keep the context.
PlatinumSDK products share application contracts, familiar controls and a common approach to data. Connect the services you need without rebuilding every foundation. Existing systems can join through supported interfaces and adapters; compatibility depends on the integration.
Responsive by design.
A native, GPU-accelerated foundation and data-oriented architecture aim to keep feedback close to the action. Less waiting on the interface, fewer interruptions to the work. Actual performance depends on the application, device and workload.
A workspace that fits your team.
Shared themes and configurable workspaces let the tools adapt to the way you work. Choose a familiar desktop character or a more restrained business presentation, with consistent behavior underneath. Available controls and customization vary by release.
Managed where it helps. Yours where it matters.
Discuss a managed deployment to reduce setup and day-to-day infrastructure work, or a self-hosted configuration for your organization’s requirements. Identity, integrations and hosting are configured deliberately rather than hidden behind a one-size-fits-all installation.
Keep the overhead proportionate.
Shared infrastructure helps avoid paying for the same foundations over and over. Ask about an evaluation, licensing and deployment options suited to your scale; we will confirm the price and included services before you commit.
How the security and deployment model fits together
Authentication proves identity; authorization controls actions; encryption protects content in a defined storage or transport context. Release hashes and signatures establish integrity and provenance, not that software is harmless. Process isolation and resource brokering are runtime responsibilities. We help you select the runtime, hosting and access settings that fit your deployment, and explain which protections each layer provides.
We agree the hosting, integrations, access rules and support responsibilities with you during evaluation, so the setup matches your organization.
Understand the boundaries.
Identity, permissions and a verified release record answer different questions. These architecture illustrations explain how the pieces fit—and where the limits remain.
Explore the architecture
The application checks that it is talking to the service you intended to use before you share account information.
These diagrams explain the architecture. During evaluation we help you choose the hosting, integrations and security settings appropriate for your organization.
Find the rest of your workspace.
Built with PlatinumSDK. Applications with their own purpose, connected through explicit integrations.