QuraMate Logo QuraMate Docs
Getting started

Guide

Connections

Work with multiple databases using the same connection model QuraMate expects in DBConfig.

Updated 2026-03-15 · 6 min read

Jump to another doc

Start From Connection Launcher

Use the connection launcher to keep environment context explicit before creating tabs.

Connection launcher
Begin from the connection launcher and select the right environment first.

Use DBConfig-Aligned Inputs

QuraMate connection flow is built around DBConfig fields:

  • type, host, port, user, password, database
  • readOnly for safe first access
  • trustServerCertificate for certificate handling paths
  • sshEnabled + SSH fields when tunneling is required

For local engines (sqlite, duckdb, libsql), host/port usage differs from server engines.

Database type picker
Pick engine type first so required connection fields stay consistent.

Connection Hygiene

Use a consistent naming convention like prod-readonly, staging-app, and local-dev. This reduces write mistakes when switching quickly between tabs.

If SSH is required, test tunnel access with read-only before introducing write workflows.