Configure the DuckDB provider

Use this page when an explicit DuckDB provider selection reports a missing or unusable installation. You need a trusted executable artifact, its checksum, and a host that supports the artifact’s protocol.

Check availability

The official provider ID is stokaro/ptah-duckdb-plugin. Its designated repository is stokaro/ptah-duckdb-plugin. The catalog recognizes duckdb as engine names.

Official DuckDB executable artifacts remain under development in issue #4204. The catalog reserves this identity; it does not provide a released download.

This provider is optional. Installing the main Ptah binary does not establish a DuckDB provider installation.

List the catalog without executing providers:

ptah providers list --json

The DuckDB entry reports its provider ID, repository, setup link, and distribution policy. An empty installations array means this invocation selected no manifest.

Declare a trusted installation

When you have a compatible DuckDB artifact, verify its publisher and checksum before authorizing it. Create an explicit manifest using the executable-provider procedure. Set provider_id to stokaro/ptah-duckdb-plugin and declare the canonical engine duckdb. Copy the artifact’s actual aliases into engines[].aliases.

Verify the installation

Given the reviewed manifest at providers.json, run:

ptah providers check --provider-config providers.json \
  --provider-engine duckdb --json

A successful check reports "status": "compatible". Read the verification contract before treating that result as database capability evidence.

Resolve a refusal

With no configured installation, an explicit selection reports provider_missing, engine ID duckdb, and this setup page. A disabled entry reports provider_disabled. Missing executable bytes, checksum mismatches, startup failures, and incompatible protocols have distinct codes.

Use the failure reference to correct the reported installation state, then repeat the check above.

Use the selected provider

Pass --provider-config providers.json --provider-engine duckdb to supported native schema commands. This explicitly requires the executable provider; an absent or failed installation cannot select an embedded implementation.

The native provider workflow describes inspection, saved plans, application, and its protocol limitations. The catalog does not add provider selection to Atlas-compatible commands or the language server.