DEV.co
Open-Source CMS · terminusdb

terminusdb

TerminusDB is a distributed graph database with built-in version control (git-like operations) for structured data. It combines document storage with knowledge graph capabilities, supporting REST, GraphQL, and WOQL query languages, and is designed for collaborative data management with temporal reasoning and schema constraints.

Source: GitHub — github.com/terminusdb/terminusdb
3.3k
GitHub stars
141
Forks
Prolog
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryterminusdb/terminusdb
Ownerterminusdb
Primary languageProlog
LicenseApache-2.0 — OSI-approved
Stars3.3k
Forks141
Open issues9
Latest releasev12.0.6 (2026-06-24)
Last updated2026-07-08
Sourcehttps://github.com/terminusdb/terminusdb

What terminusdb is

Written in Prolog, TerminusDB provides ACID semantics with document + RDF graph indexing, arbitrary-precision decimal math (ISO/IEC 21778:2017), Allen interval algebra for temporal queries, and revision control via diff/push/pull operations. Latest v12 (June 2026) adds high-precision math, range queries over succinct data, and enhanced JSON-LD support.

Quickstart

Get the terminusdb source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/terminusdb/terminusdb.gitcd terminusdb# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Collaborative Data Systems with Audit Trail

Organizations needing versioned, auditable data with git-like rollback and branching (e.g., knowledge bases, regulatory compliance records, data lineage tracking).

Knowledge Graph and Linked Data Management

Semantic web projects, ontology-driven applications, and systems linking JSON/JSON-LD documents across domains with reasoning and path queries.

Temporal and Financial Data Processing

Time-series analytics, temporal reasoning, and high-precision numeric calculations for banking, insurance, and scientific domains requiring exact decimal arithmetic.

Implementation considerations

  • Mandatory admin password configuration (TERMINUSDB_ADMIN_PASS env var) required for Docker deployment; plan authentication/RBAC strategy early.
  • WOQL and Datalog query semantics differ significantly from SQL; allocate time for query pattern training and proof-of-concept validation.
  • Schema enforcement via constraints is available but optional; decide upfront whether strict schema or schemaless JSON approach suits your data lifecycle.
  • Temporal queries (ISO8601, Allen algebra) require explicit date/interval typing; data migration from legacy systems may require transformation.
  • Revision history and commit operations add storage overhead; monitor disk usage and retention policies for high-volume insertions.

When to avoid it — and what to weigh

  • Simple CRUD or High-Throughput Write Workloads — TerminusDB's revision-control overhead and Prolog-based engine may not match the raw throughput of specialized OLTP systems (PostgreSQL, MongoDB) for simple transactional loads.
  • Team Unfamiliar with Graph or Logic Programming Concepts — WOQL (Datalog), RDF/semantic reasoning, and git-for-data paradigms require training; steep learning curve for teams used only to SQL and document stores.
  • Closed Ecosystem or Vendor Lock-in Constraints — While Apache 2.0 licensed, the ecosystem (DFRNT Studio, enterprise features) is maintained by a single vendor; deployment outside supported environments requires review.
  • Real-time Sub-millisecond Latency Requirements — Prolog interpreter overhead and revision-control operations (commits, diffs) not optimized for ultra-low-latency queries; unsuitable for high-frequency trading or real-time gaming.

License & commercial use

Licensed under Apache 2.0 (permissive OSI license). Commercial use, modification, and distribution are permitted under the license terms; no explicit commercial restrictions in the Apache 2.0 text.

Apache 2.0 permits commercial use. However, note that the README references an 'enterprise version' with additional features (faster commit history, clustering, backup/restore API) maintained by DFRNT. Verify licensing terms for enterprise features separately; open-source tier licensing alone does not guarantee enterprise feature access or support SLAs.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

No public security audit or threat model provided in data. No mention of encryption at rest/in-transit, authentication mechanisms, or vulnerability disclosure process. Default Docker deployment requires manual password configuration. For sensitive use cases (PII, financial data, regulated systems), conduct security review with vendor and independent assessment before production deployment.

Alternatives to consider

Neo4j

Graph database with mature query language (Cypher), stronger ecosystem, and commercial support options. Lacks git-for-data and temporal reasoning; better for traditional graph patterns and performance-critical use cases.

RDF triplestores (Apache Jena, Virtuoso)

Semantic web native, mature SPARQL support, strong RDF/OWL reasoning. Lack version control, document APIs, and collaborative branching; better for pure semantic web and linked data federations.

PostgreSQL with JSON/JSONB + PostGIS/temporal extensions

Proven OLTP performance, rich ecosystem (pgvector, temporal queries), and mature operational tooling. Requires custom versioning and diff logic; suitable for teams prioritizing stability and SQL familiarity over semantic reasoning.

Software development agency

Build on terminusdb with DEV.co software developers

TerminusDB combines graph storage with versioning and temporal reasoning—ideal for collaborative, auditable, and semantically-rich systems. Review the open-source tier for proof-of-concept; contact the DFRNT team for enterprise clustering and advanced features.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

terminusdb FAQ

Does TerminusDB support transactions across multiple documents?
ACID semantics are mentioned, but exact transaction scope (document-level vs. cross-document) is not detailed in the provided data. Requires review of transaction documentation and testing for multi-document consistency requirements.
Can I query the entire history of a document across all commits?
Yes. Time-travel queries are a core feature (v12 release notes). You can query any state at any commit, and Allen interval algebra enables temporal reasoning over date/time ranges.
What is the difference between 'open-source' and 'enterprise' versions?
README mentions enterprise version offers full JSON-LD/Turtle/RDF-XML support, faster commit history queries, higher write performance, clustering, and backup/restore API. Open-source tier features not fully enumerated; contact vendor for licensing details.
Is TerminusDB suitable for replacing PostgreSQL in my stack?
Not a direct replacement. TerminusDB excels at versioned, semantic, and collaborative data; PostgreSQL excels at transactional workloads and performance at scale. Evaluate specific use case (graph + versioning vs. OLTP throughput) before deciding.

Software developers & web developers for hire

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If terminusdb is part of your open-source cms roadmap, our team can implement, customize, migrate, and maintain it.

Evaluate TerminusDB for Your Data Architecture

TerminusDB combines graph storage with versioning and temporal reasoning—ideal for collaborative, auditable, and semantically-rich systems. Review the open-source tier for proof-of-concept; contact the DFRNT team for enterprise clustering and advanced features.