📌 Known limitations & FAQ (beta) — read before filing

[GamalAnwar]

Querly is in public beta. This issue is the honest, up-front list of current limitations so you know exactly what you're getting. Most of these are deliberate trade-offs for shipping a free, open-source beta early.

🔐 Signing & Gatekeeper

• Querly is ad-hoc signed, not notarized by Apple yet. On first launch (especially macOS Sequoia 15+), Gatekeeper will block it.
• Homebrew install: the cask clears this automatically — no action needed.
• Manual .zip download: run once →

  xattr -dr com.apple.quarantine /Applications/Querly.app
  

• Notarization requires a paid Apple Developer account; it's on the roadmap once there's real usage.

🔑 Credential storage

• Credentials are stored in an AES-256-GCM encrypted file under ~/Library/Application Support/Querly/, not the macOS Keychain — yet. The Keychain path (RELEASE_KEYCHAIN) already exists but is gated behind real code signing.

🧪 Beta / data safety

• Treat it like any open-source DB tool: back up your data, prefer read-only credentials for production, and use Safe Mode (previews every write as SQL before it runs).
• Not yet recommended for mission-critical workflows where data loss is unacceptable.

🖥️ Platform support

• macOS 14 (Sonoma) or later. macOS only — no Windows/Linux (it's native by design).

🗄️ Databases

• SQLite, MySQL, PostgreSQL. Other engines are not supported.

🔒 Privacy

• Zero telemetry, no phone-home, no account, works fully offline. The only network traffic is to the database host you connect to.

---

Found a bug not covered here? Please open a Bug report. Have a question? Use Discussions.