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?

LakeDB targets MySQL and MariaDB. Public packages are produced for macOS Apple Silicon, Windows x64 and Linux x64. Additional architectures require separate builds and validation.

Does LakeDB update automatically?

LakeDB can notify you when a compatible GitHub release is available, but it does not silently install it. Open the release from the notice, close LakeDB and replace or reinstall the application. 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.