Beta Limitations ​
AYB is beta software. The core runtime, APIs, SDKs, and docs are usable today, but a few shipped surfaces intentionally have bounded behavior while the project closes parity and operations gaps.
Managed PostgreSQL extension boundaries ​
Managed PostgreSQL is the zero-config local path. If you need extensions beyond the managed build's default set, such as PostGIS, use an external PostgreSQL instance unless your managed PostgreSQL build explicitly includes them.
Algolia importer automation ​
ayb migrate algolia ships for one-index Algolia record imports into PostgreSQL, with dry-run planning, JSON output, and optional supported synonym import. Algolia query-code migration is documented through AYB's shipped collection list API: search, fuzzy, filter, facets, result highlighting, typo-threshold controls, and operator-defined synonyms. AYB does not translate Algolia ranking rules or hosted index operations.
AYB search relevance is PostgreSQL-native: unweighted full-text search uses PostgreSQL frequency-based ts_rank, and configured weighted search attributes use cover-density ts_rank_cd when weighted search attributes are configured. This is not hosted Algolia relevance and does not ship BM25 or TF-IDF corpus-statistics ranking. Fuzzy typo tolerance comes from pg_trgm similarity, which can affect the effective _rank score returned by list responses. That boundary is suitable for many applications, but teams whose core product needs Algolia-class typo handling plus BM25-style relevance should evaluate that gap against the shipped Search Playground relevance scores before committing to AYB search.
Firebase migration and offline sync ​
The Firebase importer is retired; use PostgreSQL ingest paths or a custom migration. AYB does not provide Firestore-style offline/local-first sync.
Passkey resident-key registration ​
First-factor passkey login is shipped through the JavaScript SDK and React SDK. WebAuthn registration requests now set residentKey: "preferred" and requireResidentKey: false, so discoverable credentials are enabled when the authenticator supports them but are not mandatory for enrollment.
Other-language SDK passkey helpers ​
Search helper parity is shipped across the JavaScript, Go, Python, Dart, Kotlin, and Swift SDK list surfaces, and first-factor passkey wire helpers plus typed synonym methods shipped for Go, Python, Dart, Kotlin, and Swift on 2026-07-10 (contract-tested against the canonical sdk_contract fixtures). Passkey wire helpers are present in the JavaScript, Go, Python, Dart, Kotlin, and Swift SDKs. JavaScript runs browser WebAuthn ceremonies, and Swift ships a system assertion authenticator; remaining native credential ceremonies stay with each application/device platform. Dedicated RPC helpers are present in JavaScript, Python, and Dart; Go exposes Edge Function invocation helpers; and GraphQL helpers are present in JavaScript.
Local Supabase Export Caveat ​
This caveat only affects local development on macOS with Colima and does not affect customer cloud or self-hosted migrations. supabase start may fail on a Docker socket mount for Logflare/Vector; the local workaround is supabase start -x logflare,vector.
Collection list endpoint scope ​
Geo / spatial search is not a shipped parity target on GET /api/collections/{table}; PostGIS-backed geo queries remain an external-extension path rather than a list-endpoint parameter. distinct / dedup is likewise not a shipped list-endpoint parameter; consumers needing distinct result sets rely on SQL views or post-processing.
Dashboard search administration ​
The dashboard search-settings UI is limited to the shipped Search Playground and the per-collection Synonyms tab. A broader admin search configuration screen (index-wide ranking knobs, tokenizer overrides, etc.) is not shipped today.
Screen-spec coverage ​
Screen-spec backfill in docs/reference/screen_specs/ remains partial across the dashboard surface; not every shipped screen has a matching spec yet.