# libSQL clients and ORMs

> Status: Coming. A libSQL-compatible HTTP endpoint, and the ORMs that come with it, are planned for v1. They are not available today.

> **Coming.** Gauntlet's [HTTP API](https://gauntlet-db.stavros.xyz/docs/clients/http.md) is its own JSON shape. A libSQL SDK pointed at a Gauntlet node will not work today.

## What is planned

| Item | Plan | What it will add |
|---|---|---|
| libSQL-compatible HTTP endpoint | P10.2 | A route to the existing libSQL client and ORM ecosystem, in the dialect Gauntlet already speaks |
| Certified client and ORM list | P10.8 | One page of what works, what is partial and what is refused, per combination |
| SDK helpers | P10.7 | Retry on `40001` and outcome lookup on `40003`, which no stock driver does |

## Why libSQL and not PostgreSQL

Gauntlet's SQL is the SQLite family. The libSQL protocol carries that dialect, so tools built for it send SQL Gauntlet can run. Promising PostgreSQL compatibility would mean PostgreSQL types, `pg_catalog` and a second SQL dialect; that is not planned for v1. PostgreSQL wire stays a transport.

## Until then

- Use a PostgreSQL driver with hand-written SQL: [PostgreSQL wire](https://gauntlet-db.stavros.xyz/docs/clients/pgwire.md).
- From an edge runtime that has only `fetch`, call the [HTTP API](https://gauntlet-db.stavros.xyz/docs/clients/http.md) directly.

---
Source: https://gauntlet-db.stavros.xyz/docs/clients/libsql