TETRAbase · The database

Connectionsmade simple

Graph connectivitySQL ubiquityUniversal simplicity

01 · A Tuesday morning

TETRAbase speaks PostgreSQL and openCypher over one store. Point your existing tools at it. No indexes or caches to maintain, encrypted on disk, in a fraction of the space. In our benchmarks, 82x faster than PostgreSQL and 66x faster than Neo4j.

Harvest Table is an invented example.

02 · Why it is faster

  • The data matrix

    TETRAbase stores tables and graphs in a single matrix and answers queries by performing operations on that matrix. SQL and openCypher use the same stored data, so there is no need to copy data between them.

  • Graph queries without pointer chasing

    A query that follows connections does not chase pointers from record to record. On the standard graph benchmark the lead grew with size: 29.5x at the smallest, 66x at SF10.

  • Lower peak memory use in graph benchmarks

    Deep queries do not pull the graph into memory. On the same queries TETRAbase peaked at less than half the memory of Neo4j and used 13x less CPU.

Read the whitepaper: A Multidimensional Data Matrix (47 pages, PDF) ↓

03 · The numbers

Month 1Month 36 →Click a layer
See this at scale →

See the graph benchmark against Neo4j → Download the SQL report, 12 October 2026 (PDF) ↓

Graph figures from By the Numbers, OpenCypher, 1 November 2026; SQL figures from TETRA, By the Numbers, 12 October 2026. One run on a single machine. The competing engines were benchmarked once, and those results are shown here. The full report covers the test conditions, limitations, and cases where TETRAbase performs worse. DataPower: Quick test profile, one run per database and size, 1 November 2026.

Run it on your own data.

Bring a workload. We’ll compare TETRAbase with your current system and share the results with you.