AxolDB
Documentation

Guide

Install and run

The Windows ZIP and Linux tar.gz path for a self-contained local Developer Preview.

Use official downloads for current availability and release status for exact package identities and support boundaries. Private Actions artifacts are not public downloads. New security revisions are distinct candidates; the older qualified archive hashes do not qualify a later main build.

What the bundle contains

The x64 bundles include AxolDB Server, Axol CLI, Axol Studio, PostgreSQL 16.15 and required product runtimes. They do not require a separate .NET runtime, system PostgreSQL, Docker, Node or npm.

Windows

  1. Verify the adjacent SHA-256, extract the complete ZIP to a user-owned directory and verify the bundle manifest.
  2. In a normal non-elevated session, double-click Start Axol Studio.cmd.
  3. The launcher resolves its own bundle, starts or attaches to the managed Server and uses %LOCALAPPDATA%\axoldb\instances\default.
  4. Windows native Studio requires the Microsoft Edge WebView2 Evergreen Runtime. AxolDB detects it but does not download or install it.

Linux

sha256sum --check axoldb-0.1.0-developer-preview-linux-x64-security-r2.tar.gz.sha256
mkdir axoldb-preview
tar -xzf axoldb-0.1.0-developer-preview-linux-x64-security-r2.tar.gz -C axoldb-preview
cd axoldb-preview
sha256sum --check bundle-manifest.sha256
bin/axol --version
bin/axol server start
bin/axol server status --output json

Native Studio additionally needs a graphical session, GTK 3 and WebKitGTK 4.1 (2.40 or later). The recorded Linux CLI/Server lifecycle matrix covers Fedora 44, Ubuntu 26.04.1 and Debian 13.7 on x86-64; it is not a cross-distribution native GUI certification.

Data is outside the program bundle

The extracted bundle is program material. Database state, configuration, certificates and Studio profile data live under an external instance root. Removing the program bundle is not a backup and does not delete the instance. Back up the complete stopped instance before changing or removing data. Only same-compatible-version bundle replacement is documented; future-version upgrade or restore compatibility is not promised.