Softwr

Cybersecurity · head to head

IDnow vs Istio

IDnow logo

IDnow

Cybersecurity

Identity verification and qualified electronic signature for regulated European markets

From
On request
Free plan
No
Istio logo

Istio

Developer Tools

A Kubernetes service mesh that adds mutual TLS, traffic control and telemetry between services without changing application code.

From
Free
Free plan
Yes

The short version

  • Istio is free; IDnow prices on request.
  • Only IDnow lists eID and NFC; only Istio lists automatic mutual TLS.
  • Where IDnow falls short: pricing is quoted with an annual volume commitment, so the accreditation advantage comes with a floor you pay whether or not you use it.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which IDnow and Istio actually diverge.

Attributes where IDnow and Istio differ
AttributeIDnowIstio
Starting priceOn requestFree
Pricing modelQuoteOpen-source
Free tierNoYes
PlatformsWeb, iOS, Android, APIWeb
CategoryCybersecurityDeveloper Tools

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 IDnow

  • VideoIdent
  • AutoIdent
  • eSign
  • eID and NFC
  • Bank identification
  • EU data processing

Only in Istio

  • Automatic mutual TLS
  • Traffic splitting
  • Resilience policies
  • Authorization policies
  • Uniform telemetry
  • Ambient mode
  • Gateway API support
  • Multi-cluster mesh

What people use each for

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

IDnow

  • A German bank opening regulated accounts where BaFin requires a recognised identification methodnot Istio
  • An insurer needing a qualified electronic signature that will survive challenge in a European courtnot Istio
  • A telecom operator meeting national SIM registration identity rules across several EU statesnot Istio
  • A lender wanting automated checks for low-risk applicants and video identification only for high-value casesnot Istio

Istio

  • Proving to an auditor that all internal service traffic is encrypted and authenticated, as a platform property rather than a per-team promisenot IDnow
  • Progressive delivery, where releases shift traffic by percentage or header and roll back without a redeploynot IDnow
  • A polyglot estate where implementing retries, timeouts and tracing in every language's client library has already failednot IDnow
  • Connecting several Kubernetes clusters into one addressable service namespace with shared workload identitynot IDnow

Where each one falls short

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

IDnow

  • Agent-led video identification costs several times an automated check and depends on agent availability, so peak-time queues push abandonment up at exactly the moment conversion matters
  • Pricing is quoted with an annual volume commitment, so the accreditation advantage comes with a floor you pay whether or not you use it
  • The product is optimised for European regulatory regimes, so buyers verifying users in North America, Asia or Africa will find coverage and cost less competitive than global specialists
  • Qualified electronic signature is a separate licence from identity verification, which surprises buyers who assumed the accredited identity check made the signature capability included
  • Integration for the regulated flows is heavier than a simple SDK drop-in because the compliant journey, including consent and recording requirements, constrains the user experience you can build

Istio

  • Sidecar mode adds an Envoy container to every pod, which costs CPU and memory per workload and adds a hop of latency in each direction, and it introduces a startup ordering problem where an application container can begin making calls before its proxy is ready
  • Upgrades are projects rather than patches: you run revisioned control planes, canary the new revision and restart every workload to pick up new sidecars, and Istio supports only a narrow band of recent minor versions, so this recurs roughly quarterly for as long as you run it
  • The API surface is large, spanning VirtualService, DestinationRule, Gateway, PeerAuthentication, AuthorizationPolicy, Sidecar and the Kubernetes Gateway API, and a mistake usually appears as a 503 with an Envoy response flag rather than a rejected configuration, so debugging requires Envoy knowledge, not just Istio knowledge
  • Ambient mode removes the sidecar but is a different architecture with its own components and does not cover every feature the sidecar path does, so adopting it is a migration and a re-test of your policies rather than a configuration switch
  • It is Kubernetes-first; adding virtual machine workloads to the mesh is supported but much less well-trodden, so a mixed estate of Kubernetes and VMs ends up maintaining two networking and identity models
  • Below a few dozen services, most of what teams actually want (encrypted internal traffic, retries, weighted rollouts) is available from a cloud load balancer or from Linkerd with a fraction of the components, and at that scale Istio commonly becomes the single largest source of production incidents

Pricing, plan by plan

IDnow

On request
  • IDnow PlatformOn request
    • Per-identification pricing that differs sharply between automated and agent-led methods
    • Annual volume commitment typically required
    • Qualified electronic signature licensed separately

Istio

Free
  • Open SourceFree
    • self-hosted installation
    • service mesh capabilities
    • cloud native computing foundation project

Which should you pick?

Choose IDnow if

  • You need videoident.
  • You work on Web, iOS, Android, API.
  • You also want autoident.

Choose Istio if

  • You need automatic mutual tls.
  • You want to start without paying.
  • You also want traffic splitting.

Questions people ask

Is IDnow or Istio better?
Neither clearly leads. IDnow starts at On request and Istio at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, IDnow or Istio?
Istio has a free tier; the other does not. Paid plans start at On request for IDnow and Free for Istio.
Does IDnow or Istio run on more platforms?
IDnow runs on Web, iOS, Android, API. Istio runs on Web.
Can I use Istio for free?
Yes. Istio has a free tier, so you can try it without paying. IDnow starts at On request.
What is IDnow best used for?
IDnow is most often used for a german bank opening regulated accounts where bafin requires a recognised identification method, an insurer needing a qualified electronic signature that will survive challenge in a european court, a telecom operator meeting national sim registration identity rules across several eu states, a lender wanting automated checks for low-risk applicants and video identification only for high-value cases. Of those, a german bank opening regulated accounts where bafin requires a recognised identification method and an insurer needing a qualified electronic signature that will survive challenge in a european court are not what Istio is typically brought in for.
What can IDnow do that Istio cannot?
IDnow covers VideoIdent, AutoIdent, eSign, eID and NFC. Istio covers Automatic mutual TLS, Traffic splitting, Resilience policies, Authorization policies.

Answered from the vendors’ own pages

IDnow: Why choose it over a cheaper automated vendor?

Because in some European regimes the cheaper vendor is not legally permitted for the transaction. This is an eligibility question, not a quality one.

Istio: Do we need a service mesh at all?

Only if you have enough services, or a compliance requirement, that implementing mTLS, retries and tracing per language has become unmanageable. Below roughly a few dozen services, an ingress controller plus good client libraries usually delivers more reliability for less operational cost.

IDnow: Is the electronic signature included?

No. Qualified electronic signature under eIDAS is licensed separately from identity verification.

Istio: Sidecar mode or ambient mode?

Ambient removes the per-pod proxy and its startup ordering problems and costs less at high pod counts, but it is a newer architecture and does not cover every sidecar feature. New deployments should evaluate ambient first; existing sidecar meshes should treat the move as a migration project.

IDnow: Where is the data processed?

In European data centres, which is a requirement rather than a preference for many of its regulated customers.

Istio: How does it compare with Linkerd?

Linkerd is deliberately smaller, uses its own Rust proxy rather than Envoy, and is quicker to operate; Istio has a far larger feature surface, multi-cluster and VM support, and broader vendor backing. Note that Linkerd's stable distribution builds are commercially licensed by Buoyant, whereas Istio's releases are freely available.

Istio: Who supports it commercially?

Solo.io and Tetrate sell supported distributions and control planes, and Google offers Cloud Service Mesh as a managed option. The upstream project itself is CNCF-governed with community support.

Istio: Does it work outside Kubernetes?

Partly. Virtual machine workloads can be added to a mesh, but the tooling, documentation and community experience are heavily Kubernetes-centred, so a VM-majority estate is fighting the grain of the project.

Share

Related pages

Other head to heads