A Database Workspace for Developers: Seven Engines, SSH Tunnels, and Practical Data Tools

Developers often move between a terminal, a database client, an SSH tunnel command, a CSV tool, and a separate AI assistant just to investigate one issue. SSH Bridge now includes a dedicated database workspace that keeps those tasks closer to the infrastructure and project context where the work begins.

Seven Supported Database Engines

The workspace supports MySQL, PostgreSQL, Microsoft SQL Server, SQLite, Oracle, MongoDB, and Redis. That range covers traditional relational databases, local files, document storage, and key-value workloads without requiring a different desktop client for every system.

Each engine has its own defaults and dialect behavior. PostgreSQL profiles can include database and timeout settings, Oracle uses a service name, SQL Server exposes encryption and certificate options, MongoDB includes database and authentication-source settings, and Redis supports database selection and TLS configuration.

Encrypted Profiles and Connection Testing

A database profile includes the connection address, credentials, engine parameters, initialization queries, optional SSH tunnel, saved queries, export schedules, and query history. Before the profile reaches the backend, SSH Bridge encrypts it through the user's vault. The server stores only the encrypted envelope for that authenticated account.

The Add Database dialog can test the connection before saving. SQLite profiles validate the selected file, while network database profiles attempt a real session and report a useful success or failure message.

Built-In SSH Tunneling

Many production and staging databases should not be reachable from the public internet. A database profile can enable an SSH tunnel with its own host, port, username, and password or private-key authentication. Private-key passphrases are supported as well.

This means a developer can describe the database and the secure route to it in one encrypted profile instead of manually recreating a tunnel before every session.

A Real Query Workspace

The SQL editor includes line numbers, syntax highlighting, completion for keywords and discovered objects, multiple query tabs, selected-statement execution, and run-all behavior. Query results can be paged and copied as TSV, JSON, or Markdown. Developers can save useful queries, reopen query history, explain a statement, cancel a long-running query, and manage explicit commit or rollback flows.

Potentially dangerous statements receive a confirmation step before execution, keeping speed and review in balance.

Browse Schemas, Objects, and Data

The workspace can load metadata, browse schemas and tables, inspect columns and related details, view routines and database objects, and generate dialect-aware SQL for common changes. Data tools can stage inserts, updates, and deletes before sending the final statement to the database.

Redis uses a purpose-built key workflow for strings, JSON, lists, sets, hashes, sorted sets, and streams. That avoids forcing key-value operations through a relational table metaphor.

CSV, Backups, and Scheduled Exports

CSV tools support import mapping, preview, row limits, and export. A current query can also become a scheduled CSV export with its own name, interval, destination directory, and next-run information.

Backup and restore support depends on the engine and the required native utilities. SQLite uses file copies, while PostgreSQL, MySQL, MongoDB, and Redis workflows use their appropriate command-line tools. SSH Bridge validates support and asks for confirmation before restore operations that overwrite data.

AI Help With Database Context

The database assistant can use OpenAI, Gemini, or Ollama and receives context about the current engine, schemas, and active query. It can explain a query, help draft SQL, or return SQL that opens in a new query tab for review. The developer still decides what to execute.

Where the Workspace Fits

SSH Bridge began with secure server access, but developers need more than a shell. A database workspace beside SSH, files, tunnels, remote desktops, projects, messages, and meetings reduces context switching while keeping access details protected by the same vault-centered product model.