Tessera DB
PX-01
View 01
Follow how everything connects, over the same records SQL reads.
Cypher and TQL walk the records the SQL tables hold. A record can link any number of entities, each in a named role, so a payment between a payer, a payee and an approver is one record, not an invented middle node.
01
04
View 01 · Graph
The relationships, and the rows behind them, in one place.
A graph that lives in its own database is a second copy that drifts. Here the graph is a way of reading the store: write a row in SQL and it is a node you can walk; create a relationship in Cypher and SQL sees it.
77
Algorithms
8
On Free
3,893
TCK scenarios pass
n-ary
Records
02
04
What it does.
01
Hyperedges
A record links any number of entities in named roles. Over Bolt, two-endpoint records map to relationships and records with more endpoints map to nodes with every endpoint kept.
02
Cypher and TQL
POST /api/query tells them apart by the first keyword. 3,893 of the 3,897 openCypher TCK scenarios pass, counted against the unmodified suite.
03
Bolt and the official drivers
Bolt 4.4 and 5.0–5.4, read and write, with role checks and optional TLS. Tested with the official Python 6.x, JavaScript, Go and Java drivers.
04
Algorithms in the engine
Project a graph once and run algorithms on it by name. Free has PageRank, weakly and strongly connected components, BFS, DFS, shortest path, degree centrality and triangle count; Enterprise has the rest of the 77.
05
Branches
Create a branch in an instant, write to it without touching main, and merge with a preview of exactly what will change. Branches survive a restart.
06
A published GQL subset
21 named GQL features run. It is not an ISO/IEC 39075 conformance claim.
03
04
A Cypher question, over HTTP.
curl -s -X POST -H "Authorization: Bearer $TESSERA_KEY" -H 'Content-Type: application/json' \
"$TESSERA_URL/api/query" \
-d '{"query":"MATCH (c:Customer)-[:OWNS]->(a:Account) RETURN c.name AS name, a.balance AS balance"}'04
04