Tessera DB Tutorial: Connect a Postgres Database with Automatic Graph Endpoint Mapping

In the admin dashboard, click Data Sources, then add a new source and choose the PostgreSQL connector.

Fill in host, port, user, password, and database name, using read-only credentials.

Rather than typing table names by hand, click Discover schema. Tessera connects, reads the database's own catalogue, and returns a checklist of every table — each annotated with its columns and any foreign keys.

Foreign-key columns are flagged with an auto graph endpoints badge: Tessera detected the relationship and will turn it into a real graph edge for you, no manual mapping required.

Tick the tables you want — say, a customers table and an orders table — and apply the selection. Tessera confirms how many graph relationships it auto-derived from your foreign keys (for example, orders linked to customers).

For this tutorial, pick polling on a short interval so you can watch it run.

Enable incremental sync and choose a cursor column — a value that only ever increases on insert or update, such as an updated_at timestamp. On each poll, Tessera fetches only the rows newer than the last cursor value it saw.

The cursor advances to the newest value in each batch and is persisted with the source, so the next poll resumes from where the last one left off — even across server restarts.

Before saving, run a preview. Tessera pulls a single row from each selected table and renders it across all five dimensions in side-by-side cards, so you can see exactly what each row becomes: a relational row, a graph hyperedge with named endpoints, indexed text, a vector embedding, and a bitemporal record. Nothing is inserted.

If anything looks wrong — a mis-mapped endpoint, the wrong cursor column — fix it now.

Save the source. It appears in the connected-sources list with its schedule. When the first sync fires, open the source's history panel: each attempt records its timestamp, how many rows were imported, the new cursor value, and any error. The next poll pulls only rows newer than that cursor.

Your Postgres data is mirrored into Tessera as hyperedges. Foreign-key relationships are real graph edges, not flat property values. The data is indexed in all five dimensions, and updates flow in automatically with only the delta being pulled.

Switch to the query editor and walk the auto-derived graph with Cypher:

Tessera traverses the graph edges synthesised from your Postgres foreign keys. No graph-loading pipeline, no separate database, no sync job — just the same source data made queryable through a different lens.