A public market for the integrations Tabularis should support next. Request, sponsor, or claim a plugin and turn scattered requests into shipped drivers. Discord is for fast discussion; GitHub is for durable proposals.
Drivers and integrations waiting for scope, funding, or a maintainer.
Targets that already have a claim, branch, or initial scope.
Existing plugin wins that prove external drivers can land.
The featured slot should feel like a mission brief, not a normal backlog item. It points contributors and sponsors at the work with the clearest ecosystem impact, without pretending to have live market data.
A serious Oracle workflow without forcing users into heavyweight tooling.
Connection profiles, schema browsing, query execution, routines and export support for teams that still live around Oracle databases.
Highest impact after SQL Server for enterprise users evaluating Tabularis.
Every card is designed to become a real issue, discussion, sponsor target, or plugin owner handoff as the board matures.
A serious Oracle workflow without forcing users into heavyweight tooling.
Connection profiles, schema browsing, query execution, routines and export support for teams that still live around Oracle databases.
Highest impact after SQL Server for enterprise users evaluating Tabularis.
Finish read/write support and production-grade SQL Server workflows.
The driver is already in flight on a feature branch. Phase 2 needs help on TLS options, composite primary keys, FK aggregation and write support.
Phase 1 done. Phase 2 is where contributors can move the release.
Validate Redshift as a first-class analytical warehouse workflow.
Redshift speaks a PostgreSQL-derived dialect, but full support still needs warehouse-specific validation for metadata, pagination, auth, explain output, and query behavior.
Good candidate for a compatibility bounty because it can reuse parts of the PostgreSQL path only after real warehouse testing.
Make distributed SQL feel native instead of merely connectable.
CockroachDB uses the PostgreSQL wire protocol, but full support needs validation around schemas, introspection, transactions, explain output, and docs.
Likely starts as compatibility validation, not a separate driver.
Validate TiDB compatibility without pretending MySQL support is enough.
TiDB speaks the MySQL protocol, but distributed SQL behavior, metadata, transactions, and explain output need targeted validation before claiming full support.
A compatibility bounty can turn protocol support into a real support claim.
Inspect tables, keys, indexes, and targeted reads without building an AWS console clone.
DynamoDB support should be scoped around table discovery, key/index inspection, safe item reads, and AWS credential handling.
A good future target, but only if the first version avoids dangerous broad scans by default.
Cloud warehouse access for analytics teams using Tabularis notebooks.
Connection setup, warehouse/database/schema switching, result pagination and notebook-first analytics workflows for Snowflake users.
Best fit when paired with notebooks and repeatable reporting flows.
Expose keyspaces, tables, CQL queries, and practical inspection workflows.
Cassandra support should be scoped around CQL query execution, keyspace/table discovery, paging, and safe read workflows before attempting broad administration features.
Worth treating as the base driver for ScyllaDB compatibility too.
Use the Cassandra path as the base, then validate Scylla-specific behavior.
ScyllaDB can likely ride on a Cassandra/CQL driver, but full support should still document compatibility and any metadata or paging differences.
Best bundled with Cassandra so the board does not create two duplicate driver efforts.
Bring a durable embedded/server SQL database into the plugin ecosystem.
Firebird support needs connection setup, metadata inspection, query execution, type handling, and docs for both local and server deployments.
Strong fit for the plugin model because it expands SQL coverage without changing the core binary.
Extend SQLite workflows toward LibSQL and remote Turso-style databases.
LibSQL sits close to SQLite but adds remote workflows and sync-oriented assumptions. It should be validated as a separate compatibility target.
Useful for developers who already use SQLite locally but deploy on LibSQL/Turso-like infrastructure.
Support long-lived enterprise and embedded SQL Anywhere installations.
SQL Anywhere is niche but valuable for teams maintaining existing systems. The first target should be reliable read-only access and schema inspection.
Good bounty candidate if a real user can provide access, test cases, and review feedback.
Connect Tabularis notebooks to federated SQL engines.
Trino and Presto support should focus on catalogs, schemas, query execution, result paging, and docs for federated analytics workflows.
Pairs well with SQL notebooks because the value is federated analysis, not table editing.
Explore a focused SurrealQL workflow inside Tabularis.
SurrealDB needs a deliberately scoped plugin: connection, namespaces/databases, SurrealQL execution, result inspection, and docs before broad multi-model UI work.
Interesting ecosystem signal, but should stay query-first until the product shape is clear.
Bridge document collections into a focused desktop workflow.
A plugin for browsing collections, inspecting document shape, running filtered reads and exporting result sets without turning Tabularis into a generic NoSQL IDE.
Strong community pull, but scope must stay narrow and maintainable.
Run warehouse queries from the same workspace as local and app databases.
A BigQuery plugin would connect cloud analytics with Tabularis notebooks, query history, exports and AI-assisted SQL workflows.
High leverage for teams that mix app databases with analytics data.
Inspect indices, sample documents and run search queries from Tabularis.
A search-oriented plugin for index browsing, mappings, document samples and query execution without building a full observability platform.
Useful if scoped around inspection and query workflows, not cluster ops.
MariaDB is covered by the built-in MySQL/MariaDB workflow.
SHIPPEDRedisVirtual table views for strings, hashes, lists, sets and sorted sets.
SHIPPEDDuckDBLocal analytical database support through the plugin ecosystem.
SHIPPEDClickHouseColumnar database workflows for fast analytical systems.
Start with a GitHub Discussion. If the need is real, the item can graduate into a scoped bounty with an owner, target and delivery path.
