vs

Oxigraph vs RDFox

Oxigraph: Small, fast SPARQL database in Rust that embeds in Rust, Python and JavaScript or runs as a server. RDFox: In-memory RDF store with incremental Datalog reasoning, now owned by Samsung.

key differences

  • Licensing: Oxigraph is open source (permissive) (Apache-2.0 OR MIT); RDFox is proprietary (Proprietary).
  • RDFox is built for larger datasets (≤ 10 TB) than Oxigraph (≤ 100 GB).
  • Only Oxigraph has compression, runs in webassembly.
  • Only RDFox has role-based access.

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 rdfox for

  • +Rule-based decision and compliance engines
  • +On-device personal knowledge graphs
  • +Real-time knowledge-graph reasoning
  • +Product configuration and validation

best at · Knowledge graph, Embedded, Edge

overview
Primary model
RDF / Triple Store
RDF / Triple Store
Also supports
–
–
Type
Database engine
Database engine
Status
Active
Active
Developer
Oxigraph community (Tpt)
Oxford Semantic Technologies (Samsung Electronics)
First release
2018
2017
Latest version
0.5.13 (Oct 22, 2026)
7.7 (Sep 29, 2026)
License
Open source (permissive)Apache-2.0 OR MIT
ProprietaryProprietary
Free tier
✓
—
popularity
WhichDB Score
15.1
3.4
Rank
#223
#438
GitHub stars
2K
–
Stack Overflow questions
–
6
scale & guarantees
Comfortable data size
Small (≤ 100 GB)
Medium (≤ 10 TB)
Horizontal scaling
None
None
Multi-region
None
None
ACID
Full
Full
Consistency
Strong
Strong
Schema
Schemaless
Schemaless
Architecture
Embedded, Single node, Client server
In memory, Single node, Embedded, 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, Datalog, OWL 2 RL
Client languages
Rust, Python, JavaScript
Java, C++, Python (REST)
Best for
Knowledge graph, Embedded, Metadata, Scientific
Knowledge graph, Embedded, Edge, Real-time analytics

Oxigraph vs RDFox: FAQ

What is the difference between Oxigraph and RDFox?

Oxigraph: Small, fast SPARQL database in Rust that embeds in Rust, Python and JavaScript or runs as a server. RDFox: In-memory RDF store with incremental Datalog reasoning, now owned by Samsung. Licensing: Oxigraph is open source (permissive) (Apache-2.0 OR MIT); RDFox is proprietary (Proprietary). RDFox is built for larger datasets (≤ 10 TB) than Oxigraph (≤ 100 GB). Only Oxigraph has compression, runs in webassembly.

When should I choose Oxigraph over RDFox?

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 RDFox for rule-based decision and compliance engines; on-device personal knowledge graphs; and real-time knowledge-graph reasoning.

Is Oxigraph or RDFox more popular?

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

Are Oxigraph and RDFox open source?

Yes. Oxigraph is open source. License: Apache-2.0 OR MIT. No. RDFox is proprietary, closed-source software.