Speed & access

The engineering behind a responsive workbench, remote reach when you need it, and privacy when you do not.

SQLly is built to stay responsive when the work gets serious, reach your database when you are not at your desk, and stay quiet when you have not asked it to connect anywhere.

Where the speed actually comes from

Not from one trick. Four decisions, each of which removes a place where a database tool normally makes you wait:

A real engine

Native protocol drivers and warm pooled connections, on background threads, so completion and a running query do not take turns.

Streaming results

Rows paint as they arrive and spill to disk past a threshold, so a huge answer is a scroll rather than a stall.

GPU rendering

The interface is drawn on the GPU through the platform's own graphics path - not a webview - which is why scrolling a large grid feels like scrolling.

Caching that invalidates precisely

Schema is cached per connection and database and refreshed in the background, so being current does not mean waiting.

Reach and quiet

Reach your database from anywhere - an encrypted tunnel through a relay that routes what it cannot read, with a bridge that dials out so you open no inbound port.
Private by design - no telemetry in the app today, and a short, complete list of the network connections it can make, all of them yours to ask for.

In this section

Dedicated Rust engine — Let a multithreaded, carefully tested Rust engine handle completion and queries without turning every keystroke into a wait.
Unbounded, spill-to-disk results — Stream large results with backpressure and disk spillover so one huge answer does not eat the machine.
Reach your database from anywhere — Reach a database through an end-to-end encrypted relay that can route the traffic but cannot read it.
Private by design — No app telemetry today, full stop. SQLly stays quiet unless you explicitly ask it to connect somewhere.