Serverless DuckDB 2

Yes. DuckDB 2 supports managed DuckLake 1.1 on Pro and Dedicated: PostgreSQL holds metadata and managed R2 stores Parquet data. Managed lake storage has its own allowance equal to your plan storage (25 GB on Pro, plus 25 GB per pool block); over it the lake turns read-only until Reclaim storage frees space or a pool block raises the allowance. Query PostgreSQL and MariaDB as read-only sources, join them, and explicitly copy results into lake tables. DuckDB 1 remains available for standalone use and supported sources. Layerbase does not back up a lake: its Parquet objects are never copied, and a DuckDB database with retained lake state, even after detach, is not covered by local backups and blocks lifecycle operations. Databases with only read-only sources back up normally. Two Beta options, still a work in progress, are also open to Pro and Dedicated without enrollment: keeping the lake in your own AWS S3 or Cloudflare R2 bucket, and attaching a PostgreSQL database hosted outside Layerbase as a read-only source.

Yes, on every plan. The owner of a DuckDB 2 database in a personal account can enable a native connection from Connect. It runs over an HTTPS gateway with the Quack extension and a token: copy the snippet into a compatible DuckDB client. Rotate the token or disable native access at any time; enabling, rotating, and disabling briefly restart the database. If the native extension cannot be installed, the database still starts without native access and ordinary SQL over the Postgres-compatible endpoint keeps working.

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.

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.

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).

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.

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.

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 (its network listener and DNS record are removed); you can restore it from the dashboard. Paid plans never auto-archive.

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