ArcadeDB
8.3#1 in graph databasesFrom $19.99 a monthFree planWebAPILinuxmacOS
VisitArcadeDB vs TerminusDB
TerminusDB
6.2#21 in graph databasesFree planFree planWebAPILinuxSelf-hosted
VisitWhat both publish
| Fact | ArcadeDB | TerminusDB |
|---|---|---|
| Deployment | ArcadeDB can run embedded in Java applications or as a standalone server and can be installed using Docker, a GitHub binary, Maven, or Kubernetes. | The quickstart runs TerminusDB in Docker, and the documentation also describes building from source on Linux or macOS and running it on Kubernetes. |
| Product | ArcadeDB is an open-source multi-model database that stores graph, document, key-value, full-text search, vector, and time-series data in one engine. | TerminusDB is an open-source document graph database that stores JSON documents in a schema-enforced graph and includes Git-like version control. |
| Security | The maker describes a persistent write-ahead journal and automatic rollback of uncommitted transactions after a server crash. | TerminusDB provides role-based access control using users, roles, capabilities, and resource scopes. |
| Support | Paid support subscriptions include guaranteed response-time SLAs, with response targets and coverage varying by plan. | The official site directs users to the TerminusDB community on Discord and to GitHub for other ways to connect. |
| Transactions | ArcadeDB states that it provides full ACID transactions for single-node and distributed deployments. | The documentation says commits are ACID transactions and schema validation is enforced on every write. |
ArcadeDB plans
- CommunityFree
- Silver$299 a month
- Gold$599 a month
- Platinum$1,499 a month
- Studio AI Assistant$19.99 a month
TerminusDB plans
- TerminusDB Open Source Community VersionFree
Pick ArcadeDB if…
It suits developers who need several data models in one database or need graph, document, vector, and time-series capabilities together. Teams wanting support with stated response targets can consider the paid subscriptions.
Pick TerminusDB if…
It suits developers and data engineers working with auditable data lineage, complex domain models, collaborative data workflows, or structured content that changes over time. Teams focused on relational analytics, mature ORMs, or a very large extensions ecosystem may find PostgreSQL better suited to those needs.