Identity platform comparison

Covenant vs. WorkOS

Compare WorkOS and Covenant for SaaS onboarding. Read how AuthKit, Admin Portal and Directory Sync compare with Covenant’s reseller permissions and regional processing design.

At a glance

Who sets up the customer?

  • Customer IT adminWorkOS Admin Portal
  • Company-assigned resellerCovenant delegated invitations
  • Directory lifecycleWorkOS available · Covenant planned

The same customer can have two kinds of onboarding

WorkOS combines AuthKit for sign-in and user management with enterprise SSO, Directory Sync, and an Admin Portal that helps customer IT teams set up connections themselves. SaaS teams can buy the enterprise integration layer alongside authentication or connect it to their existing identity stack.

Covenant starts with a different onboarding scenario. A customer company can authorize a reseller to help onboard members to its workspace and later remove that access. The local Keycloak-backed pilot also handles personal sign-in, direct company invitations and workspace audit activity. Covenant’s production enterprise connections are planned.

This comparison uses WorkOS’s published product guides and Covenant’s synthetic pilot tests. Evaluate company IT setup and reseller delegation as separate requirements. A partner who helps a customer get started has a different role from the IT admin who controls the customer’s directory.

WorkOS AuthKitWorkOS Admin PortalWorkOS Directory Sync

Side-by-side comparison

Covenant vs. WorkOS by capability
CapabilityCovenantWorkOS
Hosted authenticationOIDC and passkeys verified against the local pilot. Workspace context is shown in Covenant’s console.AuthKit offers hosted sign-in, user management, organizations, MFA and passkeys.
Enterprise onboardingCompany domain claims and invitations work in the pilot. Self-service company SSO setup is on the roadmap.Admin Portal guides customer IT through supported SSO, Directory Sync and domain verification setup.
Directory lifecycleMember removal and reseller grant revocation are tested in the pilot. SCIM, group mapping and downstream offboarding are planned.Directory Sync normalizes users and groups across supported directories and delivers updates through events or webhooks.
Partner and reseller workflowsA company owner grants and revokes limited onboarding access for assigned resellers. Delegates can invite members.AuthKit for Platforms covers provisioning auth for a platform’s users’ apps. Your app defines reseller assignments and privileges across customer companies.
Audit and data locationWorkspace activity is available locally. Regional operation and production audit exports are planned.Audit Logs can expose organization-scoped application events in the Admin Portal. WorkOS documents US hosting and backups.

WorkOS AuthKitWorkOS Admin PortalWorkOS Directory SyncAuthKit for PlatformsWorkOS Audit LogsWorkOS security and hosting review

Where WorkOS reduces enterprise integration work

Imagine a customer that signs with a requirement to connect its identity provider and remove access when staff leave the company. The WorkOS Admin Portal gives the IT contact a guided setup path. Directory Sync gives your application a consistent way to consume user and group changes across supported providers. Your integration still owns application-specific authorization and has to process offboarding events reliably.

WorkOS can collect audit events from your application and show them by organization. That lets teams build a customer-facing trail without designing every part of the viewing experience. Your application still decides which events to emit, what data they contain and how those events support your contractual retention and export requirements.

WorkOS Admin PortalWorkOS Directory SyncWorkOS Audit Logs

Where Covenant’s reseller model helps

Covenant’s prototype lets the customer company control who assists with onboarding. A reseller delegate sees assigned companies and can invite members to those companies. The company retains authority over admin access and audit visibility. Revoking the grant blocks the delegate’s next request to that company and cancels outstanding invitations the delegate issued under that grant.

This is useful to evaluate when customers buy through multiple partners or a reseller moves off an account. Put one reseller on two synthetic workspaces, revoke access from one company, and verify the other assignment still works. Check already accepted members separately because they belong to the company directly after acceptance.

Hosting, processors and cost

WorkOS’s security review identifies AWS US East as its customer-data hosting location and AWS US West for replicated backups. For a procurement policy requiring every identity-data processor to be non-US, start the vendor review with those facts. Covenant targets independent deployments in Canada and the EU. Its processor inventory, support-access verification and operational evidence are production gates.

As reviewed November 20, 2026, WorkOS lists AuthKit as free up to one million monthly active users. Published pay-as-you-go pricing starts at $125 per month per enterprise SSO connection and per Directory Sync connection in the first tier, with published volume discounts. A company that buys both services can require one connection of each type. Check optional features and any annual contract terms alongside those numbers.

For example, at the published entry rate and before other products or discounts, four customer SSO connections and two directory connections are six billable connections, or $750 per month. Compare that with the work your team would own in a build and the Covenant pilot scope. Request commercial terms from Covenant for any production estimate.

WorkOS security and hosting reviewWorkOS pricing

What to test before switching

  1. Map each organization and connection

    List existing customer organizations, identity providers, domains, directories and group mappings. Identify which WorkOS resources take part in sign-in, onboarding, provisioning and audit.

  2. Check the access lifecycle twice

    Test removing someone from a customer directory and revoking a reseller grant as different actions. Record how they affect new requests, invitations, active sessions and support access.

  3. Choose a pilot with supported workflows

    Use synthetic accounts and a representative reseller. Keep customers with production SSO or SCIM requirements on their existing connection while you validate the target workflow and rollback.

Which fits your team?

Choose WorkOS when the urgent job is deploying enterprise SSO and directory provisioning with a polished IT-admin setup experience. Evaluate Covenant when customer-controlled reseller onboarding is central to the workflow and the processor policy determines which vendors are eligible. Confirm the pilot scope and the release gates before planning a migration.