Skip to content
LayerbaseLayerbase

Serverless DuckDB

Cloud velocity for analytics, desktop ergonomics for developers, self-hosting with the Layerbase CLI for the ops enthusiast.

Create DuckDB freeCreate an account
Free tier, no credit card

Engine

Choose a database engine to provision.

Learn more about DuckDB on Layerbase

FAQ

Common DuckDB questions

What is DuckDB?

DuckDB is an in-process columnar database built for analytics: fast aggregations and scans over CSV, JSON, and Parquet data, with a SQL dialect close to Postgres. It is the usual pick for ad-hoc analysis, BI dashboards, and OLAP work that does not justify a cluster. Layerbase exposes hosted DuckDB through a PostgreSQL-compatible endpoint with a web SQL console, so psql, Prisma, Drizzle, DBeaver, and other Postgres clients can query it.

Is DuckDB really free on Layerbase?

Yes. Layerbase Free includes DuckDB with no credit card. Your database hibernates after 15 minutes of inactivity and wakes on the next connection. Upgrade only if you need always-on, larger storage, or paid-tier engines.

How do I connect to hosted DuckDB?

Layerbase Cloud exposes DuckDB through a PostgreSQL-compatible endpoint. Use psql, any PostgreSQL driver, Prisma, Drizzle, or a BI tool: the connection string in the dashboard works with all of them. Schema introspection works too, so a client can browse your tables and columns. SSL is required (?sslmode=require).

How do I get data into hosted DuckDB?

Three ways. Drag a CSV, JSON, or Parquet file onto the web query console and it becomes a table. Import an existing .duckdb database file to restore it whole. Or query remote files in place with read_parquet and read_csv_auto over a URL. Standard INSERTs and any PostgreSQL client work too.

Can I use DuckDB locally instead?

Yes. The Layerbase CLI (npm i -g layerbase, run as lbase) runs any database engine locally, including DuckDB, as native processes with no Docker required. Layerbase Desktop wraps the same engine runtime in a GUI. The same database files are portable across local, desktop, and cloud.

What happens to my DuckDB database if I stop using it?

Free databases hibernate after 15 minutes of inactivity, or 30 for MySQL and MariaDB (paid: 6 hours), and wake automatically on connect, typically in 1 to 2 seconds for DuckDB. After 14 days idle on the Free tier, the database is archived (HAProxy listener and DNS removed); you can restore it from the dashboard. Paid plans never auto-archive.

Is DuckDB available on the desktop app?

Yes. Layerbase Desktop runs DuckDB locally with the same dashboard, query console, and connection management as the cloud version. Free for personal use.