Whether you're a developer, tester, project manager, or support person, if you work directly with database query tools, chances are you have to run a lot of queries as part of your job. If you're like us, these queries are usually scattered about in an unsaved file, some with parameters from the last time you ran them. 

With HTDB, you can store these queries or load queries pulled from a version control system such as git. Navigate through queries visually.

When exploring data, one question always leads to another. Adding your queries to HTDB allows you to associate queries with other queries. If the next query requires parameters, the parameters will be satisfied from a selected row context.

When working with cluttered sql files in a database query tool, we're usually working against a single database representing a single environment, and to switch between DEV and PROD, we're copying and pasting a lot.

HTDB separates query stores from database connections so that queries you run against one environment can easily be run against another instance of the database in a related environment.

• No plain text storage of connection credentials 

• Connections are always read-only

• Connections are only open for the duration of the query

• Configure the app with a query timeout

• Reliably re-run queries (avoiding bad intermediate queries you might run while rebuilding in a typical query explorer)