ArcadeDB

ArcadeDB is an open-source database engine that brings several data models and query languages into one system. It suits teams building graph-heavy, analytics, or AI-related applications that want to run their own database. The core product is free without usage caps; paid plans buy support commitments, not extra database features.

Overview

ArcadeDB can store graph, document, key-value, full-text search, vector, and time-series data in one engine. That breadth can reduce the need to coordinate separate database systems, especially for projects that combine connected data with search or analytics. The trade-off is that a focused database may be a better fit when an application has just one narrow workload.

The project is led by Arcade Data Ltd, a private company based in London. Its stated use cases range from knowledge graphs, fraud detection, and recommendations to real-time analytics, customer 360, supply-chain analytics, GraphRAG, and AI/ML feature stores.

Explore Multimodel Databases, Graph Databases, and Database Software for related categories.

Key features

• Multiple data models: Graph algorithms and vector search sit alongside document, key-value, full-text, and time-series storage. This combination is useful when an application needs to relate records and search across different kinds of data without splitting them between engines.
• Several query options: ArcadeDB supports SQL, OpenCypher 25, Gremlin, GraphQL, MongoDB query language, and a native Java API. The range can ease adoption across teams and existing applications, though it also means teams should settle on consistent query practices.
• Transactions and distributed operation: The database provides ACID transactions for single-node and distributed deployments, and uses Raft consensus to maintain consistency across servers. Its persistent write-ahead journal and rollback of uncommitted work after a crash are relevant safeguards for transactional workloads.
• Flexible deployment and compatibility: It can run embedded in Java applications or as a standalone server, with installation options including Docker, GitHub binary, Maven, and Kubernetes. HTTP/JSON support and compatibility with Postgres wire, Redis, and MongoDB protocols broaden integration choices.
• Migration support: Built-in importers for Neo4j and OrientDB give teams moving from either system a more direct starting point.

Pricing

The full database is free for any usage under the Apache 2.0 license, with no usage limits or feature gating. That makes Community unusually straightforward for teams that can rely on community help; the paid tiers matter when response commitments, patch handling, or escalation are operational requirements. Support prices are charged per server each month, so costs rise with server count.

Silver is the entry point for teams that want a defined response target and patch backports without paying for higher-tier escalation or round-the-clock coverage. Gold adds guaranteed backports and escalation management, while Platinum is aimed at teams that need critical coverage and an ongoing technical relationship. The separate Studio AI Assistant license offers query and schema help, but it does not unlock additional database capabilities.

Platforms

ArcadeDB supports API, Linux, macOS, self-hosted, web, and Windows environments. The latest release, 26.9.1, provides Linux, macOS, and Windows downloads.

Who it's for

ArcadeDB is a strong fit for teams consolidating graph, search, vector, and other data models, particularly when they need transactions, distributed deployments, or several query languages. Its free, unrestricted core also suits organizations able to operate the database themselves. Teams that require guaranteed support should budget for per-server subscriptions; those seeking a managed service are not specifically addressed by these deployment options.

Pros and cons

Pros

• Unrestricted free core: Apache 2.0 licensing and no usage or feature limits let teams use the full database without a paid tier.
• Broad model and query coverage: Combining six data types with multiple query languages can avoid maintaining separate systems for mixed workloads.
• Deployment and migration flexibility: Embedded and standalone modes, multiple installation routes, protocol compatibility, and Neo4j and OrientDB importers give teams several paths to adoption.

Cons

• Support can become a substantial operating cost: Paid support is billed per server per month, and higher response commitments start at $599 a month.
• Community support has no stated response commitment: Teams that need predictable incident response must move beyond the free plan.
• The product's breadth may be unnecessary for narrow workloads: A specialized database may be a better choice if an application needs only one data model.

Alternatives

• LadybugDB is a free option with an MIT-licensed codebase and pre-compiled binaries; consider it when that licensing model is a better fit.
• Memgraph offers a free, open-source in-memory graph database with ACID transactions and on-disk persistence; it is worth considering for a graph-focused workload.
• NebulaGraph has a free Apache 2.0 open-source edition with a subset of core features; choose it if that edition's scope fits.
• AllegroGraph has a free tier capped at 5 million triples and a customized-quote Enterprise plan; it may suit projects that fit that free cap or want a quoted enterprise tier.
• OrientDB offers a free Community distribution and Basic support at €1,000 a month; consider it if that distribution or support option fits your needs.
• TypeDB offers a managed Explore tier with 10 GB storage, 8 GB RAM, and 2 vCPUs; it is an option for teams seeking a managed dedicated database with those resources.
• Eclipse RDF4J is a free open-source Java framework whose latest release requires Java 25 or newer; consider it when a Java framework is the preferred form.
• GraphDB has a free tier with one parallel query and five repositories; it may work for projects whose needs fit those limits.

Verdict

Choose ArcadeDB if your application needs several data models, broad query-language support, and the option to run a full-featured database without license or usage caps. Its strongest case is the combination of that unrestricted core with flexible deployment and transactional, distributed operation. Look elsewhere if you need a narrower specialist or cannot operate the database without support commitments priced per server.