Softwr

Cybersecurity · head to head

Sardine vs Semperis

Sardine logo

Sardine

Cybersecurity

Device intelligence and behaviour biometrics for fraud and compliance

From
On request
Rated
-
Full reviewWebsite
Semperis logo

Semperis

Cybersecurity

Identity threat detection and Active Directory forest recovery for AD, Entra ID and Okta, from a privately held US vendor.

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Sardine signal quality depends on the SDK being embedded in your own web and mobile clients, so fraud improvements become dependent on your app release cycle and any coverage gap is a blind spot.; Semperis scope is limited to Active Directory, Entra ID and Okta, so an organisation whose critical identity lives elsewhere gets little from it, and the recovery value declines in direct proportion to how much has already moved off on-premises AD.
  • They diverge on capability: Sardine covers Device intelligence, Semperis covers Active Directory Forest Recovery.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Sardine and Semperis actually diverge.

Attributes where Sardine and Semperis differ
AttributeSardineSemperis
PlatformsWeb, iOS, AndroidWeb

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Cybersecurity).

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 Sardine

  • Device intelligence
  • Behaviour biometrics
  • Scam detection
  • Onboarding risk scoring
  • AML transaction monitoring
  • Dispute and chargeback handling
  • Rules editor

Only in Semperis

  • Active Directory Forest Recovery
  • Malware-free restore
  • Replication-stream monitoring
  • Automated rollback
  • Attack indicator scoring
  • Entra ID and Okta coverage
  • Purple Knight
  • Forest Druid

What people use each for

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

Sardine

  • A neobank losing money to authorised push payment scams where the customer genuinely approved the transfernot Semperis
  • A crypto exchange trying to detect accounts being operated by remote access rather than by their ownernot Semperis
  • A fintech seeing synthetic identity signups that pass document verification but share device characteristicsnot Semperis
  • A lender wanting first party fraud signals at application time that a credit bureau file does not containnot Semperis

Semperis

  • An organisation that cannot answer an auditor or insurer asking how long it would take to rebuild Active Directory after a destructive attacknot Sardine
  • Post-incident recovery where domain controllers are compromised and restoring from system-state backup would reintroduce the attacker's footholdnot Sardine
  • Continuous detection of privileged group changes and directory-level tampering that domain controller security logs missnot Sardine
  • Hybrid estates where AD, Entra ID and Okta all matter and no single tool currently shows changes across the threenot Sardine

Where each one falls short

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

Sardine

  • Signal quality depends on the SDK being embedded in your own web and mobile clients, so fraud improvements become dependent on your app release cycle and any coverage gap is a blind spot.
  • Behavioural and device telemetry collection needs a documented lawful basis under GDPR, and EU privacy reviews frequently delay rollouts that were scoped as engineering work.
  • Pricing is per session or per active user, so a consumer product with many low value sessions pays in proportion to traffic rather than to fraud exposure.
  • As a younger private company it lacks the enforcement-tested audit history that a bank examiner expects, which makes it a harder sell inside a regulated bank than inside a fintech.
  • It is strongest on session-time signals and weaker as a system of record for long horizon AML typologies, so larger institutions end up running it alongside a traditional monitoring platform rather than instead of one.

Semperis

  • Scope is limited to Active Directory, Entra ID and Okta, so an organisation whose critical identity lives elsewhere gets little from it, and the recovery value declines in direct proportion to how much has already moved off on-premises AD.
  • The licence buys tooling, not a proven runbook: forest recovery is only worth what your last rehearsal demonstrated, and a plan that has never been executed end to end in a lab is an untested assumption regardless of what was purchased.
  • It overlaps with backup and directory management products from Quest, Veeam, Commvault and others, so the buyer must argue internally why a dedicated product is needed alongside a backup contract that already claims to protect Active Directory.
  • Running Directory Services Protector well requires someone who understands AD internals, replication metadata and Tier 0 attack paths, and without that person the alerts on privileged changes are either ignored or auto-reverted in ways that break legitimate administration.
  • Licensing is driven by identity object counts, so directories carrying years of stale user accounts and service principals pay for objects that should have been deleted, and the cleanup project that would reduce the bill is the one nobody has time for.

Pricing, plan by plan

Sardine

On request
  • Sardine$undefined/year
    • Priced per user session or per monthly active user
    • Annual contract with volume commitment
    • SDK for web, iOS and Android

Semperis

On request

No published plan breakdown. See the Semperis review.

Which should you pick?

Choose Sardine if

  • You need device intelligence.
  • You work on Web, iOS, Android.
  • You also want behaviour biometrics.
Sardine review

Choose Semperis if

  • You need active directory forest recovery.
  • You also want malware-free restore.
Semperis review

Questions people ask

Is Sardine or Semperis better?
Neither clearly leads. Sardine starts at On request and Semperis at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Sardine or Semperis?
Sardine starts at On request and Semperis at On request.
Does Sardine or Semperis run on more platforms?
Sardine runs on Web, iOS, Android. Semperis runs on Web.
What is Sardine best used for?
Sardine is most often used for a neobank losing money to authorised push payment scams where the customer genuinely approved the transfer, a crypto exchange trying to detect accounts being operated by remote access rather than by their owner, a fintech seeing synthetic identity signups that pass document verification but share device characteristics, a lender wanting first party fraud signals at application time that a credit bureau file does not contain. Of those, a neobank losing money to authorised push payment scams where the customer genuinely approved the transfer and a crypto exchange trying to detect accounts being operated by remote access rather than by their owner are not what Semperis is typically brought in for.
What can Sardine do that Semperis cannot?
Sardine covers Device intelligence, Behaviour biometrics, Scam detection, Onboarding risk scoring. Semperis covers Active Directory Forest Recovery, Malware-free restore, Replication-stream monitoring, Automated rollback.

Answered from the vendors’ own pages

Sardine: Does Sardine do document verification?

It focuses on device, behavioural and transaction signals, and integrates identity verification providers rather than being one. Treat it as complementary to a KYC vendor.

Semperis: Does this replace my backups?

No. It replaces the Active Directory recovery procedure specifically. You still need backups for everything else, and the point of Semperis is that a generic system-state backup of a domain controller is a poor way to recover a forest because it restores the operating system along with whatever compromised it.

Sardine: What does it need from us to work?

An SDK in your web and mobile applications plus transaction feeds. Without the client side collector you lose the signals that differentiate it.

Semperis: Is it useful if we are cloud-only on Entra ID?

Partly. Directory Services Protector covers Entra ID and Okta for change tracking and posture, but the forest recovery product, which is the strongest reason to buy, applies to on-premises Active Directory. A genuinely cloud-only organisation should weigh it against Microsoft's own tooling.

Sardine: Is pricing published?

No. It is quoted, typically per session or per monthly active user with an annual volume commitment.

Semperis: Are Purple Knight and Forest Druid really free?

Yes, both are free downloads with no licence requirement, and they are widely used by organisations that are not Semperis customers. They are also, transparently, the top of the sales funnel.

Semperis: How long does forest recovery actually take?

The honest answer is whatever your rehearsal took. The vendor's case is hours instead of days, and automation genuinely removes most manual steps, but the number that matters for your board is the one from a test in your own environment.

Semperis: Does it require agents on domain controllers?

It collects directory changes from the AD replication stream, which is what lets it see changes that bypass the security log. Deployment details vary by product and version, so confirm the exact architecture against your domain controller change-control rules.

Share

Related pages

More on Sardine

More on Semperis

Keep looking

Other head to heads