Softwr

Machine Learning · head to head

Ray vs Turso

Ray logo

Ray

Machine Learning

Scale AI and Python applications

From
Free
Free plan
Yes
Turso logo

Turso

Databases

SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.

From
Free
Free plan
Yes

The short version

  • Ray is free; Turso starts at $4.99/mo.
  • Only Ray lists distributed computing; only Turso lists per-tenant databases.
  • Where Ray falls short: windows support is beta and multi node Ray clusters are untested on Windows.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Ray and Turso actually diverge.

Attributes where Ray and Turso differ
AttributeRayTurso
PlatformsLinux, macOS, WindowsWeb
CategoryMachine LearningDatabases

Identical on both: starting price (Free), pricing model (Freemium), free tier (Yes).

Not yet recorded: founded for Turso.

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 Ray

  • Distributed computing
  • Ray Train
  • Ray Tune
  • RLlib
  • Ray Serve
  • PyTorch
  • TensorFlow
  • Hugging Face

Only in Turso

  • Per-tenant databases
  • MIT licence
  • Embedded replicas
  • SQLite compatibility
  • HTTP access
  • Branching
  • Point-in-time restore
  • In-process engine

What people use each for

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

Ray

  • Distributed AI model training and servingnot Turso
  • Large-scale data processingnot Turso
  • Reinforcement learning workloadsnot Turso
  • ML inference servingnot Turso

Turso

  • Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Ray
  • Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Ray
  • Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Ray
  • Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Ray

Where each one falls short

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

Ray

  • Windows support is beta and multi node Ray clusters are untested on Windows
  • Windows lacks copy on write forking, which raises memory requirements, and Ray code assumes UNIX filenames
  • Multi node clusters are untested on Apple Silicon Macs
  • The Java API is experimental and community supported only, and requires matching Java and Python versions
  • Python 3.13 support is beta

Turso

  • SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option
  • Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated
  • There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate
  • Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on
  • Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only

Pricing, plan by plan

Ray

Free
  • Open SourceFree
    • Full Ray framework
    • All libraries
    • Community support
  • Anyscale PlatformFree
    • Managed infrastructure
    • Enterprise support
    • SLAs

Turso

Free
  • FreeFree
    • 100 databases
    • 5 GB storage
    • 500M monthly rows read
  • Developer$4.99/mo
    • Unlimited databases
    • 9 GB storage
    • 2.5B monthly rows read
  • Scaler$24.92/mo
    • Unlimited databases
    • 24 GB storage
    • 100B monthly rows read
  • Pro$416.58/mo
    • Unlimited databases
    • 50 GB storage
    • 250B monthly rows read

Which should you pick?

Choose Ray if

  • You need distributed computing.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want ray train.

Choose Turso if

  • You need per-tenant databases.
  • You want to start without paying.
  • You also want mit licence.

Questions people ask

Is Ray or Turso better?
Neither clearly leads. Ray starts at Free and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ray or Turso?
Ray starts at Free and Turso at Free.
Does Ray or Turso run on more platforms?
Ray runs on Linux, macOS, Windows. Turso runs on Web.
Can I use Ray for free?
Both have a free tier, so you can try either at no cost before committing.
What is Ray best used for?
Ray is most often used for distributed ai model training and serving, large-scale data processing, reinforcement learning workloads, ml inference serving. Of those, distributed ai model training and serving and large-scale data processing are not what Turso is typically brought in for.
What can Ray do that Turso cannot?
Ray covers Distributed computing, Ray Train, Ray Tune, RLlib. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

Ray: Is Ray free?

Yes. Ray is free and open source software with over 34,800 GitHub stars and 1,000+ contributors. Users can download and use the Ray framework at no cost.

Source
Turso: Is Turso just hosted SQLite?

Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.

Ray: Is there a paid option for Ray?

Yes. Anyscale, the managed platform built by Ray's creators, offers paid tiers with enterprise features like governance and advanced tooling. Specific Anyscale pricing details are not listed on the Ray website.

Source
Turso: Can I really run a million databases?

That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.

Ray: Can I try Ray with credits?

Yes. New users can try Ray with $100 credit on Anyscale's managed platform to explore the service.

Source
Turso: How do embedded replicas handle read-after-write?

Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.

Turso: What licence is it under?

libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.

Turso: Is Turso still an edge database?

No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.

Share

Related pages

Other head to heads