Visual Schema Diagrams for TarantoolDB Spaces

Tarantool keeps data in in-memory spaces served at sub-millisecond speed, with a SQL layer over the NoSQL engine. DbSchema turns the SQL-facing spaces into ER diagrams, queries them over JDBC, and documents the model for the rest of the team.

Spaces with SQL-compatible metadata appear as diagram entities
Index types — TREE, HASH, RTREE, BITSET — captured in the model
Run SQL over JDBC; EXPLAIN reveals sequential scans before production does
Browse tuples in a paginated grid, no box.select calls required

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema drawing Tarantool spaces and indexes as an ER diagram

Trusted by teams at

The Data Model Lives in Lua
New Teammates Read Diagrams

A Tarantool application defines its spaces and indexes in Lua, right beside fibers and stored procedures. The structure is real and fast — and invisible, because no place exists where someone new can see how the spaces relate.

DbSchema reads the SQL-facing schema into a diagram, and relationships kept in application logic can be drawn onto the canvas by hand — the intended data model becomes something you can point at.

Diagram, Query & Hand Off
Tarantool Spaces

Relational-grade visibility for an in-memory platform.

Load Tarantool spaces and indexes into an ER diagram

From Spaces to Entities

Spaces defined with SQL-compatible column metadata load as diagram entities, index types included — a familiar ER view of the space-and-index structure.

Prototype SQL queries against Tarantool spaces

Prototype Before Lua Wraps It

Tarantool SQL covers SELECT, INSERT, UPDATE, DELETE, and basic joins — build statements interactively, call existing procedures with CALL, and keep the winners for Lua.

A Model for Compliance and Handoff

Export the space structure as offline documentation for teams that must record their data model — with the relationships drawn in, not merely implied by code.

Sub-Millisecond Data
Long-Lived Design

The design model is a file that outlives restarts, snapshots, and rewrites — a durable description of a deliberately volatile store.

Sketch Tarantool spaces without a running instance

Sketch Spaces Offline

Draft the space structure before the instance exists — or far away from it.

History in Git

Version the model beside the Lua code that defines the spaces.

Review SQL statements before they run on Tarantool

Statements in Plain Sight

Review generated SQL on screen before anything executes on the instance.

Manage Tarantool and relational databases from one tool

One Tool Across the Stack

Model Tarantool beside the relational database it caches for, in a single app.

TarantoolDB Connection Setup — Port 3301, Driver, VShard

Connect with the Tarantool JDBC driver (tarantool-jdbc-*.jar — supply it if not already bundled) to the host and port where the binary protocol and SQL listener run: 3301 by default, so the URL reads jdbc:tarantool://localhost:3301. Credentials are the native Tarantool users created via box.schema.user.create, and the listener itself is enabled with box.cfg{listen = 3301} in the Tarantool configuration.

Deployments sharded with VShard should point DbSchema at the router instance rather than individual storage nodes, so the SQL layer has visibility across all shards. More on the TarantoolDB JDBC driver page.