Sign in with a passkey
Let people return with the passkey they enrolled for their account.
Authentication for SaaS
Add passkeys for individuals, company workspaces, and scoped reseller access through one integration. Enterprise single sign-on is planned.
Use a passkey to access your personal account.
The demo simulates sign-in. Company SSO is planned.
Start with individual accounts, then add company workspaces and reseller permissions as your customers grow.
Let people return with the passkey they enrolled for their account.
Give each customer organization its own members and roles. Preview the planned company sign-in experience.
Let customers grant a reseller access to specific tasks and revoke it from their own workspace.
For developers
Run the Northline sample with your OpenID Connect library. Production app registration and company federation are planned.
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
Covenant’s launch standard requires a non-US provider for every service that handles identity data, including hosting, backups, recovery email, logs, and support.
Identity storage, backups, and audit logs are designed to stay in Canada.
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.
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.
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.
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.
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.
Issuing invitations and changing reseller grants require recent identity verification. The workspace audit log records who made each access change and when.
Pricing is still in development. We’re evaluating a model based on active enterprise connections for single sign-on and directory sync.
The demo uses sample accounts and simulated sign-in. It collects no credentials or personal data.