Installation
Download the latest build from the official Releases page. Every package has a matching .sha256 checksum.
Check Compatibility for the supported operating systems, architectures and MySQL/MariaDB server lines.
Download the mac-arm64 DMG or ZIP. Open the DMG, or extract the ZIP, and move
LakeDB.app to Applications. The beta has an integrity-preserving ad-hoc
signature, but it is not yet signed with a trusted Apple Developer ID or
notarized.
On first launch:
- Try to open LakeDB once and close the security warning.
- Open System Settings → Privacy & Security.
- Scroll to Security and choose Open Anyway next to LakeDB.
- Authenticate if requested, then confirm Open.
macOS saves that approval for this copy of LakeDB. Only approve a package downloaded from the official release whose SHA-256 matches.
Download win-x64-setup.exe for a normal installation, or
win-x64-portable.exe to run LakeDB without installing it. The public beta
does not yet have a trusted Windows code-signing certificate. If Microsoft
Defender SmartScreen appears, verify that the file and SHA-256 came from the
official release, select More info, then Run anyway.
Use the .deb package on Debian/Ubuntu-based systems, or the AppImage on other distributions:
chmod +x LakeDB-*-linux-x86_64.AppImage
./LakeDB-*-linux-x86_64.AppImageLakeDB checks public GitHub release metadata at startup by default and shows a notice when a newer compatible version exists. You can also use Help → Check for updates… or disable automatic checks under Preferences.
LakeDB never installs an update without an explicit action. From the update notice you can open the release or download the package for the current platform with progress and SHA-256 verification. On Windows, Open installer launches the normal verified NSIS setup and leaves LakeDB running; complete setup and then restart the app. macOS opens the verified DMG and Linux launches the verified AppImage. Windows users upgrading from 0.11.0 or 0.11.1 should use View release and run the 0.11.2 installer manually once. See Updates, Recovery and Restores for the complete flow.
Local data is stored outside the package, migrations create a safety snapshot and session data is preserved, but keeping an independent configuration backup before a major update is still recommended.