// sqlly embedded

Embed a SQL editor in your web app

Q: How do I embed a SQL editor in a web app?

The practical route is a self-hosted browser workbench: run the SQLly Embedded bridge next to your databases, define per-group connection profiles, and mint a short-lived launch token per user. The browser never receives a database password.

Q: Can the browser hold database credentials?

No. Anything in the browser is visible to the person using it. Credentials must live server-side; the client receives only connection names and a secret-free launch token.

Q: Is SQLly Embedded white-label?

The hosting is: your domain (unlimited subdomains), your sign-in, your page. The workbench UI itself is SQLly's, not a rebrandable SDK.

A complete SQL workbench on your domain, behind your sign-in — with every database password kept on your server.

Put a complete SQL workbench on a page of your app — without your database passwords ever reaching a browser.

SQLly Embedded is the browser build of SQLly plus a bridge you run next to your databases. Your users get the editor, IntelliSense, explorer, execution plans and results grid on your domain; your server keeps every credential.

Why teams look for an embeddable SQL editor

SaaS products, support desks, customer portals and internal-tools teams all hit the same wall: users need to query real databases, and building an editor, a safe query API, a results grid and safety limits from scratch is a product of its own. The shortcut is embedding a self-hosted workbench that already solved all four.

What your users get

A real SQL IDE, not a text box

Schema-aware IntelliSense that writes JOIN clauses from your foreign keys, an object explorer, execution plans and a grid that streams million-row results without freezing the tab.

30 databases, one integration

SQL Server, PostgreSQL, MySQL and MariaDB, SQLite, DuckDB, ClickHouse, Oracle, libSQL/Turso, Redis and more — every engine SQLly supports, behind one bridge.

Safety built in

SELECT-only profiles enforced before a query reaches the database, confirmation on destructive SQL, query audit log — the guardrails that make a SQL surface safe to hand to customers.

How it works, in three steps

Run the bridge on a server you control. It holds your credentials and checks your license — connected licenses check in with sqlly.app; offline licenses never call home.
Define profiles — the connections, databases and labels each group of users sees. One profile per team, tenant or plan.
Mint a launch token per signed-in user from your backend, and serve the page. The browser only ever sees names — never a password.

The full walkthrough with working code for every step is in our guide: How to embed a SQL editor in your web app, and the quick start gets a sample app running in minutes.

Pricing

Yearly, priced by users connected at a time — not named seats, so today's five can be five different people tomorrow:

Users at a time	Connected	Offline
5	$200/yr	$500/yr
25	$500/yr	$1,000/yr
100	$2,000/yr	$5,000/yr

Every license covers one domain with unlimited subdomains and four tabs per user. Every account includes a free three-month, single-user trial, and companies under $5M revenue can ask for a free license. Details on the pricing page.

What it is not

Not hosted. The page, the bridge and the databases are yours; SQLly hosts only the license check.
Not a rebrandable widget. Hosting is white-label — your domain, your auth, your page — but the workbench UI is SQLly's.
Not single sign-on. Your app decides who a user is and mints the token; the bridge trusts it.

Get started

Register for the free trial, follow the quick start with the included sample admin app, and see SQLly running inside your own app this afternoon. Questions first? The Embedded overview covers the architecture.