Choose your download.

Axoldb.com is the only official channel for AxolDB native packages. Further distribution of the AxolDB application requires permission under its license. Independent third-party rights and the MIT rights of the separate Skills remain unchanged.

Read the full applicable terms before accepting. No account or email is required. See download privacy and retention and platform scope and limitations.

SHA256SUMS · Release notes

Windows x64

axoldb-0.1.0-developer-preview-win-x64-security-r2-crt-final-r1.zip

474,513,388 bytes

SHA-256: 670a006a41cb6fd49fa18cf81aa5038ba64c7f69d8d72e3b53cbf7a9cfc52949

Set up with an AI assistant

First accept the terms above and download your package. Then use an AI agent with terminal access to your computer. It will verify the package and help set up a separate local instance.

Show full setup prompt

Windows setup prompt — select and copy manually

Help me set up AxolDB 0.1.0-developer-preview on my Windows x64 computer. You need terminal access to this computer. Work step by step and report only what you actually verify.

Before setup, confirm that I personally accepted the applicable terms and downloaded the Windows package from https://axoldb.com/downloads/. If not, ask me to do that there. Do not accept any license, request a download grant or bypass the download authorization for me.

Use this versioned guide: https://axoldb.com/documentation/setup/0.1.0-developer-preview/
Support/evidence boundaries: https://axoldb.com/documentation/release-status/

1. Identify the actual Windows OS and OS architecture. This package is Windows x64, not ARM or macOS. Locate my downloaded archive, or ask only for its path if unavailable. Expected filename: axoldb-0.1.0-developer-preview-win-x64-security-r2-crt-final-r1.zip (474513388 bytes). Before running ANY packaged executable, calculate SHA-256 with Get-FileHash and compare with both the versioned official metadata at https://axoldb.com/releases/0.1.0-developer-preview/SHA256SUMS and this pinned value: 670a006a41cb6fd49fa18cf81aa5038ba64c7f69d8d72e3b53cbf7a9cfc52949. Stop on any mismatch, incomplete download or unexpected package identity.

2. Check the actual host prerequisites. The archive contains the product runtimes, PostgreSQL 16.15, app-local ICU and CRT dependencies. Do not require a development SDK, a separate .NET install, Docker or system PostgreSQL. Native Studio additionally needs Microsoft Edge WebView2 Evergreen and a suitable graphical session. Check for it without silently installing anything. Explain a missing system dependency and obtain my specific permission before installing it. Run as the normal non-elevated owner; do not use an Administrator workaround.

3. Extract the verified complete archive safely into a NEW user-owned program directory, rejecting unsafe archive paths. Choose a NEW, separate absolute instance root under my user application-state directory, with a unique name, and a NEW client connection name. Never reuse the default instance or overwrite an existing install, profile or data directory. Record the chosen paths. If owner-only storage protection fails, stop and explain; do not weaken ACLs.

4. After verification/extraction, inspect the packaged CLI help before using commands. Set $Bundle and $Instance to those exact absolute paths, and $Axol to Join-Path $Bundle 'bin\axol.exe'. Use the documented --local server status/start/trust commands with BOTH --bundle-root $Bundle and --instance-root $Instance and --output json. Start only the new intended instance; Ready alone is not successful setup. Read its non-secret config\server.json for publicHttpsPort and instance identity. Keep the listener loopback-only.

5. Follow the guide's CLI-first connection/bootstrap procedure: create unique safe connection metadata using connection add, the actual https://localhost:<publicHttpsPort> endpoint and the public CA exported by server trust through --ca-file. Keep hostname and certificate verification enabled. Bootstrap requires a private interactive terminal: give me the exact non-secret commands for this instance and ask me to supply the one-time assertion there, outside your transcript. Never run a secret reveal into captured output, request a token/assertion in chat, read private keys, or silently regenerate a consumed delivery. Preserve the bootstrap request ID on an uncertain outcome; do not retry with a new identity blindly.

6. Continue after that step and prove authenticated public reading with credential list --connection <the-new-profile> --output json, then connection test <the-new-profile> --output json and require authentication: succeeded. Do not confuse --local reads, liveness, Ready or a friendly profile name with authenticated access. Do not create example Populations or grant broad permissions just to pass setup.

7. If WebView2 and a graphical session are available, open the same instance with --local studio --bundle-root $Bundle --instance-root $Instance. Follow the guide for private Studio connection/credential input; the CLI credential store is separate from Studio. If you cannot perform a GUI or secret-input action, give me one short precise private step, then resume what you can verify. Never claim you observed a human action you did not observe. Without GUI, report CLI success and Studio not opened.

8. Finish with the install path, exact instance root/ID, localhost endpoint, client profile name, observed authenticated-read result and any pending human step. Give the exact restart/status commands for the SAME roots and the documented safe stop command: & $Axol --local server stop --bundle-root $Bundle --instance-root $Instance --output json. Closing Studio does not stop Server. Do not stop unrelated instances, kill arbitrary processes, delete data, open public ports, disable TLS verification or perform uncontrolled sudo/admin actions.

Operator 0.1.5 is optional guidance only: https://axoldb.com/documentation/agent-skills/ . Do not require or modify a Skill to complete this setup.

Open plain text

Read the versioned setup guide. The prompt does not accept licenses or authorize a download.

Linux x64

axoldb-0.1.0-developer-preview-linux-x64-security-r2.tar.gz

134,942,458 bytes

SHA-256: ec66d658f5630c4136908d8fba07782f4eefdd71d68052b8311dbaf69f995db4

AxolDB Developer Preview License 0.1 — full text

Set up with an AI assistant

First accept the terms above and download your package. Then use an AI agent with terminal access to your computer. It will verify the package and help set up a separate local instance.

Show full setup prompt

Linux setup prompt — select and copy manually

Help me set up AxolDB 0.1.0-developer-preview on my Linux x86-64 computer. You need terminal access to this computer. Work step by step and report only what you actually verify.

Before setup, confirm that I personally accepted the applicable product terms and downloaded the Linux package from https://axoldb.com/downloads/. If not, ask me to do that there. Do not accept a license, request a download grant or bypass the download authorization for me.

Use this versioned guide: https://axoldb.com/documentation/setup/0.1.0-developer-preview/
Support/evidence boundaries: https://axoldb.com/documentation/release-status/

1. Identify the actual distribution/version and architecture with /etc/os-release and uname -m. The package is linux-x64 for x86_64, not ARM, macOS or a Windows executable. The recorded Linux CLI/Server evidence covers Fedora 44, Ubuntu 26.04.1 and Debian 13.7; do not assume another distribution/version, WSL or a desktop is qualified. Explain any different context before proceeding. Locate my downloaded archive, or ask only for its path. Expected filename: axoldb-0.1.0-developer-preview-linux-x64-security-r2.tar.gz (134942458 bytes). Before running ANY packaged executable, calculate sha256sum and compare with both https://axoldb.com/releases/0.1.0-developer-preview/SHA256SUMS and this pinned SHA-256: ec66d658f5630c4136908d8fba07782f4eefdd71d68052b8311dbaf69f995db4. Stop on mismatch, incomplete download or unexpected package identity.

2. Check actual system/runtime prerequisites using the shipped runtime metadata and existing host inspection tools. The bundle includes the .NET runtime and PostgreSQL 16.15; do not require a development SDK, Docker or a separate PostgreSQL installation. The packaged PostgreSQL runtime baseline is glibc 2.36 or newer; this is not proof that every other product dependency is present. Inspect dynamic library availability for the packaged apphost and PostgreSQL. Native Studio additionally needs a graphical session, GTK 3 and WebKitGTK 4.1 (2.40 or later). Do not invent a universal distro package list. Explain each missing dependency and obtain my specific permission before installing it. Work as the normal owner, not root.

3. Safely extract the complete verified tar.gz into a NEW user-owned program directory, preserving executable bits and valid in-tree links and rejecting traversal/unsafe links. Do not overwrite an existing install. Choose a NEW, separate absolute instance root below my user state directory with a unique name and a NEW client connection name; never reuse the default instance. Record paths, and verify bundle-manifest.sha256 with sha256sum --check from the extracted root. Do not weaken owner-only permissions or use chmod 777 to fix a failure.

4. Inspect packaged CLI help before composing commands. Let bundle and instance be those exact absolute paths and axol="$bundle/bin/axol". Use "$axol" --local server status/start/trust with BOTH --bundle-root "$bundle" and --instance-root "$instance" and --output json. Start only this new intended instance; Ready alone is not successful setup. Read non-secret config/server.json for publicHttpsPort and instance identity. Keep listeners loopback-only.

5. Follow the guide's CLI-first connection/bootstrap procedure: connection add with a unique name, actual https://localhost:<publicHttpsPort> endpoint and --ca-file pointing to the public CA exported by server trust. Keep hostname/chain verification enabled. Bootstrap needs a private interactive terminal: give me the exact non-secret commands for this instance and ask me to supply the one-time assertion there, outside your transcript. Do not reveal secrets in captured output, ask for tokens/assertions in chat, read private keys or regenerate a consumed delivery. On an uncertain bootstrap outcome, preserve the original request identity and use documented outcome resolution rather than blindly retrying with a new one.

6. Resume and prove authenticated public reading with "$axol" credential list --connection <the-new-profile> --output json. Also run connection test <the-new-profile> --output json and require authentication: succeeded. A --local read, liveness, Ready or a profile name alone does not prove this. Do not populate a database or grant broad permissions just to pass setup.

7. If a suitable graphical session and Studio libraries exist, open the SAME instance with "$axol" --local studio --bundle-root "$bundle" --instance-root "$instance". Follow the guide's private Studio connection/credential step; the CLI store is separate from Studio. If a GUI or secret-entry action is unavailable to you, give me one short precise private action and then continue what you can verify. Do not claim an unobserved human action happened. On a headless host, report CLI success and Studio not opened; do not install a desktop or change X/Wayland access automatically.

8. Finish with installation path, exact instance root/ID, localhost endpoint, new profile name, authenticated-read result and any pending human step. Give exact same-root start/status commands and safe stop: "$axol" --local server stop --bundle-root "$bundle" --instance-root "$instance" --output json. Closing Studio leaves Server running. Never delete existing data, stop unrelated instances, kill arbitrary PIDs, open public ports, bypass TLS or perform uncontrolled sudo/admin actions.

Operator 0.1.5 is optional guidance only: https://axoldb.com/documentation/agent-skills/ . Do not require or modify a Skill to complete this setup.

Open plain text

Read the versioned setup guide. The prompt does not accept licenses or authorize a download.

Agent Skills — MIT

These separate packages require neither AxolDB product nor Windows CRT acceptance. Their MIT license permits reuse and redistribution subject to its notice requirement. Read the MIT license.

Download Architect 0.1.1 (14,856 bytes)
SHA-256: 2db712a117d2a7bcfd9ff9ce3352b52c1f35a3928966a0f5aab8c2005e153209
Download Operator 0.1.5 (17,511 bytes)
SHA-256: 9f3a89b6106413ab59353c43dc97700cc1b633e8d30551b778785118521cb9f6

Verify and resume

Verify the downloaded size and SHA-256 before extracting. Native authorization lasts five minutes and is held in a secure browser cookie. A transfer already started can finish after expiry; a new or resumed request after expiry requires accepting again. Single byte-range resume is supported while authorization remains valid. Sharing the URL does not grant another browser permission, and this service cannot prevent every copy or unauthorized mirror.