AsaDB logo mark AsaDB

Prolog Language SQL Engine

Local-first database software

Official Home Page

Safe operation

Compatibility & Backups

Keep the runtime and all database sidecars together before moving data or upgrading.

Source runtimeA feature-complete SWI-Prolog must be present on PATH. The Linux check tests operating system, CPU, HTTP, crypto, UUID, thread, core, Reservoir, and web capabilities.
Linux targetThe published packages target x86_64/amd64. They are source distributions and do not bundle SWI-Prolog, a browser, or system libraries.
Windows source packageThe current Windows source ZIP expects an installed compatible SWI-Prolog; a native portable executable is a separate build target.
Browser panelAsAPanel includes modern and Firefox-38-compatible interface bundles and is intended for localhost use.
Storage migrationCompatible v2 list-backed user tables can migrate to v3 page storage on boot. Preserve all files and logs first if migration fails.

Database file set

example.asa catalog and versioned database state example.asa.meta durable metadata sidecar example.asa.store/*.heap persistent table heap pages example.asa.store/*.btree persistent index pages example.asa.journal logical compatibility journal example.asa.reservoir/ transient durable bridge jobs, spool, results *.undo / *.mutbak / *.txbak recovery artifacts when present

v1.4.0 production backup: AsAPanel can request a backend-produced .asb backup that carries schema, records, indexes, catalog objects, and SHA-256 integrity data. Restore validates the envelope and rebuilt table/row totals before one transaction commits; creation and restore refuse an already-active transaction. Keep multiple verified copies and test restore regularly—an .asb is a logical backup, not a storage-level hot copy.

Manual preservation rule: when copying an existing live database by hand, preserve the .asa catalog and all matching sidecars together, especially the full .asa.store directory. Do not delete an unreadable database before preserving a copy of the catalog, metadata, journal, and store directory.

Known boundaries

See the primary compatibility matrix ↗ and installation guide ↗ for current upstream detail.