Databases

Different databases.
Native understanding.

Each engine has its own way of working. Recern follows it, with views built around how each one runs instead of a generic table browser.

Works with

Available

PostgreSQL

Sessions, locks, queries, tables, indexes and a console. Query statistics come from pg_stat_statements when it is installed.

OverviewSessionsLocksQueriesTablesIndexesConsole
Available

Redis

Memory, clients, the slow log and keys, with a console that knows which commands only read.

OverviewMemoryClientsSlow logKeysConsole
Available

Valkey

The Redis views, with Valkey recognised when you connect.

OverviewMemoryClientsSlow logKeysConsole
Available

Dragonfly

The Redis views for Dragonfly, recognised when you connect.

OverviewMemoryClientsSlow logKeysConsole
Available

Recern Vector

Open a .rvec file to see its collections, the HNSW graph and recall measured against exact search. Recern only reads the file.

OverviewIndexRecall
Coming soon

MongoDB

Collections, documents, operations, indexes and query efficiency.

Coming soon

ClickHouse

Queries, parts, merges, mutations and replicas.

Coming soon

MySQL

Sessions, locks, queries, InnoDB and replication.

Coming soon

SQLite

Tables, indexes, pragmas and storage of a file on your disk.

Coming soon

Cassandra

Keyspaces, tables, compaction and the health of every node.

Coming soon

pgvector

Vector indexes in PostgreSQL: whether queries use them, their memory and real recall.

Coming soon

Qdrant

Collections, segments and recall of a vector-native engine.

The order can change. Tell us which database you need next: [email protected]