Softwr

Cloud · head to head

Longhorn vs Ory Kratos

Longhorn logo

Longhorn

Cloud

Open source distributed block storage for Kubernetes, incubating at the CNCF

From
Free
Rated
-
Full reviewWebsite
Ory Kratos logo

Ory Kratos

Cybersecurity

Headless identity and user management API

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Longhorn there is no vendor and no SLA, so a production incident at three in the morning is your own problem unless you buy SUSE Rancher Prime support separately.; Ory Kratos headless means you build every screen, which is significant work compared with a hosted login page
  • They diverge on capability: Longhorn covers Per-volume controllers, Ory Kratos covers Headless API.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Longhorn and Ory Kratos actually diverge.

Attributes where Longhorn and Ory Kratos differ
AttributeLonghornOry Kratos
Pricing modelOpen source, no licence feeOpen-source self-hosted, with a paid managed network
PlatformsLinux, KubernetesLinux, Docker, Kubernetes, Self-hosted
CategoryCloudCybersecurity

Identical on both: starting price (Free), free tier (Yes), 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 Longhorn

  • Per-volume controllers
  • Synchronous replication
  • Snapshots and backups
  • Volume expansion
  • Disaster recovery volumes
  • Web interface

Only in Ory Kratos

  • Headless API
  • Self-service flows
  • Multi-factor authentication
  • Pluggable identity schemas

What people use each for

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

Longhorn

  • An on-premises Kubernetes cluster with local disks and no SAN that needs replicated persistent volumesnot Ory Kratos
  • Edge sites where shipping a storage array is impractical and three nodes is the whole clusternot Ory Kratos
  • A K3s deployment where the storage layer must be light enough to run alongside the workloadsnot Ory Kratos
  • A team that wants snapshots and S3 backups of persistent volumes without paying per-node storage licencesnot Ory Kratos

Ory Kratos

  • Products needing complete control over the look and flow of authenticationnot Longhorn
  • Applications that must not hand user identity data to a third partynot Longhorn
  • Teams building identity as infrastructure across several servicesnot Longhorn

Where each one falls short

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

Longhorn

  • There is no vendor and no SLA, so a production incident at three in the morning is your own problem unless you buy SUSE Rancher Prime support separately.
  • Synchronous replication across nodes means write latency depends on the slowest replica and the network between nodes, which makes it a poor fit for latency-sensitive databases.
  • Every replica is a full copy, so three-way replication consumes three times the raw capacity, unlike erasure-coded systems that are far more space efficient.
  • It is designed for block storage on modest clusters and does not scale to the node counts or throughput that Ceph or a commercial array handles, so growth eventually forces a migration.
  • Recovery from certain degraded states, such as a volume stuck detaching or replicas failing to rebuild, requires manual intervention and knowledge of Longhorn internals that is not widely held.

Ory Kratos

  • Headless means you build every screen, which is significant work compared with a hosted login page
  • More moving parts than a monolithic IAM: Kratos handles identity, and OAuth2 needs Ory Hydra alongside
  • Documentation assumes real familiarity with identity concepts and is not a gentle introduction
  • Self-hosting identity carries the security and availability burden that hosted providers absorb

Pricing, plan by plan

Longhorn

Free
  • LonghornFree
    • Apache 2.0 licensed, no licence fee
    • Community support via GitHub and Slack only
    • No vendor SLA or escalation path

Ory Kratos

Free
  • Self-hostedFree
    • Full identity server
    • All flows
    • Community support

Which should you pick?

Choose Longhorn if

  • You need per-volume controllers.
  • You want to start without paying.
  • You work on Linux, Kubernetes.
  • You also want synchronous replication.
Longhorn review

Choose Ory Kratos if

  • You need headless api.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want self-service flows.
Ory Kratos review

Questions people ask

Is Longhorn or Ory Kratos better?
Neither clearly leads. Longhorn starts at Free and Ory Kratos at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Longhorn or Ory Kratos?
Longhorn starts at Free and Ory Kratos at Free.
Does Longhorn or Ory Kratos run on more platforms?
Longhorn runs on Linux, Kubernetes. Ory Kratos runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Longhorn for free?
Both have a free tier, so you can try either at no cost before committing.
What is Longhorn best used for?
Longhorn is most often used for an on-premises kubernetes cluster with local disks and no san that needs replicated persistent volumes, edge sites where shipping a storage array is impractical and three nodes is the whole cluster, a k3s deployment where the storage layer must be light enough to run alongside the workloads, a team that wants snapshots and s3 backups of persistent volumes without paying per-node storage licences. Of those, an on-premises kubernetes cluster with local disks and no san that needs replicated persistent volumes and edge sites where shipping a storage array is impractical and three nodes is the whole cluster are not what Ory Kratos is typically brought in for.
What can Longhorn do that Ory Kratos cannot?
Longhorn covers Per-volume controllers, Synchronous replication, Snapshots and backups, Volume expansion. Ory Kratos covers Headless API, Self-service flows, Multi-factor authentication, Pluggable identity schemas.

Answered from the vendors’ own pages

Longhorn: Who do we call when it breaks?

Nobody, unless you buy SUSE Rancher Prime, which includes commercial support for Longhorn. This is the decisive question for production use.

Ory Kratos: Is Ory Kratos free?

Yes, open source and free to self-host. Ory Network is a paid managed service.

Longhorn: How much capacity does replication cost?

Full copies, so three replicas means three times the raw capacity. Budget accordingly rather than assuming erasure coding efficiency.

Ory Kratos: What does headless mean here?

Kratos provides identity flows as APIs and no user interface. You build the login, registration and recovery screens yourself.

Longhorn: Is it suitable for production databases?

For modest workloads yes, but synchronous replication adds write latency and high-transaction databases usually want something faster.

Ory Kratos: Does Kratos do OAuth2?

No. Kratos handles user identity; OAuth2 and OpenID Connect provider functionality is Ory Hydra, a separate component.

Share

Related pages

More on Longhorn

More on Ory Kratos

Keep looking

Other head to heads