Softwr

Cybersecurity · head to head

Entrust Identity as a Service vs SAP for Government

Entrust Identity as a Service logo

Entrust Identity as a Service

Cybersecurity

Workforce and customer authentication from a certificate authority

From
$2/month
Free plan
No
Full reviewWebsite
SAP for Government logo

SAP for Government

Government

Intelligent Enterprise for Public Sector

From
$8000/month
Free plan
No
Full reviewWebsite

The short version

  • Each has a real cost: Entrust Identity as a Service the application integration catalogue is smaller than that of the dedicated identity vendors, so uncommon SaaS applications more often need custom SAML configuration rather than a template.; SAP for Government sAP's own G-Cloud 14 SuccessFactors pricing document lists Employee Central at £59.76 per user per year for the public sector, with Recruiting and Onboarding modules charged per transaction at £142.00 and £72.00 respectively
  • They diverge on capability: Entrust Identity as a Service covers Multi-factor authentication, SAP for Government covers Financial Management.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Entrust Identity as a Service and SAP for Government actually diverge.

Attributes where Entrust Identity as a Service and SAP for Government differ
AttributeEntrust Identity as a ServiceSAP for Government
Starting price$2/month$8000/month
Pricing modelPer user per monthsubscription
PlatformsWeb, iOS, Android, Windows, LinuxWeb, Desktop, Mobile
CategoryCybersecurityGovernment
FoundedUnknown1972

Identical on both: free tier (No), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Entrust Identity as a Service

  • Multi-factor authentication
  • Single sign-on
  • Adaptive authentication
  • Passwordless login
  • Credential lifecycle
  • Derived PIV credentials
  • Directory integration

Only in SAP for Government

  • Financial Management
  • Procurement
  • Human Resources
  • Analytics
  • Grants Management
  • Microsoft
  • Oracle
  • Third-party Systems

What people use each for

The jobs each tool is most often brought in to do.

Entrust Identity as a Service

  • A government agency needing derived mobile credentials from an existing PIV smart card estatenot SAP for Government
  • A bank that must support hardware tokens for corporate treasury users alongside push authentication for staffnot SAP for Government
  • An organisation already buying Entrust certificates that wants credential issuance and authentication from one vendornot SAP for Government
  • A defence supplier required to use certificate-based authentication that mainstream cloud identity products handle poorlynot SAP for Government

SAP for Government

  • Citizen Servicesnot Entrust Identity as a Service
  • Records Managementnot Entrust Identity as a Service
  • Public Safetynot Entrust Identity as a Service
  • Civic Engagementnot Entrust Identity as a Service

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Entrust Identity as a Service

  • The application integration catalogue is smaller than that of the dedicated identity vendors, so uncommon SaaS applications more often need custom SAML configuration rather than a template.
  • Developer experience for customer identity use cases is behind the specialists, and teams building consumer signup flows will find the APIs and documentation less complete.
  • Advanced capabilities including adaptive authentication and credential management sit above the published entry price, so the two dollar figure rarely reflects what a regulated buyer actually spends.
  • There are two overlapping products, Identity as a Service and Identity Enterprise, and choosing wrongly at the start means a migration later rather than a licence change.
  • Identity governance, access certification and privileged access are not covered, so an organisation with audit-driven access review requirements needs a second vendor alongside it.

SAP for Government

  • SAP's own G-Cloud 14 SuccessFactors pricing document lists Employee Central at £59.76 per user per year for the public sector, with Recruiting and Onboarding modules charged per transaction at £142.00 and £72.00 respectively
  • RISE with SAP is listed on G-Cloud 14 as a subscription requiring a minimum three year contract term, per SAP's own pricing document

Pricing, plan by plan

Entrust Identity as a Service

$2/month
  • Workforce Standard$2/month
    • Multi-factor authentication
    • Single sign-on
    • Directory integration
  • Higher tiers$undefined/month
    • Adaptive risk-based authentication
    • Certificate and smart card credential management
    • Derived PIV credentials

SAP for Government

$8000/month
  • Government Cloud$8000/month
    • ERP
    • Financial Management
    • Analytics

Which should you pick?

Choose Entrust Identity as a Service if

  • You need multi-factor authentication.
  • You work on Web, iOS, Android, Windows, Linux.
  • You also want single sign-on.
Entrust Identity as a Service review

Choose SAP for Government if

  • You need financial management.
  • You work on Web, Desktop, Mobile.
  • You also want procurement.
SAP for Government review

Questions people ask

Is Entrust Identity as a Service or SAP for Government better?
Neither clearly leads. Entrust Identity as a Service starts at $2/month and SAP for Government at $8000/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Entrust Identity as a Service or SAP for Government?
Entrust Identity as a Service starts at $2/month and SAP for Government at $8000/month.
Does Entrust Identity as a Service or SAP for Government run on more platforms?
Entrust Identity as a Service runs on Web, iOS, Android, Windows, Linux. SAP for Government runs on Web, Desktop, Mobile.
What is Entrust Identity as a Service best used for?
Entrust Identity as a Service is most often used for a government agency needing derived mobile credentials from an existing piv smart card estate, a bank that must support hardware tokens for corporate treasury users alongside push authentication for staff, an organisation already buying entrust certificates that wants credential issuance and authentication from one vendor, a defence supplier required to use certificate-based authentication that mainstream cloud identity products handle poorly. Of those, a government agency needing derived mobile credentials from an existing piv smart card estate and a bank that must support hardware tokens for corporate treasury users alongside push authentication for staff are not what SAP for Government is typically brought in for.
What can Entrust Identity as a Service do that SAP for Government cannot?
Entrust Identity as a Service covers Multi-factor authentication, Single sign-on, Adaptive authentication, Passwordless login. SAP for Government covers Financial Management, Procurement, Human Resources, Analytics.

Answered from the vendors’ own pages

Entrust Identity as a Service: Is MFA included or extra?

Multi-factor authentication is included in the workforce bundles rather than sold separately, which is not true of every competitor. Adaptive risk-based authentication sits in higher tiers.

Entrust Identity as a Service: Does it do identity governance?

No. Access certification, role mining and joiner-mover-leaver governance require a separate product such as SailPoint or Saviynt.

Entrust Identity as a Service: Why choose this over Okta or Entra ID?

Almost always because of PKI, smart cards or derived credentials. Without that requirement the mainstream platforms are the stronger general purpose choice.

Share

Related pages

More on Entrust Identity as a Service

More on SAP for Government

Keep looking

Other head to heads