Identity platform comparison

Covenant vs. Firebase

Compare Covenant with Firebase Authentication and the Identity Platform upgrade. See how sign-in, tenant roles, reseller onboarding, and data location affect SaaS decisions.

At a glance

Choose the level of identity you need

  • App sign-in and SDKsFirebase Authentication
  • MFA, SAML and identity tenantsIdentity Platform upgrade
  • Company and reseller workspacesCovenant’s local pilot

Firebase Authentication and Identity Platform

Firebase Authentication gives an application managed sign-in and client and admin SDKs. It is a practical fit for many teams already using Firebase for mobile or web development. Google’s Identity Platform is also the backend for Firebase Authentication with Identity Platform. That upgrade adds capabilities such as MFA, SAML and OIDC identity providers, multi-tenancy and blocking functions.

Covenant is developing a SaaS identity product for individuals, companies and resellers. The current pilot uses Keycloak for standards-based sign-in and passkeys. Covenant’s console handles workspace invitations, role-based access and company-granted reseller onboarding. Its independent Canadian and EU production deployments are planned.

This comparison covers authentication and SaaS access workflows. Firebase’s database, hosting and other app services have their own capabilities and data terms. The Covenant examples reflect synthetic accounts and local tests.

Google’s Firebase and Identity Platform comparison

Side-by-side comparison

Covenant vs. Firebase by capability
CapabilityCovenantFirebase
Application sign-inHosted OIDC and passkeys tested in the local pilot. The Northline sample uses the authorization code flow with PKCE.Base Firebase Authentication supports managed sign-in and client SDKs. Identity Platform adds MFA and generic SAML/OIDC provider support.
Company accessPersonal and company workspaces, member and admin roles, and account-bound invitations.Identity Platform adds identity tenants. Admin APIs and custom claims let teams implement project or tenant-specific access rules.
Reseller onboardingCompany owners assign and revoke a limited onboarding grant for a reseller. The delegate can invite company members.Model reseller-to-company relationships, invitation privileges, and admin views in the application.
Sessions and offboardingConsole sessions are revocable. Workspace membership and delegation are checked on each scoped request.Firebase Admin SDK can revoke user refresh tokens. Applications can check token revocation when required by their session policy.
Data processingCanada and EU deployments are planned with a non-US identity processor requirement. Production evidence is pending.Google’s privacy page describes US-only processing for Firebase Authentication. Confirm the terms of the exact identity service you intend to use.

Google’s Firebase and Identity Platform comparisonManaging Identity Platform tenantsFirebase custom claimsFirebase session managementFirebase privacy and data locations

Why Firebase fits many app teams

A team launching a mobile app can use the Firebase client SDKs and manage users with the Admin SDK. If the same team later needs MFA, SAML or a tenant-specific identity provider, it can evaluate the Identity Platform upgrade while keeping its existing Firebase services. Google documents programmatic tenant and provider management for teams that need to automate setup.

Firebase custom claims can carry access attributes into verified ID tokens and, where appropriate, Firebase Security Rules. This is a useful primitive for application authorization. Design the authoritative company membership separately when access can change frequently, and decide when a current token must be checked again after a membership change.

Google’s Firebase and Identity Platform comparisonFirebase custom claimsManaging Identity Platform tenants

When the workspace matters more than the identity tenant

Consider one person who uses your product personally, administers a company workspace and helps a reseller onboard another customer. The product needs to decide what that person can do in each workspace. Identity tenants can isolate user pools and configure different providers. Workspace membership models which business accounts the person can act for and which permissions apply when they switch.

Covenant implements that relationship in its local console. A personal account can accept a company invitation, an admin can read company activity, and a reseller delegate has access only to assigned companies and a limited invitation workflow. If you already have this model in a Firebase-backed app, compare the cost of retaining it with the value of using Covenant’s prebuilt views and checks in a pilot.

Managing Identity Platform tenants

Check the location of identity processing

Google’s Firebase privacy documentation says Firebase Authentication processes data in the United States. Ask for the data-processing terms for the exact identity service under evaluation, even when another Firebase product offers regional storage. Confirm how sign-in records, recovery and maintenance access fit your policy.

Covenant plans regional identity processing, backups and support access covered by a non-US vendor requirement. Treat that as a deployment and procurement requirement. Before production, check the processor inventory, demonstrate an in-region restore, and review the results for the region that would handle your users.

For budgets, Google’s published Identity Platform pricing uses monthly active users and distinguishes provider tiers, including SAML and OIDC. Phone or SMS can have separate charges depending on the flow and destination. Price the features you actually need and include implementation work for memberships, reseller permissions and operations. Pricing reviewed November 20, 2026.

Firebase privacy and data locationsGoogle Identity Platform pricing

What a migration needs

  1. Inventory Firebase user IDs and linked providers

    Identify where Firebase UIDs and tenant IDs appear in database records, Security Rules and back-end authorization. Review export formats and password hash portability before deciding how to migrate existing accounts.

  2. Plan the client and session change

    Test how web and mobile apps obtain and verify their new credentials. Decide when old refresh tokens must be revoked and how clients behave during a rollback.

  3. Validate the target with synthetic identities

    Rehearse a consumer sign-in, company invite, reseller handoff and revocation. Use realistic workspace memberships and verify what happens if a user has to recover access or enroll a new passkey.

Firebase Auth import and exportFirebase session management

Which fits your team?

Choose Firebase Authentication when managed sign-in and Firebase integration are the immediate priorities. Evaluate Identity Platform when you need its enterprise sign-in or tenant features. Pilot Covenant when company and reseller relationships are core to your product or your procurement rules require a verified non-US identity-processing chain.