Release 2026.9.1 - Changelog

This release brings Seaquel to the browser. Seaquel Cloud runs the app you already know as a hosted service, and the same build ships as a single self-hostable container for teams that want it on their own infrastructure.

Seaquel Cloud

Seaquel in the Browser — The full Seaquel experience — projects, connections, queries, dashboards, and the schema explorer — now runs as a hosted service. Nothing to install, and your workspace follows you between machines.

Team Accounts — A subscription covers a pool of seats. The subscription owner invites teammates, and each one signs in with their own account.

Self-Hosting

One Container, One Command — Seaquel ships a multi-arch image at ghcr.io/webstonehq/seaquel for linux/amd64 and linux/arm64. The web app and the database service run together in a single container, so getting started is one docker run with a volume mounted at /data.

docker run --name seaquel -p 8787:8787 -v seaquel-data:/data ghcr.io/webstonehq/seaquel:latest

Everything in One Volume — Identity, per-user metadata, and the session-signing secret all live under /data. Back up that volume and you’ve backed up the whole install.

Sensible Defaults — Port, data directory, and session secret all work out of the box. Environment variables exist for reverse proxies, custom domains, shared-cookie subdomains, and multi-replica deployments, but none of them are required for a single-host install.

Docker Compose — A ready-to-use compose file is included for deployments that prefer it, pulling the pre-built image by default or building from source if you’d rather.

Encrypted Credential Vault

Your Passwords Stay Yours — Connection credentials are encrypted in your browser with a passphrase only you know before they’re stored, so the server only ever keeps ciphertext. A leaked database or backup never exposes your passwords. When you open a connection, your browser decrypts the credentials and sends them to the server, which uses them to reach your database.

Air-Gapped Deployments

No Outbound Calls — Self-hosted instances can run fully offline. The subscription owner downloads a signed license bundle from the Seaquel dashboard, transfers it to the instance, and uploads it. From that point, every license check happens locally and the instance never contacts seaquel.app.

Renewals and Revocations — Bundles stay valid for 30 days past the end of the billing period. Each fresh bundle carries the current seat assignments and the full revocation list, so downloading a new one each cycle keeps the install in sync.

Licensing Clarified

The terms are now spelled out explicitly in the README and on the pricing page:

Source code — MIT licensed. Build it, modify it, redistribute it, and run your own builds anywhere, including at work, at no cost. The Seaquel name and logo aren’t part of that grant.
Official desktop binaries — Free for personal, non-commercial use. Commercial use requires a license.
Seaquel Cloud and the self-host image — A subscription is required for all use.

GitHub release notes now carry the same summary, so it’s clear at the point of download.

Help Shape Seaquel — A short feedback prompt now appears in app settings and in the update popover. It’s two questions about what works, what’s missing, and what Seaquel is worth to you — roughly ten minutes, and it directly shapes what gets built next.

Bug Fixes

Fixed the Windows build for the new DuckDB integration

Download the latest version from our homepage to get these improvements.