Products

Find the right integration surface.

Compare ABI, Abbey, WDBX, and Quasar by purpose, setup requirements, and implementation limits.

The catalog describes local developer and document-workspace surfaces. Quasar is experimental and requires a separately running local service and provider configuration.

Inspect the source behind this page

Local developer framework

ABI

Explore deterministic persona routing, template completion, and source-defined tools.

Local developer framework

Local deterministic routing and template completion do not establish foundation-model quality. External providers need separate configuration.

Browser document preview

Abbey

Explore a browser document workspace and its optional configured server model-request path.

Browser document preview

Documents are stored in this browser's localStorage. This preview does not establish setup or acceptance for a separate Abbey app.

Implemented Rust components for local integration

WDBX

Store durable records and retrieve vectors with inspectable provenance.

Implemented Rust components for local integration

Storage integrity does not prove the truth of stored statements. The reference cluster protocol does not establish production multi-host operation or sharding.

Experimental local website builder with a browser client

Quasar

Generate a Next.js website and preview it on your own machine.

Experimental local website builder with a browser client

The service defaults to loopback and requires pairing for API operations. Generated project code runs as the operator. Live provider generation remains unverified; remote exposure requires operator-managed HTTPS and network opt-in.

Choose by what you want to do: Get started. Inspect the supporting research collection.