OriginChainDB / Release notes
Migrate keeps a copy in sync until you switch over, and search by meaning and embedding schedules arrive. Also: team access you can shape, Vezual Beta, graph relationships on existing tables, closer PostgreSQL and steadier free and $29/$49 databases.
For PostgreSQL and MySQL sources, Migrate can now keep your OriginChainDB copy in sync with the source until you switch over, right from the console, which shows how far behind the copy is.
PostgreSQL and MySQL sources only. Your source's data is never changed; a PostgreSQL source gains a replication slot and a publication until syncing ends. Very busy MySQL sources can fall behind while syncing.
Search a table's vectors with plain text: the database embeds your question with the same embedder that filled the table and returns the nearest rows, in the console and the API. Embedding schedules keep a table's vectors current automatically, and you can add a vector column to a table you already have.
ALTER TABLE docs ADD COLUMN embedding VECTOR(1536)
Search by text needs a table filled by an embedding run or a migration with a saved embedder. Schedules embed new rows, and optionally changed rows.
Tell Migrate which two columns a table links, and every row, such as each transfer or follow, becomes its own graph edge. Foreign keys that point at an email, a code or any other unique column become graph links too, and full-text search is set up on every table you bring over, including tables keyed by several columns.
Links through unique columns: PostgreSQL, CockroachDB, MySQL and SQL Server sources, and the referenced table must be keyed by one column.
Organize teammates into groups that grant roles, edit custom roles, give a role on chosen databases only, and add deny rules that take one permission away whatever the roles grant. An access review shows every permission a member has and where it comes from, and members see only the databases they can access.
The Usage page now shows measured API requests and data sent out for each dedicated database, alongside storage and compute.
Vezual, for turning your data into dashboards, 3D scenes and shareable live pages, now lives under Plugins in the console and is labelled Beta. If a change fails, your canvas stays as it was; unsaved layouts can be restored after a reload; and a revoked share link stays revoked.
Declare a graph relationship on a table that already holds rows. Existing rows are linked at once, and later inserts, updates and deletes keep the links current. A statement that cannot work is refused with a clear error and changes nothing.
ALTER TABLE shop.orders ADD RELATIONSHIP placed_by (user_id) REFERENCES shop.users
A relationship cannot be removed yet, and the target table must be keyed by a single column.
Full-text and geo indexes now follow every insert, update and delete, through every way of writing, and schema changes keep a table's search setup.
An index created before 18 October 2026 must be created once more to get this behaviour.
More SQL results now match PostgreSQL exactly. Over PostgreSQL connections, psql's \d describes tables as PostgreSQL does, and foreign keys inside a transaction are checked at COMMIT, so rows that point at a missing parent are no longer stored.
A database that is busy, moving or just restarted now answers 503 with a Retry-After header and a short message instead of a raw error, so clients can retry safely. Each free database gets a fair share of its server, so one busy database cannot slow its neighbours, and right after a server is replaced a database quickly says to retry shortly instead of failing slowly.