Plazia Identity · made for product builders

Your product.
Their way in.

A welcoming sign-in. A connected experience.
Bring passkeys, SSO, and customer organizations
into the products you’re building.

Every step feels like your product.

Eight little demos. Swipe or use the arrows to explore.

Explore the steps. Read the real integration code. Set up the SvelteKit adapter →

Built on familiar foundationsOpenID ConnectOAuth + PKCEWebAuthnDevice authorization

From first sign-in to daily operation

The identity work behind
every good product.

Connect the experiences your users see with the controls your team needs.

Let people sign in their way.

Passkeys, passwords, email codes, and configured identity providers. Registration and recovery belong to the same hosted experience.

Explore authentication

Make room for every customer.

Organize customers within each product. Keep memberships, connections, and organization policies tied to the right business.

Explore customer organizations

Keep each product in focus.

Manage separate businesses, environments, and application registrations through a central management entry.

Explore workspace boundaries

Connect to existing identity.

Use configured OIDC connections for enterprise or social sign-in, with connection policy under your control.

Explore integrations

Cover the whole session.

Support authentication, refresh, revocation, and logout as part of your application’s identity lifecycle.

Explore session controls

Build beyond the browser.

Connect browser applications, supported native clients, devices, and backend services through their appropriate protocol flows.

Explore application types

Designed around what you’re building

Choose your starting point.

Web applications

Your application starts authentication. Identity hosts the configured sign-in experience and returns the user to your registered callback.

  1. Register your application and its callback.
  2. Launch hosted authentication using OAuth and PKCE.
  3. Handle the callback and establish your application session.
Business SaaS

Give each customer an organization inside your product’s identity workspace. Keep membership and connection policy explicit as your customer base grows.

  1. Create the business and its environments.
  2. Configure customer organizations and their connections.
  3. Authenticate users in the right organization context.
Devices & services

Use device authorization for devices that cannot host a full sign-in experience. Give backend services their own registered credentials and API grants.

  1. Choose the appropriate device or service client.
  2. Configure the target API and permitted scopes.
  3. Use the registered flow and manage credential lifecycle.

Developer experience

Choose an integration.
Follow a real example.

Start with the application you have. Keep protocol details, configuration, and complete examples close at hand.

Explore the documentation
SvelteKit applications

Use the server adapter for authorization entry, callback handling, protected pages, and logout. Keep credentials and session storage on your server.

SvelteKit integration
Browser applications

Use the TypeScript browser SDK for discovery, authorization-code launch with PKCE, callback verification, and session helpers. Public clients never receive a client secret.

Explore the SDKs
APIs and backend services

Register application clients and API audiences. Use the management API and CLI to configure users, organizations, connections, and service credentials.

Management API
Events and feature configuration

Connect lifecycle events through webhooks. Manage typed feature flags and scoped overrides separately from access permissions.

Security you can reason about

Clear boundaries.
Deliberate access.

Understand how applications, organizations, and sessions fit together before you connect your product.

Application and callback boundaries

Registered clients, explicit redirect policies, PKCE, and issuer validation define the authentication handoff.

Customer organization boundaries

Organization membership and credentials determine identity access. A hostname or a selected workspace does not grant permissions.

Session and credential lifecycle

Refresh, revocation, and logout have explicit contracts. The central management app keeps its OAuth credentials on the server.

Product authorization stays with your product

Identity provides authentication and shared identity facts. Your application owns its business rules and domain permissions.

Start with your next application

Give identity a clear home.

Explore integration guides