Install as a local service
Run KrakenSQL as a per-user macOS LaunchAgent with a configurable data root and localhost-only binding.
Private developer preview
A SQL Server-shaped local database for Mac developers, built around a Rust engine, SwiftUI client, and Apple Silicon-first workflow.
Built for local persistence, schema management, WAL recovery work, and future SQL Server compatibility.
SwiftUI query workspace with object explorer, result grids, saved tabs, and schema reflection.
LaunchAgent install, SQL-authenticated local wire API, and sqlcmd-style tooling without Microsoft dependencies.
Engine first
KrakenSQL starts with the practical gap: Mac developers need a dependable SQL target without spinning up a remote SQL Server or leaving macOS-native tooling behind.
krakensqlcmd -S 127.0.0.1,1433 \
-U sa \
-P "$KRAKENSQL_TDS_PASSWORD" \
-d default \
-i schema.sql
Built for real development loops
Run KrakenSQL as a per-user macOS LaunchAgent with a configurable data root and localhost-only binding.
Use the SQL-authenticated wire API for owned apps while TDS compatibility matures.
Use krakensqlcmd for common sqlcmd-style flags without installing Microsoft tools.
Browse schema, run SQL, inspect result sets, and keep the admin experience native.
Private build channel
KrakenSQL checks the protected Sparkle appcast and installs signed app updates after the update account is saved in the Mac app.
View appcastThe in-app updater downloads the signed package, verifies SHA-256, and opens the installer for the LaunchDaemon-backed server.
Open server packageThe protected JSON feed advertises app build 8 and server build 8 to KrakenSQL clients with a saved update account.
View latest.jsonHonest roadmap
Local service, SQL auth, basic write path, restart persistence tests, and CLI tooling.
Backup/restore, supported SQL matrix, catalog crash tests, and SQL Server client validation.
Roles, TLS, encryption at rest, admin UI, large-result streaming, and migration tooling.
Update account
KrakenSQL is in active development. Build 8 expects the release site to be protected with an update account while licensing is being designed. The Mac app stores that account in Keychain and uses it for app and server update checks.
Basic Auth is the temporary preview gate. Licensing should replace it with account-bound release tokens.