whichdb
vs

Oxigraph vs QLever

Oxigraph: Small, fast SPARQL database in Rust that embeds in Rust, Python and JavaScript or runs as a server. QLever: Fast open-source SPARQL engine that serves all of Wikidata or OpenStreetMap from one machine.

key differences

  • QLever is built for larger datasets (≤ 1 PB) than Oxigraph (≤ 100 GB).
  • Transactions: Oxigraph offers full ACID; QLever offers limited.
  • Only Oxigraph has transactions, in-memory, runs in webassembly.
  • Only QLever has full-text search, geospatial.
  • Oxigraph can run embedded in your application process.

choose oxigraph for

  • +Embedding RDF in Python or Rust apps
  • +Client-side SPARQL in the browser
  • +Small SPARQL endpoints for datasets and vocabularies
  • +Testing RDF pipelines

best at · Knowledge graph, Embedded, Metadata

choose qlever for

  • +Public SPARQL endpoints for Wikidata, OSM, UniProt
  • +Large read-mostly knowledge graphs
  • +Research on big RDF datasets
  • +Replacing aging Blazegraph deployments

best at · Knowledge graph, OLAP, Scientific

OxigraphSmall, fast SPARQL database in Rust that embeds in Rust, Python and JavaScript or runs as a server.
QLeverFast open-source SPARQL engine that serves all of Wikidata or OpenStreetMap from one machine.
overview
Primary model
RDF / Triple Store
RDF / Triple Store
Also supports
–
–
Type
Database engine
Database engine
Status
Active
Active
Developer
Oxigraph community (Tpt)
University of Freiburg (Chair of Algorithms and Data Structures)
First release
2018
2017
Latest version
0.5.13 (Oct 22, 2026)
0.6.0 (Aug 13, 2026)
License
Open source (permissive)Apache-2.0 OR MIT
Open source (permissive)Apache License 2.0
Free tier
✓
✓
popularity
WhichDB Score
15.1
17.9
Rank
#223
#186
GitHub stars
2K
931
Stack Overflow questions
–
3
scale & guarantees
Comfortable data size
Small (≤ 100 GB)
Large (≤ 1 PB)
Horizontal scaling
None
None
Multi-region
None
None
ACID
Full
Limited
Consistency
Strong
Strong
Schema
Schemaless
Schemaless
Architecture
Embedded, Single node, Client server
Single node, Client server
deployment
Self-hosted
✓
✓
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
✓
—
Edge
—
—
Clouds
–
–
capabilities
Transactions
✓
—
Joins
—
—
Secondary indexes
—
—
Full-text search
—
✓
Vector search
—
—
Geospatial
—
✓
JSON
—
—
Change data capture
—
—
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
✓
—
Durable persistence
✓
✓
Compression
✓
✓
Encryption at rest
—
—
Role-based access
—
—
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
—
—
Offline sync
—
—
Runs in WebAssembly
✓
—
interfaces
Query languages
SPARQL
SPARQL
Client languages
Rust, Python, JavaScript
Any SPARQL client
Best for
Knowledge graph, Embedded, Metadata, Scientific
Knowledge graph, OLAP, Scientific, Geo
Add more to this comparisonNot sure either fits? Try smart match

Oxigraph vs QLever: FAQ

What is the difference between Oxigraph and QLever?

Oxigraph: Small, fast SPARQL database in Rust that embeds in Rust, Python and JavaScript or runs as a server. QLever: Fast open-source SPARQL engine that serves all of Wikidata or OpenStreetMap from one machine. QLever is built for larger datasets (≤ 1 PB) than Oxigraph (≤ 100 GB). Transactions: Oxigraph offers full ACID; QLever offers limited. Only Oxigraph has transactions, in-memory, runs in webassembly.

When should I choose Oxigraph over QLever?

Choose Oxigraph for embedding RDF in Python or Rust apps; client-side SPARQL in the browser; and small SPARQL endpoints for datasets and vocabularies. Choose QLever for public SPARQL endpoints for Wikidata, OSM, UniProt; large read-mostly knowledge graphs; and research on big RDF datasets.

Is Oxigraph or QLever more popular?

QLever ranks #186 on the WhichDB Score (17.9/100) and Oxigraph ranks #223 (15.1/100). Popularity is not fit: check the requirements that matter for your project.

Are Oxigraph and QLever open source?

Yes. Oxigraph is open source. License: Apache-2.0 OR MIT. Yes. QLever is open source. License: Apache License 2.0.