vs

Concourse vs TerminusDB

Concourse: Self-tuning document-graph database with automatic indexing, full version history and time-travel reads. TerminusDB: Git-for-data document and knowledge-graph database with branches, diffs and time travel.

key differences

  • Concourse is primarily a document database; TerminusDB is graph.
  • Only Concourse has secondary indexes, full-text search.
  • Only TerminusDB has joins, compression, role-based access, branching, online schema changes.

choose concourse for

  • +Applications that need audit trails and point-in-time reads
  • +Exploratory data where queries are not known in advance
  • +Integrating heterogeneous records with search across them

best at · OLTP, Search, Real-time analytics

choose terminusdb for

  • +Collaborative curation of reference or master data
  • +Auditable knowledge graphs with review workflows
  • +Versioned configuration and product data
  • +Data products that need reproducible snapshots

best at · Knowledge graph, Content, Metadata

overview
Primary model
Document
Graph
Also supports
Graph
Document, RDF / Triple Store
Type
Database engine
Database engine
Status
Active
Active
Developer
Cinchapi Inc.
Gettier (DFRNT AB) and TerminusDB community
First release
2012
2019
Latest version
1.0.6 (Oct 2026)
12.0.8 (Oct 12, 2026)
License
Open source (permissive)Apache License 2.0
Open source (permissive)Apache License 2.0
Free tier
✓
✓
popularity
WhichDB Score
0.9
21.0
Rank
#593
#146
GitHub stars
–
3.5K
Stack Overflow questions
–
2
scale & guarantees
Comfortable data size
Small (≤ 100 GB)
Small (≤ 100 GB)
Horizontal scaling
None
None
Multi-region
None
None
ACID
Full
Full
Consistency
Strong
Strong
Schema
Schemaless
Strict
Architecture
Client server, Distributed
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
CCL
WOQL (Datalog), GraphQL
Client languages
Java
Python, JavaScript, Rust, Elixir
Best for
OLTP, Search, Real-time analytics
Knowledge graph, Content, Metadata

Concourse vs TerminusDB: FAQ

What is the difference between Concourse and TerminusDB?

Concourse: Self-tuning document-graph database with automatic indexing, full version history and time-travel reads. TerminusDB: Git-for-data document and knowledge-graph database with branches, diffs and time travel. Concourse is primarily a document database; TerminusDB is graph. Only Concourse has secondary indexes, full-text search. Only TerminusDB has joins, compression, role-based access, branching, online schema changes.

When should I choose Concourse over TerminusDB?

Choose Concourse for applications that need audit trails and point-in-time reads; exploratory data where queries are not known in advance; and integrating heterogeneous records with search across them. Choose TerminusDB for collaborative curation of reference or master data; auditable knowledge graphs with review workflows; and versioned configuration and product data.

Is Concourse or TerminusDB more popular?

TerminusDB ranks #146 on the WhichDB Score (21.0/100) and Concourse ranks #593 (0.9/100). Popularity is not fit: check the requirements that matter for your project.

Are Concourse and TerminusDB open source?

Yes. Concourse is open source. License: Apache License 2.0. Yes. TerminusDB is open source. License: Apache License 2.0.