Frequently Asked Questions

Frequently Asked Questions

Does LakeDB limit connections or tabs?

No. The current LakeDB build has no artificial limits on connections, tabs or editing.

Are credentials sent to the cloud?

No. Credentials are encrypted locally and connections originate from your computer.

Which databases and platforms are supported?

The supported baseline is MySQL 8.4 LTS and MariaDB 10.11, 11.4 and 11.8 LTS. Public packages target macOS 12+ Apple Silicon, Windows 10 22H2/11 x64, and Ubuntu 22.04/24.04 or Debian 12 x64. See Compatibility for best-effort combinations and feature-dependent limits.

Which LakeDB versions receive fixes?

The latest published build receives bug, compatibility and security fixes. Older lines remain in the version history but are not actively supported. See the Support Policy.

Does LakeDB update automatically?

LakeDB can notify you when a compatible GitHub release is available, but it never installs one without your confirmation. Windows downloads and verifies the setup package, then opens the normal visible installer without closing LakeDB. macOS opens the verified DMG and Linux launches the verified AppImage. Local data is stored separately and migrated in place with a pre-migration snapshot.

Will I lose open tabs after a crash or update?

LakeDB continuously saves recoverable workspace state for every open connection and restores it after normal or unexpected exits. Query results and passwords are intentionally excluded. Keep an independent backup before major operating-system or application changes.

Can I use LakeDB in production?

Yes, with least-privilege users, read-only mode where appropriate and verified backups. LakeDB's confirmations reduce accidents but are not a substitute for access controls and review.