arcadedb (native build)
This is arcadedb, the native build of the ArcadeDB Python bindings, and the default choice for scripts, notebooks, tests, CLIs, serverless functions and agents. Its sibling arcadedb-jvm runs the Java engine on a bundled JVM: use arcadedb-jvm for heavy, long-running loads, where the JIT compiler makes the engine faster over time, and when you need the Java-object APIs. Both packages import arcadedb and have the same public API. Install one, not both. Which package?
ArcadeDB (SQL, openCypher, document, graph, vector, time series) runs in your Python process without a JVM and without JPype. The engine is compiled ahead of time with GraalVM Community Edition into a shared library (libarcadedb.so, .dylib or .dll), and Python loads it with ctypes. It starts in milliseconds and has a small memory footprint.
Transition note: the first release of this layout is 26.11.1. Until
arcadedbpasses its readiness bar, it may appear only as pre-releases,26.11.1.devN. Install those withuv add --prerelease allow arcadedb. Report problems at https://github.com/ArcadeData/arcadedb-python/issues and say that you use the native build.
Install
uv add arcadedb
Optional extras for the columnar helpers: [numpy], [arrow], [pandas], [polars].
Old names: this package was formerly arcadedb-embedded-native, imported as arcadedb_native. The old project is archived on PyPI: it gets no new releases and no shim. A last release of the JVM project arcadedb-embedded will install this package.
If arcadedb-jvm is installed in the same environment, import arcadedb raises an ImportError that names both packages. Run uv remove arcadedb arcadedb-jvm, then install the one you want.
Use
import arcadedb
print(arcadedb.__backend__) # "native"
with arcadedb.create_database("/tmp/demo") as db:
db.schema.create_vertex_type("Person")
with db.transaction():
db.command("sql", "CREATE VERTEX Person SET name = ?", "Ada")
print(db.query("sql", "SELECT FROM Person").to_list())
arcadedb.__backend__ is native for this package and jvm for arcadedb-jvm. arcadedb.__version__ is the package version.
What is in the wheel
- The shared library with the ArcadeDB engine: SQL and openCypher, the document, graph, key/value, vector and time series models, ACID transactions, and the in-process server with its HTTP API and the Postgres, Redis and Bolt wire protocols.
- The Python API on top of it, loaded with
ctypes. - Not in the image: gRPC, the MongoDB wire protocol, Raft/HA and Gremlin.
- No polyglot scripting languages (
jsorpythonas query languages, script triggers, polyglot functions). The polyglot engine is switched off at start-up (arcadedb.polyglotEngineEnabled=false), so the first database open writes nothing at WARNING.
Platforms
CPython 3.11 to 3.15. One wheel per platform serves every Python version, because the library is loaded with ctypes and is not compiled against CPython. The images are built for the baseline CPU of the platform (-march=compatibility), so they do not need a special instruction set. On 3.15 the CI runs a subset of the tests, because jpype1 and ladybug, two dependencies of the full test suite, have no 3.15 wheel yet.
| Platform | Wheel tag | Note |
|---|---|---|
| Linux x86-64, glibc 2.28+ | manylinux_2_28_x86_64 |
RHEL 8 and Rocky 8, Debian 10, Ubuntu 20.04 and newer |
| Linux arm64, glibc 2.28+ | manylinux_2_28_aarch64 |
|
| macOS arm64 | macosx_<minos>_arm64 |
|
| Windows x64 | win_amd64 |
The newest wheel. It is built in CI, and its test run is the least proven of the four |
Intel macOS, Windows arm64 and musl-based Linux (Alpine) are not built and not supported. On an Intel Mac use Docker or a Linux virtual machine; on Alpine use a glibc image such as python:3.12-slim.
Not available or not yet
- JVM-only APIs do not exist:
get_java_database()and the otherget_java_*calls,start_jvm(),jvm_kwargsand JVM options. There is no JVM. Usearcadedb-jvmif you need them. - A few API calls raise
NotOnNativeYet(aNotImplementedError) instead of misbehaving:AsyncExecutor.transaction,find_nearest_approximateover product quantization,get_metadataof a foreign index, andget_stats. - Free-threaded Python (3.14t) runs a subset of the tests in CI; it is informational and does not gate a release.
The bindings' own tests run against the installed wheel (the parity run). What does not pass is the list above, or JVM-only by nature.
Licence
Apache-2.0 for ArcadeDB and these bindings. The library also contains the GraalVM Community Edition runtime and JDK class library code, licensed GPLv2 with the Classpath Exception, plus the Apache/BSD/MIT/UPL/EDL third-party Java libraries listed in THIRD_PARTY_NOTICES.md. All texts and the source locations are in the wheel's *.dist-info/licenses/.
Metadata
Release files for arcadedb 26.11.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| arcadedb-26.11.1-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for arcadedb-26.11.1-py3-none-win_amd64.whl |
| arcadedb-26.11.1-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details for arcadedb-26.11.1-py3-none-manylinux_2_28_x86_64.whl |
| arcadedb-26.11.1-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details for arcadedb-26.11.1-py3-none-manylinux_2_28_aarch64.whl |
| arcadedb-26.11.1-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for arcadedb-26.11.1-py3-none-macosx_11_0_arm64.whl |
Total release size: 267.5 MB
Release files / arcadedb-26.11.1-py3-none-win_amd64.whl
| Download URL | arcadedb-26.11.1-py3-none-win_amd64.whl |
|---|---|
| Size | 66.7 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6fc25de6d6e2cc71a72958507c26dfb5f6994497584761e24969f4fa6b30f5b6
|
|
BLAKE2b-256 checksum How to use checksums |
9cc610e86f5ee993b26a0ca5e9eb946e5021c4a53b419383c40966e384e449ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / arcadedb-26.11.1-py3-none-manylinux_2_28_x86_64.whl
| Download URL | arcadedb-26.11.1-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 65.9 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
3baccb356e5b48425c7d1c7d6f916b3a646a8429cf82ae595bcecdb9e30c8c54
|
|
BLAKE2b-256 checksum How to use checksums |
fa8bb8cf1fb49091d6adce12c1411ca30d5313d8c18f309abb35803abad91f77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / arcadedb-26.11.1-py3-none-manylinux_2_28_aarch64.whl
| Download URL | arcadedb-26.11.1-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 67.1 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
f5744397116cb64855ce4e9f6a393dbe87e1a4435cb88b6974997ea50a5591ff
|
|
BLAKE2b-256 checksum How to use checksums |
d1661dd276c628f2f6e8fbfcb49378ed1d665b674f051aa937d7387d0bc30bc6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / arcadedb-26.11.1-py3-none-macosx_11_0_arm64.whl
| Download URL | arcadedb-26.11.1-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 67.7 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6703b7df8a4cad0f644752b856141abb153192d6522e1deb0564bf40dc19f8f4
|
|
BLAKE2b-256 checksum How to use checksums |
8384b014b5603941c4a91922572f3124b143f480ff9a3ad12e9e8056db166faa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for arcadedb 26.11.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 4 files in this release have been uploaded with provenance metadata.
Attestation for arcadedb-26.11.1-py3-none-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.