DORA
Features
Multi-DatabasePostgreSQL, MySQL, SQLite & libSQLQuery HistorySearch, replay and analyze every querySchema VisualizationLive ER diagrams of your relationshipsDocker ContainersSpin up and manage local databasesSSH TunnelingReach private databases through secure tunnelsORM CockpitDiff Drizzle/Prisma schema, preview migrationsThemingCustom look and feel for your workspaceAnalyticsQuery PostHog with HogQL, build dashboards
All features
ChangelogDORADocumentationView web app
Dora docs
Dora docsGetting StartedInstallation

Connect a database

Connections

Features

Features

Guides

Working with data

Data StudioSQL ConsoleSchema VisualizerChartsExportLive change monitoring

ORMs

ORM CockpitORM Runners

Productivity

Command Palette & shortcutsAI AssistantDocker Manager

Reference & internals

Credentials & securityMock Data GuideBackend Features Integration

Reference

API ReferenceShared TypesDora runner (Go CLI/TUI)
Guides

Loading documentation…

Preparing this guide.

Loading page content

Docker Manager

Spin up, manage, and seed local database containers from inside Dora.

Mock Data Guide

Implementing the Data Seeder UI.

Engineered by remco_stoeten
GitHub ProfileRepositoryFeaturesDocsChangelog
© 2026 Dora. All rights reserved.
Guides

Credentials & security

How Dora stores connection credentials and AI keys, and how it secures private-network connections.

Dora is a local desktop app: your data and credentials stay on your machine and go directly to your databases and chosen providers. There is no Dora server in the middle.

Connection credentials

Saved connections are stored in a local SQLite database in your app data directory. Connection passwords are not persisted in plaintext. For a saved connection you re-enter the password when needed rather than having it written to disk unprotected.

Treat connection strings as secrets: they often embed a username and password. Anyone with read access to an exported string can use it.

AI provider keys

API keys for the AI assistant are encrypted at rest with AES-256-GCM. The master encryption key is generated on first run and stored in your operating system keychain:

  • macOS: Keychain,
  • Linux: Secret Service (gnome-keyring / libsecret),
  • Windows: Credential Manager.

It is never written to disk in plaintext. If no OS keychain is available, Dora falls back to a local key file so the app still works, but the keychain is preferred. You can also supply keys via environment variables instead of saving them.

Private-network databases

To reach a database that is not exposed to the internet, use an SSH tunnel. Dora authenticates with a private key file, a password, or your SSH agent, opens the tunnel before connecting, and closes it on disconnect, so your database stays unexposed.

Cloud provider tokens

Account integrations (Supabase, Neon, Vercel, PlanetScale, Xata, Cloudflare, Turso) store the provider token in the same secure storage and use it only to list your databases and build connections.

Docker Manager

Spin up, manage, and seed local database containers from inside Dora.

Mock Data Guide

Implementing the Data Seeder UI.

On this page

Connection credentialsAI provider keysPrivate-network databasesCloud provider tokens