Skip to main content
Glama
ArcadeDB Multi-Model DBMS

ArcadeDB Multi-Model DBMS

Official
by ArcadeData

ArcadeDB

ArcadeDB is a Multi-Model DBMS created by Luca Garulli, the same founder of OrientDB, after SAP's acquisition. Written from scratch with a brand-new engine made of Alien Technology, ArcadeDB is able to crunch millions of records per second on common hardware with minimal resource usage. ArcadeDB reuses OrientDB's SQL engine (heavily modified) and some utility classes. It's written in LLJ: Low Level Java - still Java21+ but only using low level APIs to leverage advanced mechanical sympathy techniques and reduce Garbage Collector pressure. Highly optimized for extreme performance, it runs from a Raspberry Pi to multiple servers on the cloud.

ArcadeDB is fully transactional DBMS with support for ACID transactions, structured and unstructured data, native graph engine (no joins but links between records), full-text indexing, geospatial querying, and advanced security.

ArcadeDB supports the following models:

ArcadeDB understands multiple languages:

ArcadeDB key capabilities:

  • 70+ Built-in Graph Algorithms — Pathfinding, centrality, community detection, link prediction, graph embeddings, and more — all available out of the box

  • Parallel Query Execution — SQL queries leverage multiple CPU cores for faster execution on large datasets

  • Materialized Views — Pre-computed query results stored and automatically maintained

  • MCP Server — Built-in Model Context Protocol server for AI assistant and LLM integration

  • AI Assistant — Integrated AI assistant in Studio (Beta) for query help and database management

  • Geospatial Indexing — Native spatial queries and proximity searches with geo.* SQL functions

  • TimeSeries — Columnar storage with Gorilla/Delta-of-Delta compression, InfluxDB/Prometheus ingestion, PromQL queries, Grafana integration

  • Hash Indexes — Extendible hashing for faster exact-match lookups alongside LSM-Tree indexes

ArcadeDB can be used as:

  • Embedded from any language on top of the Java Virtual Machine

  • Embedded from Python via bindings: arcadedb-embedded-python

  • Remotely by using HTTP/JSON

  • Remotely by using a Postgres driver (ArcadeDB implements Postgres Wire protocol)

  • Remotely by using a Redis driver (only a subset of the operations are implemented)

  • Remotely by using a MongoDB driver (only a subset of the operations are implemented)

  • By AI assistants via the built-in MCP Server (Model Context Protocol)

For more information, see the documentation.

Use Cases

Explore real-world examples in the arcadedb-usecases repository — self-contained projects with Docker Compose, SQL schemas, and runnable demos covering:

  • Recommendation Engine — graph traversal + vector similarity + time-series

  • Knowledge Graphs — co-authorship and citation networks with full-text search

  • Graph RAG — retrieval-augmented generation with LangChain4j and Neo4j Bolt

  • Fraud Detection — graph, vector, and time-series signals with Cypher

  • Real-time Analytics — IoT and service monitoring with time-series

  • Social Network Analytics — materialized view dashboards with polyglot queries

  • Supply Chain — multi-tier visibility with PostgreSQL protocol and JavaScript

Getting started in 5 minutes

Start ArcadeDB Server with Docker:

docker run --rm -p 2480:2480 -p 2424:2424 \
           -e JAVA_OPTS="-Darcadedb.server.rootPassword=playwithdata -Darcadedb.server.defaultDatabases=Imported[root]{import:https://github.com/ArcadeData/arcadedb-datasets/raw/main/orientdb/OpenBeer.gz}" \
           arcadedata/arcadedb:latest

Now open your browser on http://localhost:2480 and play with ArcadeDB Studio and the imported OpenBeer database to find your favorite beer.

ArcadeDB Studio

ArcadeDB is cloud-ready with Docker and Kubernetes support.

You can also download the latest release, unpack it on your local hard drive and start the server with bin/server.sh or bin/server.bat for Windows.

Releases

There are four variants of (about monthly) releases:

  • full - this is the complete package including all modules

  • minimal - this package excludes the gremlin, redisw, mongodbw, graphql modules

  • headless - this package excludes the gremlin, redisw, mongodbw, graphql, studio modules

  • base - core engine, server, and network only — excludes all optional modules (console, gremlin, studio, redisw, mongodbw, postgresw, grpcw, graphql, metrics)

The nightly builds of the repository head can be found here.

You can also build a custom distribution with only the modules you need using the Custom Package Builder:

curl -fsSL https://github.com/ArcadeData/arcadedb/releases/download/26.3.1/arcadedb-builder.sh | \
  bash -s -- --version=26.3.1 --modules=gremlin,studio

Available optional modules: console, gremlin, studio, redisw, mongodbw, postgresw, grpcw, graphql, metrics. The builder supports interactive mode, Docker image generation, and offline builds from local Maven repositories.

Java Versions

Starting from ArcadeDB 24.4.1 code is compatible with Java 21.

Java 21 packages are available on Maven central and docker images on Docker Hub.

We also support Java 17 on a separate branch java17 for those who cannot upgrade to Java 21 yet through GitHub packages.

To use Java 17 inside your project, add the repository to your pom.xml and reference dependencies as follows:


<repositories>
    <repository>
        <name>github</name>
        <id>github</id>
        <url>https://maven.pkg.github.com/ArcadeData/arcadedb</url>
    </repository>
</repositories>
<dependencies>
<dependency>
    <groupId>com.arcadedb</groupId>
    <artifactId>arcadedb-engine</artifactId>
    <version>26.3.1-java17</version>
</dependency>
</dependencies>

Docker images are available on ghcr.io too:

docker pull ghcr.io/arcadedata/arcadedb:26.3.1-java17

Building and Testing

Build the entire project (skipping tests):

mvn clean install -DskipTests

Run the full test suite:

mvn test

Some tests are tagged to indicate their cost:

  • slow - functional tests that take noticeably long (large batches, multi-second elapsed time, big payloads)

  • benchmark - microbenchmarks not intended for regular CI runs

To skip these and run only the fast tests:

mvn test -DexcludedGroups="slow,benchmark"

To run only a specific tag (e.g. benchmark tests in isolation):

mvn test -Dgroups="benchmark"

Community

Join our growing community around the world, for ideas, discussions and help regarding ArcadeDB.

Security

For security issues kindly email us at support@arcadedb.com instead of posting a public issue on GitHub.

License and Attribution

ArcadeDB is Free for any usage and licensed under the liberal Open Source Apache 2 license. We are committed to remaining Open Source Forever — see our Governance for the structural guarantees that make this more than a promise. If you need commercial support, or you need to have an issue fixed ASAP, check our pricing page.

For third-party attributions and copyright notices, see:

Thanks To

for providing YourKit Profiler to our committers.

Contributing

We would love for you to get involved with ArcadeDB project. If you wish to help, you can learn more about how you can contribute to this project in the contribution guide.

Have fun with data!

The ArcadeDB Team

Stargazers over time

Stargazers over time

Available Tools

10 tools
execute_commandA

Execute a non-idempotent command against an ArcadeDB database. Use this for INSERT, UPDATE, DELETE, CREATE TYPE, and other write operations. Prefer OpenCypher (language: 'cypher') unless SQL is explicitly requested.

Inputs: command (required), database (required), limit, language.

get_schemaB

Get the full schema of a database including types (vertex, edge, document), their properties, indexes, and inheritance hierarchy.

Inputs: database (required).

get_server_settingsA

Retrieve ArcadeDB server configuration settings. Returns all server-level settings with their current values, defaults, and descriptions. Sensitive values (passwords) are masked. Use this to understand and diagnose server configuration.

Inputs: no named parameters.

list_databasesA

List all databases available to the authenticated user on the ArcadeDB server.

Inputs: no named parameters.

profiler_startA

Start the query profiler to capture query execution data. The profiler records all queries with their execution times and plans. It auto-stops after the specified timeout (default 60 seconds). Use profiler_stop to stop early and get results, or profiler_status to check progress.

Inputs: timeoutSeconds.

profiler_statusA

Get the current status of the query profiler. Returns whether the profiler is recording, and if available, the current or last profiling results including captured queries, timing statistics, and server metric snapshots.

Inputs: no named parameters.

profiler_stopA

Stop the query profiler and return the captured profiling data. Returns aggregated query statistics including execution counts, timing (min/max/avg/p99), and execution plan step costs. Results are also saved to disk for later retrieval.

Inputs: no named parameters.

queryA

Execute a read-only (idempotent) query against an ArcadeDB database. Use this for SELECT, MATCH, and other read operations. Prefer OpenCypher (language: 'cypher') unless SQL is explicitly requested.

Inputs: query (required), database (required), limit, language.

server_statusA

Get ArcadeDB server information including version, server name, available query languages, and HA/cluster status.

Inputs: no named parameters.

set_server_settingA

Update a server configuration setting at runtime. Changes take effect immediately but may not persist across server restarts (depends on the setting). Use get_server_settings first to see available settings and their current values.

Inputs: key (required), value (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a clearly distinct concern: server admin (status, settings), profiler lifecycle (start/stop/status), and database operations (list, schema, query, execute). No two tools overlap in purpose, making misselection unlikely.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern: profiler_start/stop/status, get_server_settings, set_server_setting, list_databases, get_schema, execute_command, query, server_status. The only slight deviation is 'execute_command' and 'query' which use more generic verbs rather than a resource-specific noun, and 'server_status' uses a different word order than get_/set_ prefixes.

    Tool Count5/5

    Ten tools is well-scoped for a DBMS server MCP. Each tool maps to a meaningful operation a client would need: server introspection, config management, profiling, and database CRUD/querying. Nothing feels redundant or missing at the top level.

    Completeness4/5

    The surface covers server status, configuration management, profiling, database enumeration, schema retrieval, and both read and write operations. Minor gaps include no database creation/deletion and no explicit way to retrieve saved profiler results from disk, but the core admin+query workflow is complete.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightning-fast, self-hosted knowledge store and memory layer for AI agents
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server for readonly-first access to Oracle, SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, and Qdrant vector search.
      68 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables persistent agent memory and document ingestion with hybrid vector and lexical retrieval, memory lifecycle management, graph-backed entities, preferences, facts, and cited search through ArcadeDB. It also supports provider-agnostic embeddings and reranking, durable file processing, and optional governance/redaction hooks.
      MIT