Skip to content

Engines overview

35 engines under one consistent UI. SQL family in Free; NoSQL / cloud / vector in Pro.

Free tier — 7 engines + 13 wire-compat presets

Section titled “Free tier — 7 engines + 13 wire-compat presets”

The full SQL family + every engine that speaks a wire-compat dialect:

EngineWire-compat presets
PostgreSQLCockroach · Yugabyte · Neon · Supabase · Timescale · Redshift · Aurora-PG · Greenplum · Citus
MySQL / MariaDBTiDB · PlanetScale · Aurora-MySQL · Vitess
SQLite
SQL ServerAzure SQL
DuckDB · ClickHouse · CassandraScyllaDB (via Cassandra)

For wire-compat presets, the connection dropdown picks the upstream engine + the preset slot tunes a few catalog queries (SHOW COLUMNS vs INFORMATION_SCHEMA, partitioning syntax, etc.). Same underlying driver, dialect-aware UI.

Pro — 15 NoSQL · cloud · vector engines

Section titled “Pro — 15 NoSQL · cloud · vector engines”

Everything in Free, plus:

FamilyEngines
DocumentMongoDB
Key-valueRedis · Memcached
Column-familyCassandra · ScyllaDB
Cloud warehousesSnowflake · BigQuery · Databricks
SearchElasticsearch
Time-seriesInfluxDB
GraphNeo4j
Document (cloud)DynamoDB · Firestore
VectorQdrant · Weaviate · Pinecone

Each NoSQL / cloud engine has a native idiom — the chrome stays consistent (edit-as-draft, prod-tag confirmations, backup grammar) but the engine-shaped operations work the way that engine works:

  • Mongo: collection browser, BSON editor, aggregation pipeline builder, change stream tail
  • Redis: key tree, type-aware editors, pub/sub tail, JSONL dump
  • Cassandra: keyspace browser, ALLOW FILTERING warnings, prepared statement helper
  • BigQuery: dry-run cost estimator
  • Snowflake: warehouse suspend/resume controls
  • Vector DBs: similarity search panel (paste vector, set k, see top-k with scores)
  • Neo4j: Cypher editor + plan visualiser

Every engine takes:

  • Dialect (the engine type)
  • Name (your label)
  • Tagdev / staging / prod / free-form. prod triggers the typed-name confirmation rules (Confirmation rules)

Then engine-specific fields. Most SQL engines need host / port / user / password / database / SSL mode. Cloud engines need account identifiers + service-account credentials. Vector DBs need an API key + collection. Each engine page below covers its specifics.

The engines covered as “rest of the SQL family” or “rest of the NoSQL/cloud” don’t have dedicated pages yet — their depth matches the closest neighbour engine; the feedback channel catches anything missing.