DbSchema connects to ScyllaDB with a Cassandra-compatible JDBC driver, draws every keyspace as an ER diagram with partition and clustering keys annotated, and publishes documentation the whole team can browse.
Trusted by teams at
ScyllaDB's shard-per-core architecture rewards a data model designed around its partition keys — and punishes one that isn't. Yet the only view most teams have of that model is DESCRIBE output in cqlsh, scrolled through table by table.
DbSchema reads the system catalog and lays the whole keyspace out visually: tables with their partition and clustering keys, materialized views, secondary indexes, and the full CQL type system — collections, frozen types, and user-defined types included.
Cassandra-compatible tooling for clusters that outgrew guesswork.
Connect to a self-managed cluster or ScyllaDB Cloud and DbSchema reads the catalog — tables, column types, materialized views, and secondary indexes — into a diagram you can rearrange and annotate.
Compose SELECT statements in the visual builder with partition key predicates in place, and skip the ALLOW FILTERING penalty that unqualified queries pay at runtime.
Split a large keyspace into focused diagrams per domain, color-code the groups, and export to PDF or SVG when the data model goes into a design review.
One click renders the model as interactive HTML5 documentation: searchable diagrams, table definitions with partition and clustering key designations, keyspace replication strategy settings, and materialized view definitions. Teams running ScyllaDB across multiple datacenters get a shared reference nobody needs cqlsh — or cluster credentials — to read.
Explore the Documentation Tool
DbSchema ships its own open-source ScyllaDB JDBC driver — browse the code on
GitHub — and the DataStax
Cassandra JDBC driver works identically, since ScyllaDB is protocol-compatible with Apache
Cassandra. Connect with the host, the keyspace, and port 9042 by default,
giving a URL like jdbc:cassandra://host:9042/keyspace. If the cluster uses CQL
authentication — Cassandra's PasswordAuthenticator — supply the username and
password.
For ScyllaDB Cloud, use the hostname and credentials shown in the ScyllaDB Cloud console. Self-managed clusters with client-to-node encryption enabled take their SSL parameters in the JDBC URL or in the driver settings. Setup details are on the ScyllaDB JDBC driver page.
One installer: free Community Edition plus a 15-day Architect trial. No signup.
Teams working with ScyllaDB often use these engines too. Explore dedicated guides and JDBC setup for each.