Operate a local instance

CLI lifecycle

From an extracted Linux bundle:

bin/axol server start --output json
bin/axol server status --output json
bin/axol server stop --output json

From PowerShell in an extracted Windows bundle, stop the launcher’s default instance with:

.\bin\axol.exe server stop --bundle-root . --instance-root "$env:LOCALAPPDATA\axoldb\instances\default" --output json

Closing Studio leaves the Server active. Use public status and stop commands for the exact intended instance; do not guess another instance path.

Safe recovery

During first initialization, cancelling native Studio can leave public status StaleOrInconsistent after attempt-owned processes have exited. This is an accepted Developer Preview limitation, not a cancellation PASS. Inspect status and use public server stop for that exact instance. Do not kill arbitrary PIDs or delete database or PID files as recovery.

Backup, removal and deletion

• Backup: stop Server and make a tested filesystem backup of the complete instance root.
• Remove the program: delete only the extracted bundle after stopping it; external instance data remains.
• Delete an instance: a separate destructive operator action that removes database state, configuration, certificates and local Studio data. It is not an uninstall side effect.