# orientechnologies/orientdb

OrientDB is the most versatile DBMS supporting Graph, Document, Reactive, Full-Text and Geospatial models in one Multi-Model product. OrientDB can run distributed (Multi-Master), supports SQL, ACID Transactions, Full-Text indexing and Reactive Queries.

Repository: https://github.com/orientechnologies/orientdb
Canonical: https://ross.abutalabs.com/products/orientdb
Homepage: https://orientdb.dev
Language: Java
License: Apache-2.0
License Family: permissive
Topics: orientdb, graph-database, document-database, dbms, nosql, graph-store, multi-master, multi-model-dbms, database, performance, fast, sql
Last push: 2026-08-26T20:43:41+00:00

## Health v2 (maintenance only)
Score: 97/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 93, longevity 100
- inputs: {"age_days": 5015, "days_push": 7, "days_rel": 44, "gap_med": 29, "n_releases_24m": 22}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4983, forks 867 (observed 2026-08-28T04:09:04.211209+00:00)

## What it is
OrientDB is an open-source multi-model NoSQL DBMS written in Java that combines graph, document, full-text, reactive, and geospatial models in a single product. It supports SQL queries, ACID transactions, and distributed multi-master replication with fast record traversal without joins.

## Use cases
- store and query graph data with relationships as physical links
- manage document data alongside graph relationships in one database
- run SQL queries against a NoSQL database
- build a distributed multi-master database cluster
- perform full-text and geospatial searches on operational data
- replace a relational database with a schema-flexible NoSQL alternative

## When to choose
- you need graph and document models in a single DBMS
- you want SQL familiarity with NoSQL flexibility
- you need ACID transactions in a NoSQL store
- you want a self-hosted Java database that runs on any platform

## When to avoid
- you need a mainstream database with a large active ecosystem and vendor support
- you only need a simple key-value or relational store
- you require heavy cloud-managed database operations

## Facets
- artifact type: application
- maturity: maintenance
- function: database, search-engine, serialization
- domain: databases, backend, web-development
- platform: jvm, cross-platform, windows, self-hosted
- tags: graph-database, document-database, nosql, multi-model, sql, acid-transactions, distributed, multi-master, full-text-search, geospatial, search, linux, macos, docker

## Member repositories
- orientechnologies/orientdb (main) score 97

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:04.211209+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:17:41.422222+00:00, confidence not recorded.
  - readme: https://github.com/orientechnologies/orientdb (fetched 2026-08-28T04:09:04.211209+00:00, sha 18e0dab93a34)
  - homepage: https://orientdb.dev (fetched 2026-08-29T08:58:48.400960+00:00, sha da1a8f964fed)
  - site_page: https://orientdb.dev/getting-started (fetched 2026-08-29T08:58:48.410128+00:00, sha 79c435eeb485)
  - site_page: https://orientdb.dev/documentation (fetched 2026-08-29T08:58:48.412385+00:00, sha b113329915f1)
- Data as of 2026-08-30T08:39:29.467469+00:00.