Beta status and support contract

What v0.1.0 beta guarantees, what it does not, and how to deploy accordingly.

Version
Latest
v0.1.0 · latest 2 min read
On this page
  1. Supported for beta use
  2. Known restrictions (ship with the beta)
  3. Out of scope for v0.1.0
  4. Reporting issues

PLOMID v0.1.0 is a beta. It is complete enough to build real applications on a single node, and honest enough to tell you where the edges are. This page is the contract: what you can rely on, what you must work around, and what is out of scope until fixed.

Supported for beta use#

  • Single-node server on loopback or trusted networks with explicit credentials.
  • Full SQL lifecycle: DDL, CRUD, joins, CTEs, window functions, JSON, temporal types, transactions with MVCC snapshots.
  • Dense vector storage and similarity search (exact + HNSW), metadata-filtered search.
  • TLS transport (verified handshake; sslmode=require negotiates successfully).
  • Cold full backup → clean restore, with post-restore verification.
  • psql, Python psycopg, and JavaScript node-postgres drivers (all verified end-to-end).

Known restrictions (ship with the beta)#

Area Restriction
Authorization bypass (critical) Any authenticated user can CREATE/DROP DATABASE without the required privilege check. Do not run shared, multi-user, remote, or cloud deployments as if they were safe until a fix lands and is verified. Single-user local development is the supported profile. See RBAC and Secure remote profile.
ILIKE Parses but behaves as case-sensitive LIKE ('ABC' ILIKE 'abc' → false). Use lower(x) LIKE lower(y) until fixed.
DROP ROLE / DROP USER Unsupported (unsupported DROP object) — plan role lifecycle accordingly.
Vector index in transaction CREATE INDEX ... USING hnsw inside BEGIN ... COMMIT is refused; use autocommit.
Backup model Cold full copies only; no hot, incremental, or point-in-time recovery.
Sparse / multivector DDL parses; no verified SQL write path. Experimental.
GPU No working backend; CPU only.
Distribution Single node; no replication, Kubernetes manifests, or multi-region.

Out of scope for v0.1.0#

Graph queries, blobs, key-value APIs, continuous aggregates/retention automation, hot backups, managed cloud, and any performance or production-readiness promise beyond what this page and the Support matrix state.

Reporting issues#

Security findings follow SECURITY.md (private report, never a public issue). Correctness bugs should include: server version, exact statements, expected vs actual output, and whether the behavior reproduces on a fresh data directory.

Was this page helpful?