Roadmap
Active initiatives and the work queued behind them. Each entry links to a GitHub epic; sub-issues are where the actual work happens. Click a card for the technical write-up, the open tasks and how to claim one.
SQL Server driver
Microsoft SQL Server support is now being built as a **driver plugin** in its own repository, [tabularis-sqlserver-plugin](https://github.com/TabularisDB/tabularis-sqlserver-plugin), instead of a built-in driver inside the app binary. The plugin covers connection pooling, schema introspection, query execution, CRUD, DDL, triggers, stored routines and visual execution plans. It is in active development and has not shipped a release yet.
UI design system & visual identity
Tabularis was built by a backend developer, one modal at a time, with colors and spacing picked on the spot. It works, but it lacks a system. This initiative replaces the vibe-coded UI with a documented design system: real logo, semantic palette, one type and spacing scale, shared primitives. Not a UX rework — pure visual coherence, plus the docs needed so the next contributor doesn't have to reverse-engineer my taste.
Plugin registry platform
Shipped as **Tabularium**, a purpose-built plugin registry live at registry.tabularis.dev since Tabularis v0.16.0. Developers sign in via OAuth (GitHub, GitLab, Gitea/Forgejo — Codeberg included), claim a plugin slug, link their repo, and new releases are picked up automatically via webhooks. The registry stays a catalog + trust layer — binaries keep living in the author's Releases, with signature + SHA-256 verification on install. Built by Dominik Spitzli (@NewtTheWolf) on [#196](https://github.com/TabularisDB/tabularis/issues/196).
Not yet on the board
Other drivers and major features land here as they move from idea to scoped work. Propose one via a GitHub Discussion.