Authentication for SaaS

Sign-in for
every customer.

Add passkeys for individuals, company workspaces, and scoped reseller access through one integration. Enterprise single sign-on is planned.

Interactive previewCA / Canada
Demo modes Sample accounts

Three paths through Covenant

  • PersonalSign in with a passkey
  • BusinessPreview company SSO
  • ResellerOpen an assigned workspace

The demo simulates sign-in. Company SSO is planned.

From first signup
to enterprise rollout.

Start with individual accounts, then add company workspaces and reseller permissions as your customers grow.

Sign in with a passkey

Let people return with the passkey they enrolled for their account.

Connect company identity

Give each customer organization its own members and roles. Preview the planned company sign-in experience.

Delegate reseller access

Let customers grant a reseller access to specific tasks and revoke it from their own workspace.

For developers

Start with the auth library you already use.

Run the Northline sample with your OpenID Connect library. Production app registration and company federation are planned.

.env.example
OIDC_ISSUER=https://ca.covenant.example
OIDC_CLIENT_ID=your_client_id
OIDC_REDIRECT_URI=http://localhost:3000/callback

Example configuration · Placeholder issuer

Trust and residency

Know who handles your identity data.

Covenant’s launch standard requires a non-US provider for every service that handles identity data, including hosting, backups, recovery email, logs, and support.

Planned region

Canada

Identity storage, backups, and audit logs are designed to stay in Canada.

Common questions

View all questions
What can I test today?

The local build supports OpenID Connect with PKCE, passkey enrollment and sign-in, company workspaces, and scoped reseller access. The Northline sample integration demonstrates the sign-in flow end to end.

Where will my users’ identity data live?

Canada and the European Union are the planned hosting regions. Each region is designed to have its own identity service, databases, backups, and audit logs. You’ll choose a region when setting up your application.

What does the non-US provider requirement cover?

It covers every service that handles identity data, from the edge services that terminate encrypted connections to hosting, backups, recovery email, logging, and support. Before launch, Covenant will verify who operates each service, where it processes data, and who can access it.

How will company single sign-on work?

An admin verifies the company’s domain by adding a DNS TXT record. The planned setup then connects the company’s identity provider using SAML or OpenID Connect. Domain verification is implemented. Self-service SSO setup and SCIM directory sync, including automatic removal of access, are in development.

What can a reseller access?

A customer can let a reseller invite members to one company workspace. The grant excludes admin assignments, audit logs, and other workspaces. If the customer revokes it, the reseller loses access and any pending invitations issued through that grant are cancelled.

How are sensitive account changes protected?

Issuing invitations and changing reseller grants require recent identity verification. The workspace audit log records who made each access change and when.

How will pricing work?

Pricing is still in development. We’re evaluating a model based on active enterprise connections for single sign-on and directory sync.

Does the demo use real accounts?

The demo uses sample accounts and simulated sign-in. It collects no credentials or personal data.